Como instalo @attested Intelligence/aga?

Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.

@attested Intelligence/aga precisa de uma chave de API?

Este registro não lista nenhuma variável de ambiente obrigatória.

Qual transporte @attested Intelligence/aga usa?

@attested Intelligence/aga roda localmente via stdio.

Servidor MCP @attested Intelligence/aga | PlugMCP

Potencialize seu agente

Adicionar este servidor

O comando do próprio publicador. Não é um endpoint do PlugMCP.

Adicionar ao Cursor Adicionar ao VS Code Rodar no PlugMCP

Host a copy with our keys and logs.

Comando local

npx -y @attested-intelligence/[email protected]

O Claude Code não tem link de instalação para um comando local. Copie o comando abaixo e execute-o em um terminal.

shClaude Code

1claude mcp add attested-intelligence-aga-mcp-server -- npx -y @attested-intelligence/aga-mcp-server@3.6.6

Execute em um terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "attested-intelligence-aga-mcp-server": {4      "command": "npx",5      "args": [6        "-y",7        "@attested-intelligence/[email protected]"8      ]9    }10  }11}

claude_desktop_config.json

Local · npmInstalação do publicadorPasso a passo: adicione em Claude

URL remota ou um comando na sua máquina? Como as duas instalações diferem

Rodar no PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Abrir

Dados do servidor

Local

Transporte: stdio
Versão: 3.6.6
Última verificação

Do publicador

Documentação

AGA - Attested Governance Artifacts

Verifiable decision records for AI agents: each recorded tool-call decision is a signed, hash-chained receipt, exported in evidence bundles a reviewer can verify offline against the published format. Verification establishes the integrity of the receipts present, not that every action was recorded.

git clone https://github.com/attestedintelligence/aga-mcp-server
cd aga-mcp-server
# A canonical SEP bundle verifies; a one-byte-tampered copy is rejected.
node aga-receipt-spec/verify/verify-sep.mjs fixtures/valid_minimal.json   # OVERALL: VERIFIED (integrity only; no key pinned)
node aga-receipt-spec/verify/verify-sep.mjs fixtures/tampered.json        # OVERALL: FAILED

# Runtime example only, after the isolation and known-issue review.
npx -y @attested-intelligence/[email protected]

{
  "mcpServers": {
    "aga": {
      "command": "npx",
      "args": ["-y", "@attested-intelligence/[email protected]"]
    }
  }
}

# generate a seed once (32 random bytes, hex)
node -e "console.log(require('node:crypto').randomBytes(32).toString('hex'))"

{
  "mcpServers": {
    "aga": {
      "command": "npx",
      "args": ["-y", "@attested-intelligence/[email protected]"],
      "env": { "AGA_GATEWAY_KEY": "<your-64-hex-seed>" }
    }
  }
}

Category	Tools
Identity	`get_server_info`, `get_portal_state`
Lifecycle	`init_chain`, `attest_subject`, `revoke_artifact`
Measurement & decision	`measure_integrity`, `measure_behavior`, `verify_chain`
Evidence	`generate_evidence_bundle`, `verify_bundle_offline`
Privacy	`request_claim`, `list_claims`
Delegation	`delegate_to_subagent`
Audit	`get_receipts`, `get_chain_events`

# Published verifier CLI. Obtain and authenticate the expected key outside the bundle before running.
npx -y @attested-intelligence/[email protected] evidence-bundle.json --pubkey <gateway-public-key>

# Or, from a clone of this repo, the zero-dependency reference verifier (Node 18+) checks its supported profile; parser/pin behavior can differ:
node aga-receipt-spec/verify/verify-sep.mjs evidence-bundle.json --pubkey <gateway-public-key>

JS reference check	Python result field	What it covers
`structural`	`algorithm_valid` + parts of `bundle_consistent`	algorithm id, key well-formedness, receipt/proof counts
`receipt_signatures`	`receipt_signatures_valid`	Ed25519 over canonical receipt bytes
`chain_and_ordering`	`chain_integrity_valid`	prev-leaf linkage, canonical non-decreasing timestamps (ids are not ordering fields and are not checked)
`merkle_and_bijection`	`merkle_proofs_valid`	leaf recompute, single-root walk, index bijection
`signed_checkpoint`	`checkpoint_valid`	gateway-signed root + count + chain-head binding
`envelope_consistency`	`envelope_consistent`	envelope `gateway_id`, `generated_at`, `merkle_root` vs signed content (`bundle_id`, `schema_version`, the envelope `policy_reference` and `offline_capable` are unsigned and unchecked)
`gateway_key_match` (with `--pubkey`)	`gateway_key_match` / `provenance`	pinned issuer key

Known decomposition difference: the JS reference recomputes every Merkle leaf from full receipt content, so a receipt-signature tamper also fails merkle_and_bijection; the Python verifier surfaces the same tamper in receipt_signatures_valid, chain_integrity_valid, and bundle_consistent while its merkle_proofs_valid can remain true. Neither is looser: the bundle fails in both stacks, exit 1. A --pubkey KEY that is not 64 lowercase hex characters is a usage error (exit 2) in the JS reference, aga-verify and the Python SDK, and a 64-hex pin that is not a valid curve point is honored, fails to match, and fails the bundle (exit 1). In the September 25 measurements, --pubkey=KEY was ignored by the JS reference, aga-verify through 2.2.2, verify.go and v2/verify-v2.go, and by verify.py when it follows the bundle path (integrity only, exit 0), and read by the Python SDK. Other verifiers differ as well. Through runtime 3.6.4, the in-server engine (the package's ./verify export, which verify_bundle_offline calls) treats a pin that is not a well-formed key for the bundle's profile (for a v1 bundle, a small-order point or a non-canonical encoding) as no pin, and returns VERIFIED with pinned: false. v2/verify-v2.go does the same and prints integrity only; no key pinned (exit 0). A 64-hex value that is not a curve point counts as well-formed, so both take it as a pin and the bundle fails. The Go and Python reference verifiers in aga-receipt-spec/verify/ treat a pin that is not 64 lowercase hex the same way and print integrity only; no key pinned (exit 0). Read pinned before taking a VERIFIED as provenance; in CI, pass the key after a space and check that the output says provenance verified. A --pubkey given with no value is also treated as no pin (exit 0, integrity only) by aga-verify through 2.2.2, verify-sep.mjs, verify.py, verify.go and v2/verify-v2.go, and is a usage error in the Python SDK. Other differences concern the bundle rather than the pin, and https://attestedintelligence.com/security lists the ones measured, including which algorithm labels each verifier leaves unchecked; outside the conformance corpus the verifiers differ in both directions. Two examples, where the failing side fails closed: a proof leaf_index spelled as an integral float (1.0) reports FAILED in aga-governance 0.3.2 and VERIFIED in the others, and object keys outside the Basic Multilingual Plane (possible only in a non-string field value, which no shipped producer emits) sort differently in verify.py, verify.go, v2/verify-v2.go and aga-governance than in the JavaScript verifiers, so such a bundle reports VERIFIED in JavaScript and FAILED in Go and Python. These parser and cross-language differences remain. Standalone verifier 2.2.3 separately fixes expected-key handling: equals-form options are refused rather than ignored, missing values are usage errors, and malformed supplied API keys fail verification.

AI Agent                  AGA Proxy                      Verifier
   |                          |                              |
   |-- tools/call ----------->|                              |
   |                    [Evaluate Policy]                    |
   |                    [Sign Receipt]                       |
   |                    [Chain to Previous]                  |
   |<-- PERMITTED/DENIED -----|                              |
   |                          |                              |
   |                    [Export Bundle]                       |
   |                          |--------- evidence.json ----->|
   |                          |                  [Verify Signatures]
   |                          |                  [Verify Chain + Order]
   |                          |                  [Verify Merkle Tree]
   |                          |                  [Verify Signed Checkpoint]
   |                          |                  [PASS / FAIL]

# Start the proxy (the `aga-proxy` bin) in front of an upstream MCP server.
# stdio upstream = the default stdio transport (the upstream is a child process, not network-reachable).
npx -p @attested-intelligence/[email protected] aga-proxy start \
  --upstream "npx -y @modelcontextprotocol/server-filesystem /tmp/test" --profile permissive

# Terminal A: start the proxy in front of an upstream MCP server
npx -p @attested-intelligence/[email protected] aga-proxy start \
  --upstream "npx -y @modelcontextprotocol/server-filesystem /tmp/test" --profile permissive

# (First, drive at least one tools/call through the proxy from your MCP client; an empty
#  ledger has no receipts to checkpoint, and the export reports there is nothing to export.)
# Terminal B: export the live ledger from a different shell, then verify it offline
npx -p @attested-intelligence/[email protected] aga-proxy export -o evidence.json
npx -y @attested-intelligence/[email protected] evidence.json --pubkey <gateway-public-key>

Primitive	Purpose
Ed25519	Receipt signatures
SHA-256	Hash chaining, Merkle trees, leaf computation
JCS-profile (sorted-key canonical JSON)	Deterministic signing (canon is byte-compatible with the reference verifier)
Merkle Trees	Binding all receipts to a single verifiable root

# Check status
curl https://aga-mcp-gateway.attested-intelligence.workers.dev/health

# Download a static demonstration bundle (not a live export)
curl https://attestedintelligence.com/sample-bundle.json -o evidence-bundle.json
# Static sample only. Use the separately published sample pin, not a key read from this file.

pip install "aga-governance==0.3.2"

from aga import AgentSession

with AgentSession(gateway_id="my-gateway") as session:
    session.record_tool_call(
        tool_name="search_web",
        decision="PERMITTED",
        reason="tool in allowlist",
        request_id="req-1",
    )
    bundle = session.export_bundle()
    result = session.verify()
    assert result["overall_valid"]

npm test                              # TypeScript tests (vitest)
npm run test:conformance              # SEP conformance corpus
pip install "aga-governance==0.3.2" && python -c "import aga; print(aga.__version__)"   # Python SDK smoke check

src/
  sep/                 # Canonical SEP evidence engine: single source of truth (canon, merkle, receipt, checkpoint, bundle, verify)
  core/                # Governance primitives (portal, artifact, attestation, disclosure, delegation, behavioral) + internal continuity-chain profile
  crypto/              # Internal continuity-chain crypto: Ed25519 (node:crypto), SHA-256/blake2b, salt
  proxy/               # MCP governance proxy (transparent interception + policy evaluation; emits SEP bundles)
  middleware/          # Governance PEP wrapper (records a signed PERMITTED/DENIED receipt per governed call)
independent-verifier/  # @attested-intelligence/aga-verify: standalone SEP verifier, zero AGA imports
scenarios/             # Demo scenarios (SCADA, autonomous vehicle, AI agent) that emit SEP bundles
tests/                 # Historical 3.6.0 CI: 428 tests; reviewed 2026-09-21

The agent port listens on every network interface, with no authentication. Anyone who can reach the host on that port can send governed calls through the proxy. The proxy also sets no limit on the number of connections, so although each connection's unfinished message is capped (item 7), the memory they hold together is not: on 3.6.2, ten connections that each sent 7.5 MiB without ending a message raised the proxy's working set from 68 MiB to 392 MiB while they stayed open, and a governed call on another connection was still answered. On Windows, a process running under the same user account as the proxy can bind 127.0.0.1 on the same port while the proxy listens, and a local client that connects to 127.0.0.1 then reaches that process instead of the proxy, with no policy check and no receipt (measured on 3.6.2 with both processes under one account). Block inbound traffic to the port in the host firewall, or admit only the agent with network policy; on Windows, run nothing untrusted under the proxy's account, and check while the proxy runs that its process is the only listener on the port. The control port is bound to loopback; see item 12.
Two clients that reuse a JSON-RPC id through one proxy can receive each other's tool results. Workaround, measured on 3.6.0: give each client its own id range, or run one proxy per client. With disjoint ids, every result reached the client that asked for it.
When the gateway key is supplied through AGA_GATEWAY_KEY (with or without --ephemeral) or AGA_GATEWAY_KEY_FILE, the stdio upstream inherits that variable (the seed, or the file's path), so the upstream sits inside the key's trust domain. Workaround, measured on 3.6.0: run without either variable. The upstream then sees neither, but the proxy signs with a per-process key that cannot be pinned across restarts.
The --upstream-url mode forwards raw JSON-RPC over HTTP POST with only a content-type header. It does not implement the MCP Streamable HTTP transport (the Accept header, the request metadata headers and event-stream handling), so a spec-conformant HTTP MCP server rejects its requests. Workaround: bridge to the server over stdio.
A bundle file can repeat a field name anywhere: in a receipt, in the checkpoint or in the envelope. For example, a forged "decision": "PERMITTED" can be placed ahead of the signed "decision": "DENIED", or a forged checkpoint leaf_count ahead of the signed one. The published verifiers (aga-verify 2.2.2, aga-governance 0.3.2, the verifier in this package, and the reference verifiers in aga-receipt-spec/verify/) and the site's /verify page read the last occurrence, and when it holds the genuine value they report VERIFIED, with provenance when the key is pinned. They do not reject the file, so a tool or a person reading the first occurrence can see a value that was never signed. Measured on the public sample bundle, pinned to the sample key: with the repeated name inserted in a receipt, in the checkpoint or in the envelope, aga-verify 2.2.2, aga-governance 0.3.2, the verifier in this package and /verify report VERIFIED, and a real change of the checkpoint value fails. Workaround: treat the verifier's parsed output as the record's content, and reject or flag files with repeated field names before displaying them. A strict rejection of repeated field names is planned for the reviewed release.
A message can repeat the "method" member when aga-proxy has an HTTP upstream (--upstream-url). With tools/call first and another method last, aga-proxy reads the last copy, so it never checks the tool call against the policy, and it forwards every method other than tools/call to the HTTP upstream as the exact bytes it received. An upstream whose JSON parser keeps the first copy of a repeated name then runs the tool call, even one the policy denies. The bundle holds no receipt for that call: nothing at all when the last method is one the proxy passes through without a receipt (such as ping, initialize, a list method or a notification), and otherwise only a passthrough receipt that names the last method. An upstream that keeps the last copy handles the message as the method the proxy read. The stdio upstream, the default, is not affected: the proxy re-serializes each message before writing it, so the upstream receives one method. Measured on 3.6.2 from npm on 2026-09-25, with the restrictive profile and with the default permissive profile. Workaround: keep the stdio default, or have the HTTP upstream reject any message that repeats a member name. A strict rejection of repeated member names in the proxy is planned for the reviewed release.
aga-proxy does not record every tools/call it refuses. It signs a tools/call's receipt before it forwards the call, so with a stdio upstream a call it cannot record never reaches the tool (for an HTTP upstream, see item 6), but such a call leaves no receipt. These cases were measured on 3.6.2 from npm on 2026-09-25, each with no receipt and no response to the client: a tools/call whose tool name is a non-zero number, an array or an object (a name of 0, false, null or an empty string counts as no name and gets a DENIED receipt and an error); one whose tool name or string id holds an unpaired surrogate (the JSON escape \ud800, for example); under a --policy file in allowlist or denylist mode whose constraints member is missing or null, every tools/call with a tool name and arguments the proxy can canonicalize; and, under an allowlist file, a call it would otherwise permit that carries a string path when that tool's path_prefix is neither a string nor false, 0 or null. The proxy starts with such a policy file, and it reports each refusal listed above only on its own stderr. A message sent as a JSON-RPC batch array or without "jsonrpc": "2.0" is refused differently: the client gets an error, and there is no receipt. A message of 8,388,608 characters or more (UTF-16 code units, about 8.4 million), not counting the newline that ends it but counting a carriage return before that newline, also gets an error and no receipt, and the proxy then closes the connection, dropping any reply still due on it. The limit counts input not yet split into messages, so a message just under the limit can be refused the same way when the read that completes it also carries enough input after it to pass the limit; whether that happens depends on where the reads fall. On 3.6.2, when a 100-character message, a message 58 characters under the limit and a 100,000-character message were sent in one write, the first was answered, the second got the error and the connection closed; sent without the 100,000-character message, or without the 100-character one, every message was forwarded. These are the cases measured, not a proof that no other input does the same. Workaround: give every policy file a constraints object whose path_prefix values are strings, and have the client time out a call that gets no reply. A DENIED receipt and an error for a malformed tool name, and a check of the policy file at startup, are planned for the reviewed release.
aga-proxy can alter non-ASCII text whose bytes are split between two reads. It decodes each chunk it reads from the agent's connection, and from a stdio upstream's output, on its own, so a character split between two chunks becomes one or more replacement characters (U+FFFD). A tool call's arguments can then reach the upstream altered, and the receipt's arguments hash is the hash of the altered arguments; a large non-ASCII result from a stdio upstream can reach the agent altered. An HTTP upstream's result is decoded whole. Whether a split happens depends on how the bytes arrive, so any message with non-ASCII text can be affected, and large ones more often. Measured on 3.6.2 from npm on 2026-09-26: a forced split inside "é" reached the upstream as two replacement characters, and a result of 200,000 "€" reached the client with 15 replacement characters in it. Workaround: send JSON whose non-ASCII characters are written as \uXXXX escapes, so every byte the proxy reads from the agent is ASCII, and have a stdio upstream do the same; a forced split of the escaped message then arrived intact. A fix is planned for the reviewed release.
Exporting the evidence bundle takes time that grows with the square of the number of receipts, and aga-proxy handles nothing else while it runs: every governed call waits until the export ends. A call forwarded to a stdio upstream that has not answered when an export starts gets a timeout error if the export ends more than 30 seconds after the call was forwarded, although the upstream ran it and its receipt says PERMITTED, so an agent that retries can run the tool twice. Measured on 3.6.2 from npm on 2026-09-26 through the control channel's GET /export: 2.8 seconds at 1,000 receipts and 17.4 seconds at 2,500, with a tools/call sent during the export waiting as long; at 4,000 receipts an export took 43.8 seconds, and a call forwarded just before it, which the upstream answered in 2 seconds, got the timeout error. At 1,000 to 4,000 receipts a compact bundle took about 1.7 to 1.9 KB per receipt, rising with the count. An audit the same day measured 88 to 113 seconds at 5,000 receipts. Verification time grows close to linearly. Workaround: each export covers every receipt since the proxy started and does not shorten the chain, so bound the chain by restarting the proxy on a schedule: pause the agents, export and verify, then restart. A restart begins a new chain that is not linked to the last one and resets the rate-limit counts; with a per-process key (--ephemeral, or neither AGA_GATEWAY_KEY nor AGA_GATEWAY_KEY_FILE set) it also begins a new signing key, printed at startup, that cannot be pinned across restarts (item 3). Export outside busy periods, and export and verify before any stop, because the live chain is kept in memory and a stop loses receipts not yet exported. A fix that leaves the bundle's bytes unchanged is planned for the reviewed release.
Policy constraints check less than their names suggest. A path_prefix is checked only when the value under the checked key (path, or the keys a rule lists in path_keys) is a string, so the same path sent inside an array or an object is not checked. denied_patterns match case-sensitively and only in top-level string arguments, so an uppercased command, or one inside an array or a nested object, is not matched. A constraint key the proxy does not recognise, such as a misspelling, is ignored without a warning, and a value of the wrong JSON type is not rejected: allowed: "false", a string, allows the tool; in denylist mode a tool listed as false, null or 0 instead of an object is allowed; and a non-empty path_keys string instead of an array makes the check read each character as a key name, so the intended key goes unchecked. Rate limits count per tool name across the whole proxy, shared by every client, and in allowlist mode the limit is checked before the path and pattern rules, so a call those rules deny still uses up a slot. Measured on 3.6.2 from npm on 2026-09-26 with allowlist and denylist policy files: a path_prefix of /home denied "/etc/passwd" and forwarded ["/etc/passwd"]; a denied pattern of rm -rf denied rm -rf / and forwarded RM -RF / and the same command inside an array; a rule spelled denied_pattern denied nothing; allowed: "false" forwarded the call in both modes; a denylist entry of false forwarded the call; path_keys: "path" forwarded /etc/passwd past a /home prefix; and, under a limit of 2 a minute, two calls denied by a /home prefix left a third call, to a path under /home, denied for the rate limit, while after one such denial that call was forwarded. Workaround: treat path and pattern rules as a convenience rather than a boundary, restrict paths in the upstream server itself, and check a policy file's keys against the constraint names in dist/proxy/types.d.ts. Checks that fail closed on these inputs, and a check of the policy file at startup, are planned for the reviewed release.
A stdio upstream's response whose JSON line is 8,388,608 characters or more (UTF-16 code units, counting JSON escaping and a carriage return before the newline, but not the newline itself) is dropped. The call already has a PERMITTED receipt, and the agent gets a timeout error after 30 seconds, so an agent that retries can run the tool twice; the proxy reports the drop only on its own stderr. The limit counts upstream output not yet split into lines, so a response just under it can be dropped when the read that completes it also carries enough output after it to pass the limit; every response after it that begins in that read, possibly to other clients' calls, is dropped with it. Whether that happens depends on where the reads fall. Measured on 3.6.2 from npm on 2026-09-26: a 9,000,000-character result was dropped and the agent got the timeout after 30.0 seconds, while a 1,000,000-character result came back in 31 milliseconds. Through a running proxy, a response line of 8,388,607 characters was returned and one of 8,388,608 was dropped; and when the upstream answered three calls in one write (100 characters and 58 under the limit for one client, then 100 for the other), the first was answered and the other two, one of them the other client's, timed out, while the same answers without the leading 100-character answer were both returned. These are the cases measured. An HTTP upstream's result is read whole and is not dropped this way; on Linux, one at the same bound closes the agent's connection instead (item 13). Workaround: keep tool results well under the bound, for example by reading large files in parts, and where results are large run one proxy per client. An error returned at once is planned for the reviewed release.
The control channel does not check a request's Host or Origin header. It listens on 127.0.0.1 (port 18801 by default) so that a separate aga-proxy export can fetch the live bundle (routes /export, /status and /receipts). Measured on 3.6.2 from npm on 2026-09-26: GET /receipts and GET /export sent with the Host and Origin of another site returned 200, and both carried a denied call's argument path in its denial reason. A web page open in a browser on the same host can therefore read the live receipts and the evidence bundle through DNS rebinding, unless the browser blocks a public site's requests to the loopback address; any local user on the host can read them as well. A page can also start an export with a plain GET /export without rebinding, unless the browser blocks it, and each export holds up governed calls while it runs (item 9). The CLI has no option meant to turn the channel off; a --control-port of 70000, or any number above 65535, leaves it unstarted while governance runs, but then no command can export the running proxy's receipts. Workaround: do not browse the web on the host while the proxy runs, or run the proxy on a host where no one does, and on a host shared with other users treat the live receipts as readable by all of them. A Host and Origin check is planned for the reviewed release.
On Linux, an HTTP upstream's (--upstream-url) response whose JSON line, as the proxy serializes it, is 8,388,608 characters or more (UTF-16 code units, counting JSON escaping but not the newline) closes the agent's connection. The proxy writes the whole line to the agent's socket in one call. A Linux kernel with its default socket buffers takes only part of a write that size; the rest goes out as the client reads, but the whole line counts as waiting until it has all gone, so the proxy's guard against a client that does not read its responses sees more than 8,388,608 characters waiting, the newline included, and destroys the socket. The call already has a PERMITTED receipt and the upstream has run the tool; the agent's connection closes part-way through the reply with no error message, so an agent that reconnects and retries can run the tool twice; every other call in flight on that connection is lost with it; and the proxy reports nothing. Measured on 3.6.2 from npm on 2026-09-26 on a Linux 6.18 host with Node 24 and the default socket buffers (net.ipv4.tcp_wmem 4096 16384 4194304): result lines of 4,000,000, 8,000,000, 8,388,606 and 8,388,607 characters were returned, and lines of 8,388,608, 8,388,609, 9,000,000, 10,000,000, 12,000,000, 16,000,000, 20,000,000 and 32,000,000 characters closed the connection after 3.1 to 5.0 MB of the reply had arrived; a client that read nothing for 4 seconds got a 4,000,000-character result and lost a 9,000,000-character one after 2.7 MB. On Windows 11 the same proxy returned a 20,000,000-character result, and a 9,000,000-character one to a client that read nothing for 4 seconds, because that kernel took each write whole. A stdio upstream's response of this size is dropped instead (item 11). Workaround: keep tool results well under the bound, for example by reading large files in parts. An error returned at once is planned for the reviewed release.

@attested Intelligence/aga

Q: Quando @attested Intelligence/aga foi verificado pela última vez?

Última verificação: 2026-10-28. Signed decision records for agent vendors facing customer evidence reviews. Public reference gateway and static verifier; pre-pilot, with documented limits.

GitHub ActionsReivindicar este servidor

Signed decision records for agent vendors facing customer evidence reviews. Public reference gateway and static verifier; pre-pilot, with documented limits.

Devops Developer Tools

Adicionar ao Cursor Adicionar ao VS Code Rodar no PlugMCPReivindicar este servidor

Adicionar ao Cursor Adicionar ao VS Code Rodar no PlugMCP

1{2  "mcpServers": {3    "attested-intelligence-aga-mcp-server": {4      "command": "npx",5      "args": [6        "-y",7        "@attested-intelligence/[email protected]"8      ]9    }10  }11}

.cursor/mcp.jsonServidor MCP

Transporte: stdio
Status: Local

Adicionar este servidor

Host a copy with our keys and logs.

Dados do servidor

Documentação

AGA - Attested Governance Artifacts

Reference runtime 3.6.6

Verify a retained record

What This Does

Optional runtime evaluation

Use with Claude Desktop in the approved evaluation environment

Persist a synthetic evaluation key before testing restarts

MCP Tools (15)

Quick Start: verify a bundle offline

Check-name mapping across implementations

How It Works

MCP Governance Proxy

Exporting the evidence bundle from a running proxy

Verification (canonical SEP 3.0; normative §6 algorithm in `aga-receipt-spec/verify/verify-sep.mjs`)

Cryptographic Primitives

Live Gateway

Python SDK

Test Suite

Benchmarks

Project Structure

Links

Historical issues through 3.6.4 and separately published verifiers

Security

Contributing

License

@attested Intelligence/aga

Ferramentas

Perguntas

Como instalo @attested Intelligence/aga?