Agent Passport System — Cryptographic Identity for AI Agents vs Proof Layer
A side-by-side look at the Agent Passport System — Cryptographic Identity for AI Agents and Proof Layer 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 Proof Layer 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 Proof Layer when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PROOF_LAYER_API_KEY, PROOF_LAYER_API_URL. - You want tools like
pl_evaluate, pl_get_receipt, pl_verify_receipt.
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 | PROOF_LAYER_API_KEYPROOF_LAYER_API_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 | 8 |
| Full listing | View Agent Passport System — Cryptographic Identity for AI Agents | View Proof Layer |
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
Proof Layer tools 8
pl_evaluateSubmit an AI agent action proposal to Proof Layer for governance evaluation. Returns a cryptographically-signed receipt with a verdict of EXECUTE, BLOCK, REVIEW, or SHADOW. Use this before any consequential agent action (sending emails, modifying data, making payments, etc.).pl_get_receiptRetrieve a Proof Layer audit receipt by its UUID. Returns the full receipt including verdict, signature, and policy pack hash.pl_verify_receiptCryptographically verify a Proof Layer receipt. Checks the Ed25519 signature and confirms the signing key is ACTIVE. Returns valid: true/false with a reason.pl_list_receiptsList recent Proof Layer audit receipts for the authenticated tenant. Supports filtering by agent and verdict.pl_usageGet current Proof Layer quota usage — receipts used, receipts remaining, credit balance, billing cycle dates, and plan tier.pl_list_policy_packsList all governance policy packs for the authenticated tenant, including which one is currently active.pl_create_planA human approves a governed plan — a scoped, time-bounded set of future actions across named agents. Returns a plan_id and JTI that agents use to request delegation receipts via pl_delegate. Scope patterns support wildcards: 'build:*' authorizes any action starting with 'build:'.pl_delegateAn agent requests authorization to perform a specific action under a parent plan. Returns 'ok' with a signed receipt (proceed with the action), 'checkpoint_required' (human must re-approve this specific action), or 'denied' (agent or action not authorized under the plan).
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"
]
}
}
}
Proof Layer
{
"mcpServers": {
"proof-layer": {
"command": "npx",
"args": [
"-y",
"@proof-layer/mcp@latest"
],
"env": {
"PROOF_LAYER_API_KEY": "YOUR_PROOF_LAYER_API_KEY_HERE",
"PROOF_LAYER_API_URL": "YOUR_PROOF_LAYER_API_URL_HERE"
}
}
}
}
Frequently asked questions
Agent Passport System — Cryptographic Identity for AI Agents is categorized under Cryptography and uses a local stdio subprocess. Proof Layer belongs to Cryptography and uses a local stdio subprocess. Pick Agent Passport System — Cryptographic Identity for AI Agents for cryptography work and Proof Layer 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. Proof Layer 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 proof-layer 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. Proof Layer 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