LabscoMCP early access ↗
attestedintelligenceMCP SERVER · OFFICIAL PROJECT

AGA MCP Server

Seal what an agent is allowed to do into a signed artifact, measure it against that artifact while it runs, and export evidence anyone can verify offline.

by attestedintelligence ↗Agent Guardrails, Content Safety & Audit✓ Official

LABSCO SUMMARY

Every measurement leaves a receipt, and the receipts verify without calling home.

The loop is attest, measure, verify: a sealed artifact fixes what is allowed, each measurement against it is signed, and the exported bundle carries the permitted and denied calls with their proofs. Offline verification is what makes that evidence worth anything to somebody outside your organisation.

What it is

A runtime governance layer for agents. It attests a subject into a sealed policy artifact, measures the running state against it, and produces signed receipts and bundles that verify without a network.

What you get

  • attest_subject — attests a subject and seals a policy artifact, loading it into the portal
  • measure_integrity — measures subject state against the sealed reference, signing a receipt for every measurement
  • measure_behavior — behavioural patterns such as unauthorized tools, rate violations and forbidden sequences, detective-only by default
  • delegate_to_subagent — derives a constrained artifact for a sub-agent, whose scope can only narrow, never widen
  • revoke_artifact — revokes an active artifact mid-session, terminating the portal on the next measurement
  • init_chain, verify_chain and get_chain_events — the continuity chain started from a genesis event, verified, and read back
  • generate_evidence_bundle and verify_bundle_offline — export the permitted and denied tool-call receipts with Merkle proofs, and verify a bundle with no network involved
  • request_claim and list_claims — available claims with their sensitivity levels, and disclosure requests that substitute automatically when denied
  • get_receipts, get_server_info and get_portal_state — the signed receipts, the server's public keys, and the current portal and enforcement state

Requirements

npx and a Node runtime; it runs as a local stdio process and needs no account key. Set AGA_GATEWAY_KEY to a signing seed you generate yourself before first use; without it the signing key changes on every restart, so evidence bundles cannot be pinned to one key. Verifying a bundle needs nothing at all — the reference verifier ships in the repository.

Setup effort

One command — npx -y @attested-intelligence/aga-mcp-server