Attestix MCP

Install

Works in

• Claude Code
• SourceCraft
• Koda
• Coddy

Manual install

pip install attestix==0.4.2

What it does

Attestix is a Python package and MCP server that stores signed evidence about an AI agent. The server starts with `python -m attestix.main` over stdio and exposes 47 tools in nine groups: agent identities, A2A cards, DID identifiers, delegation, reputation, EU AI Act compliance, credentials, data provenance and blockchain anchoring. Data lives in JSON files under `~/.attestix`, and an Ed25519 key is created on first run. The agent creates an identity (`create_agent_identity`), gets a did:key or did:web DID, issues W3C credentials signed with Ed25519Signature2020 and bundles them into a signed presentation for a verifier. Delegation uses UCAN-style tokens, and the action log (`log_action`) is a SHA-256 hash chain, so a tampered record shows. For the EU AI Act there is a risk profile, an Article 43 conformity assessment record and an Annex V declaration that is also issued as a credential. Self-assessment is blocked for a high-risk profile. Optional anchoring (`anchor_identity`, `anchor_credential`, `anchor_audit_batch`) publishes hashes on the Base network through the Ethereum Attestation Service. Signed bundles can be verified without Python: the project ships verifier libraries for JavaScript, Go, Rust, Java and R.

Who it is for. For AI system developers who need signed agent identities and a verifiable action trail, and teams assembling EU AI Act documentation for provider review.

Example request

Create an identity for my data analysis agent with the capabilities data_analysis and reporting and show me its DID

MCP

Transport

stdio

Authentication

not required

Limitations

• A pre-1.0 project with a single maintainer and no independent security audit. The documentation recommends `attestix==0.4.2` while the source already describes 0.4.3, so pin the version you reviewed.
• A signature and a declaration do not prove conformity with the law. `workflow_complete` only shows that documentation is filled in, `legal_conformity` is not assessed, and generated declarations remain drafts.
• The signing key sits in `.signing_key.json` in the data directory; if you lose it, new artifacts cannot chain to the same DID. AES-256-GCM encryption of the key is switched on with `ATTESTIX_KEY_PASSWORD`.
• The local purge `purge_agent_data` does not erase external replicas, remote logs, previously shared credentials or third-party backups.
• Anchoring needs `BASE_RPC_URL`, a wallet with `BASE_WALLET_KEY` and funds for gas. Remote DID resolution and hosted signers depend on configured services. License Apache-2.0.

How to disable. Remove the attestix entry from mcpServers in ~/.claude.json and run pip uninstall attestix. Data and the key stay in ~/.attestix or in the directory from ATTESTIX_DATA_DIR. Delete them by hand and only after a backup: the signing key cannot be restored. If you set BASE_WALLET_KEY, remove the variable from the environment.

README in short

The repository's front page opens with a status block and a note on which versions are published to registries. Next come installation, CLI commands (`attestix status`, `attestix init`, `attestix compliance`), a table of verifier libraries in six languages and a table of nine modules. It has a quick start for MCP and for Python with a working example, a seven-step evidence workflow for a high-risk system, the package directory layout, all tools listed by group and a table of conformance tests against RFC 8032, W3C VC, W3C DID and UCAN. It ends with a security section, a link to the author's paper and a disclaimer that the tool does not replace counsel.