Aga MCP Server

MCP governance proxy and evidence engine for AI agent tool calls: evaluate each call against a sealed policy, permit or deny it at the proxy

Remote serverstreamable-httpPython

What is the Aga MCP server?

Aga MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. MCP governance proxy and evidence engine for AI agent tool calls: evaluate each call against a sealed policy, permit or deny it at the proxy boundary, and prove every decision with signed, offline-verifiable evidence bundles.

What you get

Cryptographic runtime governance for AI agents and autonomous systems.

What the assistant can call

Once Aga is connected, these are the calls the assistant has available:

  • Category — Tools
  • Identity — get_server_info, get_portal_state
  • Lifecycle — init_chain, attest_subject, revoke_artifact
  • Evidence — generate_evidence_bundle, verify_bundle_offline
  • Privacy — request_claim, list_claims
  • Delegation — delegate_to_subagent
  • Audit — get_receipts, get_chain_events

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration and credentials

You will need one environment variable: AGA_GATEWAY_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Aga's toolset — Category, Identity, Lifecycle and 4 more — is a fair guide to whether it matches your workflow. It is maintained by attestedintelligence; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the aga mcp server does with a few real requests.

Available tools

ToolWhat it does
CategoryTools
Identityget_server_info, get_portal_state
Lifecycleinit_chain, attest_subject, revoke_artifact
Evidencegenerate_evidence_bundle, verify_bundle_offline
Privacyrequest_claim, list_claims
Delegationdelegate_to_subagent
Auditget_receipts, get_chain_events

How to install the Aga MCP server

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

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
AGA_GATEWAY_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Aga to Category.
  • Use Aga to Identity.
  • Use Aga to Lifecycle.

Frequently asked questions

It connects Aga to MCP-compatible AI assistants such as Claude and Cursor, exposing 7 tools (Category, Identity, Lifecycle, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Aga directly.