ERC-8004 Agent Identity Bridge — Claude Code MCP server: what it does
ERC-8004 Agent Identity Bridge — a remote MCP server that reads ERC-8004 identity and reputation records, scores an agent's feedback and returns unsigned attestations for your own signer.
no license 555 installs updated 2026-07-11
claude mcp add --transport http agent-erc8004-bridge https://agent-erc8004-bridge--hartjustin6.run.toolsWhat ERC-8004 Agent Identity Bridge does
Point it at ERC-8004 and your coding agent can pull a registration straight from the Identity Registry: chain id, ERC-721 token id, the agent URI, the owner. The bridge answers with a stable DID derived from those values, so later lookups work either through that DID or through the chain and token pair. Re-importing the same record overwrites it instead of creating a duplicate.
Reputation comes from feedback you import yourself. Each item carries a value, a timestamp, and optionally a source, a weight and a feedback id. score_agent folds them into a number from 0 to 1 where recent entries count for more than old ones. An agent with nothing imported sits at a neutral 0.5 rather than zero.
No private key ever reaches this server, and it does not write to a chain. That is stated as an invariant, so the validation payload leaves unsigned and content-addressed: anchoring it is your signer's job, and until you run one you hold a draft rather than a proof. Nine tools cover the loop, ending with verify_attestation, which recomputes the hash to show the payload is intact.
What it helps with
- resolve a registered agent from its chain id and token id
- score an agent's trust from imported feedback, weighting recent entries
- tie an on-chain identity to a fleet DID
- produce an unsigned validation payload for your own signer
- check that an attestation payload was not altered
Example prompts for the agent
- Import the ERC-8004 registration for this agent and show me its bridge DID.
- Score the agent behind
did:viridis:erc8004:<chain>:<token>using the feedback already imported. - Export the current trust score as an unsigned attestation and verify its hash.
How to install ERC-8004 Agent Identity Bridge
Platform CLI: remote server
claude mcp add --transport http agent-erc8004-bridge https://agent-erc8004-bridge--hartjustin6.run.toolsPlatform CLI: remote server
codex mcp add erc-8004-agent-identity-bridge --url https://agent-erc8004-bridge--hartjustin6.run.toolsConfig file
{
"mcpServers": {
"erc-8004-agent-identity-bridge": {
"url": "https://agent-erc8004-bridge--hartjustin6.run.tools"
}
}
}Config file
{
"servers": {
"erc-8004-agent-identity-bridge": {
"type": "http",
"url": "https://agent-erc8004-bridge--hartjustin6.run.tools"
}
}
}Platform CLI: remote server
gemini mcp add -t http erc-8004-agent-identity-bridge https://agent-erc8004-bridge--hartjustin6.run.toolsStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about ERC-8004 Agent Identity Bridge
How do I install ERC-8004 Agent Identity Bridge in Claude Code?
Run claude mcp add --transport http agent-erc8004-bridge https://agent-erc8004-bridge--hartjustin6.run.tools. The same command with the name erc-8004-agent-identity-bridge registers the server under that second name.
What does ERC-8004 Agent Identity Bridge do?
It imports ERC-8004 registrations and feedback, computes a decay-weighted trust score, binds on-chain identities to DIDs and exports attestations unsigned so your own signer can anchor them.
Do I need keys or chain write access?
No. The server reads records and prepares payloads; signing and sending them on-chain stay with your own tooling.