MCP.Market

Aga MCP server

by attestedintelligence·io.github.attestedintelligence/aga-mcp-server·v3.6.2
No reviews yet

Verifiable decision records for AI agents: signed receipts for calls to its own governed tools.

B80/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
Growing

0 stars609 downloads/wk

Reviews

Write one

Nobody has reviewed Aga yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Aga tools (11)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • attest_subject

    Attest subject, generate sealed Policy Artifact. Auto-loads into portal.

  • generate_evidence_bundle

    Export the canonical SEP evidence bundle: signed PERMITTED/DENIED tool-call receipts + Merkle proofs + a mandatory signed checkpoint, for offline third-party verification (verify_bundle_offline, aga-verify, or aga-receipt-spec/verify/verify-sep.mjs). Pin gateway_public_key to prove provenance.

  • get_chain_events

    Get continuity chain events.

  • get_portal_state

    Get current portal state, loaded artifact info, and enforcement status.

  • get_receipts

    Get all signed receipts, optionally filtered by artifact.

  • get_server_info

    Get AGA server info, public keys, and portal state.

  • init_chain

    Initialize continuity chain with genesis event.

  • list_claims

    List available claims with sensitivity levels.

  • measure_behavior

    Measure behavioral patterns (unauthorized tools, rate violations, forbidden sequences). DETECTIVE-ONLY by default: it records and PROVES drift but does not block. Pass enforce=true to also trip the portal into phantom quarantine on drift (opt-in; off by default). (NIST-2025-0035)

  • verify_bundle_offline

    Verify a canonical SEP evidence bundle offline (full §6 algorithm: structural floor, receipt signatures, chain+ordering, leaf-recompute + Merkle bijection, signed checkpoint). Pass pinned_public_key to also prove provenance.

  • verify_chain

    Verify continuity chain integrity.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan101 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Aga compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 60% of 48,255 servers
Tools
11
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
609
more than 90% of 12,191 servers with a package

What its tools let an agent do: 10 read · 1 create

Install Aga in Claude Code, Cursor or VS Code

Runs npx -y @attested-intelligence/aga-mcp-server on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add aga-mcp-server -- npx -y @attested-intelligence/aga-mcp-server
Add to Cursor

What the publisher says

From the Aga repository's README, as published. We do not edit it. Read it on GitHub

AGA - Attested Governance Artifacts

Verifiable decision records for AI agents: each governed tool-call decision becomes a signed, hash-chained receipt, exported in evidence bundles anyone can verify offline against the published format.

Status: published to npm; this release carries SLSA build provenance (check it: npm audit signatures). The server tools and the aga-proxy emit the canonical SEP evidence bundle, verifiable offline by the published @attested-intelligence/aga-verify and the reference verifier aga-receipt-spec/verify/verify-sep.mjs. Since 3.2.0 the verifier is algorithm-agile and ships a post-quantum profile: v1 Ed25519-SHA256-JCS (the default the gateway emits) and v2 ML-DSA-65+Ed25519-SHA256-JCS (a NIST FIPS-204 ML-DSA-65 + RFC-8032 Ed25519 composite, both must verify), selected per-bundle by the algorithm field with a VERIFIED / FAILED / UNSUPPORTEDPROFILE trichotomy. Pre-3.0 releases (a legacy continuity-chain bundle that does not verify under the SEP verifier) are deprecated; use ^3.0.0. Claim scope and residual attack surface are documented honestly in THREATBOUNDARY.md. 3.5.0 (2026-08-29) changes one behavior: an artifact's TTL now fails closed — on expiry the portal terminates and a further measurement is refused, where earlier releases degraded and kept measuring. If you depend on the old post-expiry behavior, pin 3.3.3. 3.6.0 (2026-09-18) changes no existing behavior: it makes aga-proxy honour AGAGATEWAYKEY / AGAGATEWAYKEY_FILE, which it had silently ignored. See CHANGELOG.md.

# This package IS the AGA MCP server (TypeScript, runs over stdio). Use it from any MCP client:
npx -y @attested-intelligence/aga-mcp-server

A Python companion SDK (aga-governance) is documented in the Python SDK section below.

Verify this yourself (don't take our word)

You do not have to take any of this on faith. The repo ships the reference verifier, the canonical vectors, and sample bundles, so you can check one offline right now, with no network and no callback to us:

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

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Aga: common questions

Is Aga MCP server safe?
Mostly: it is graded B (80/100). Read the Aga safety report
How do I install Aga?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Aga need an API key?
Yes. The registry entry asks for AGA_GATEWAY_KEY.
Is Aga maintained?
The last commit was 39 days ago (2026-09-26). The latest release is v3.6.2.
What can I use instead of Aga?
Servers from other publishers that do the same job: Nautilus Compass Memory MCP server.
How does Aga compare with other MCP servers?
safety score 80/100 (higher than 60% of 48,255 servers); tools 11 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Aga

Same job from other publishers: the closest match first, then the best rated.

  • Nautilus Compass Memory
    Local-first long-term memory for AI agents, with byte-recomputable signed verification receipts.
    B