Agent Passport System — Cryptographic Identity for AI Agents vs Provenonce
A side-by-side look at the Agent Passport System — Cryptographic Identity for AI Agents and Provenonce 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 Provenonce for cryptography as a local process. 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 Provenonce when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PROVENONCE_API_KEY, PROVENONCE_AGENT_HASH, PROVENONCE_SKILL_REF, PROVENONCE_REGISTRY_URL. - You want tools like
provenonce_register, provenonce_status, provenonce_purchase_sigil.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cryptography | Cryptography |
| Quality signal | 64/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | PROVENONCE_API_KEYPROVENONCE_AGENT_HASHPROVENONCE_SKILL_REFPROVENONCE_REGISTRY_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 154 | 11 |
| Full listing | View Agent Passport System — Cryptographic Identity for AI Agents | View Provenonce |
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
Provenonce tools 11
provenonce_registerRegister this agent with Provenonce to get a cryptographic identity (hash + API key). Safe to call multiple times — returns existing identity if already registered. No wallet required. Free.provenonce_statusGet this agent's current Provenonce status: identity, SIGIL, beats balance, and next steps. Requires prior provenonce_register call.provenonce_purchase_sigilPurchase a Provenonce SIGIL to unlock full provenance: heartbeat access, signed passport, and a permanent identity record. If payment_tx is omitted, returns payment instructions (fee amount + address). SIGIL format: name*principal*tier (e.g. my-agent*acme*ind).provenonce_heartbeatSubmit a heartbeat to prove this agent is alive. Root agents (depth 0) require a SIGIL first; child agents (depth > 0) can heartbeat without a SIGIL. If payment_tx is omitted, returns payment instructions (fee amount + address).provenonce_get_passportGet this agent's cryptographically signed Passport — a verifiable identity document any third party can verify offline using the Provenonce authority public key. Root agents (depth 0) require an active SIGIL; child agents (depth > 0) only need at least one heartbeat.provenonce_beats_proofCompute a Beats work-proof — cryptographic evidence of computational effort by this agent. Computes sequential hash chains at the current network difficulty, submits to the Beats service for a signed receipt. The receipt can be used for spawn authorization and other operations.provenonce_submit_beatsCompute VDF beats and submit to the Registry to credit this agent's lifetime beat count. Unlike provenonce_beats_proof (which gets a receipt for spawn/resync), this extends the agent's persistent beat chain and increases the "Lifetime Beats" metric visible in the Registry.provenonce_verify_agentVerify another agent's Provenonce identity. Returns their SIGIL, identity class, and registration status. Public — no authentication required.provenonce_spawnSpawn a child agent under this agent's identity. The child inherits lineage from the parent. Returns the child's hash and API key. Requires sufficient beats balance or a work-proof receipt.provenonce_get_lineageGet the full lineage chain for an agent — all events in its provenance history (registration, SIGIL issuance, heartbeats, spawns). Public — no authentication required.provenonce_batch_heartbeatSubmit heartbeats for multiple child agents in a single call. One payment covers all children. Requires active sponsorships for each child. Max 20 children per batch.
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"
]
}
}
}
Provenonce
{
"mcpServers": {
"provenonce": {
"command": "npx",
"args": [
"-y",
"@provenonce/mcp"
],
"env": {
"PROVENONCE_API_KEY": "YOUR_PROVENONCE_API_KEY_HERE",
"PROVENONCE_AGENT_HASH": "YOUR_PROVENONCE_AGENT_HASH_HERE",
"PROVENONCE_SKILL_REF": "YOUR_PROVENONCE_SKILL_REF_HERE",
"PROVENONCE_REGISTRY_URL": "YOUR_PROVENONCE_REGISTRY_URL_HERE"
}
}
}
}
Frequently asked questions
Agent Passport System — Cryptographic Identity for AI Agents is categorized under Cryptography and uses a local stdio subprocess. Provenonce belongs to Cryptography and uses a local stdio subprocess. Pick Agent Passport System — Cryptographic Identity for AI Agents for cryptography work and Provenonce 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. Provenonce 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 provenonce 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. Provenonce has 55/100 (Good) with 2 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