Agent Passport System — Cryptographic Identity for AI Agents vs AnchorRegistry
A side-by-side look at the Agent Passport System — Cryptographic Identity for AI Agents and AnchorRegistry MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Agent Passport System — Cryptographic Identity for AI Agents for cryptography work as a local process; choose AnchorRegistry for cryptography over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Agent Passport System — Cryptographic Identity for AI Agents when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
list_profiles, list_tools_for_scope, identify.
Choose AnchorRegistry when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
ar_verify_arid, ar_verify_by_hash, ar_resolve_tree.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cryptography | Cryptography |
| Quality signal | 64/100 · Good | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 154 | 3 |
| Full listing | View Agent Passport System — Cryptographic Identity for AI Agents | View AnchorRegistry |
Tools & capabilities
Agent Passport System — Cryptographic Identity for AI Agents tools 154
list_profilesShow available tool profiles. Set APS_PROFILE env var to limit exposed tools (e.g. APS_PROFILE=data).list_tools_for_scopeList available MCP tools filtered by delegation scope. Pass your delegation scopes to see which tools you can use. Scopes: identity, delegation, principal, reputation, coordination, communication, governance, commerce, data, gateway, network, temporal, attribution, settlement, capability, mutual-auth. Use ['*'] for all tools.identifyIdentify yourself to the coordination server. Sets your role and scopes tools accordingly.generate_keysGenerate an Ed25519 keypair for agent identity.issue_passportIssue a complete agent passport with keys, signed passport, attestation summary, and optional values floor in a single call. The server silently captures Tier 0 observed signals and computes a passport grade (0-3). Use this to onboard any agent without an npm install.verify_issuerVerify that a passport was officially issued by AEOESS. Checks the issuer countersignature against the published AEOESS public key. Returns false for self-signed passports.get_passport_gradeQuery the attestation grade and issuance context for a passport. Returns the passport grade (0-3), flags, and evidence summary. Grade 0 = self-signed, 1 = issuer countersigned, 2 = runtime-bound, 3 = principal-bound. This is the partner-facing trust query.list_issuance_recordsList all stored issuance records with their passport grades. Shows how many passports have been issued in this session and their trust posture. Useful for monitoring issuance patterns.get_behavioral_sequenceGet the post-issuance behavioral sequence for an agent. Shows the first 10 tool calls after passport issuance. Real agents do work. Farming agents extract.get_my_roleGet your current role, assigned tasks, and role-specific instructions.create_task_brief[OPERATOR] Create a new task with roles, deliverables, and acceptance criteria.assign_agent[OPERATOR] Assign an agent to a role in a task. Creates a delegation automatically.- +142 more on the listing page
AnchorRegistry tools 3
ar_verify_aridResolve an AnchorRegistry AR-ID to its full provenance record. Use this when you encounter an SPDX-Anchor or DAPX-Anchor tag (e.g. in a README, paper, model card, or website) and need to confirm what the artifact is, who anchored it, when, what type it is, and whether the tree has been sealed, retracted, voided, or affirmed. Free, public, no auth required.ar_verify_by_hashResolve an artifact by its SHA-256 manifest hash. Use this when you have the artifact itself but no AR-ID, and want to check whether it has been anchored. Returns the AR-ID and full provenance record if found, or a clear "not anchored" response otherwise.ar_resolve_treeResolve the full provenance tree for an AR-ID. Returns every anchor in the tree (root + all descendants) with their relationships, types, manifest hashes, and timestamps. Use this when you need to understand a multi-artifact provenance chain — for example, a research paper anchored as the root with its training dataset and model weights as children.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Agent Passport System — Cryptographic Identity for AI Agents
{
"mcpServers": {
"agent-passport-system-cryptographic-identity-for-ai-agents": {
"command": "npx",
"args": [
"agent-passport-system-mcp"
]
}
}
}
AnchorRegistry
{
"mcpServers": {
"anchorregistry": {
"url": "https://mcp.anchorregistry.ai/mcp"
}
}
}
Frequently asked questions
Agent Passport System — Cryptographic Identity for AI Agents is categorized under Cryptography and uses a local stdio subprocess. AnchorRegistry belongs to Cryptography and uses a remote HTTP/SSE transport. Pick Agent Passport System — Cryptographic Identity for AI Agents for cryptography work and AnchorRegistry for cryptography.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Agent Passport System — Cryptographic Identity for AI Agents is listed as free. Auth: no auth required. AnchorRegistry has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add agent-passport-system-cryptographic-identity-for-ai-agents and anchorregistry as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agent Passport System — Cryptographic Identity for AI Agents has a quality signal of 64/100 (Good) with 1 views, 0 installs and 4 GitHub stars. AnchorRegistry has 47/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.
Related comparisons
Popular comparisons with Agent Passport System — Cryptographic Identity for AI Agents
Agent Passport System — Cryptographic Identity for AI Agents vs Aga MCP Server
Agent Passport System — Cryptographic Identity for AI Agents vs Firecrawl MCP Server
Agent Passport System — Cryptographic Identity for AI Agents vs Codebase Memory MCP
Agent Passport System — Cryptographic Identity for AI Agents vs Server Everything