Log inSubmit server

Agent Passport System — Cryptographic Identity for AI Agents vs APEX PSI

A side-by-side look at the Agent Passport System — Cryptographic Identity for AI Agents and APEX PSI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Agent Passport System — Cryptographic Identity for AI Agents logoAgent Passport System — Cryptographic Identity for AI AgentsCryptography · Local subprocess (stdio)Cryptographic identity, delegation, governance, and commerce for AI agents. 152 tools.64GoodAuth: no auth requiredAPEX PSI logoAPEX PSICryptography · Local subprocess (stdio)Cryptographic truth infrastructure for AI agents: seal, verify, anchor, cite, audit.60GoodAuth: not declared

Verdict: choose Agent Passport System — Cryptographic Identity for AI Agents for cryptography work as a local process; choose APEX PSI for cryptography as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Agent Passport System — Cryptographic Identity for AI Agents logoChoose 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.
Explore Agent Passport System — Cryptographic Identity for AI Agents

APEX PSI logoChoose APEX PSI when

  • You need dedicated capabilities in the Cryptography domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like seal, verify, anchor.
Explore APEX PSI

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAgent Passport System — Cryptographic Identity for AI Agents logoAgent Passport System — Cryptographic Identity for AI AgentsAPEX PSI logoAPEX PSI
CategoryCryptographyCryptography
Quality signal64/100 · Good60/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars41
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools1545
Full listingView Agent Passport System — Cryptographic Identity for AI Agents View APEX PSI

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

APEX PSI tools 5

  • sealStamp a cryptographic receipt on content. Writes to the APEX PSI append-only ledger with SHA-256 hash, Ed25519 signature, and post-quantum LMS-W4-SHA256 signature. Proves existence and integrity at a point in time — not the truth of the contents.
  • verifyConfirm a seal's integrity against the APEX PSI append-only ledger. Accepts a receipt object (from the seal tool) or a raw SHA-256 hash. Reports whether the hash is present and anchored — integrity, not the truth of the original content.
  • anchorRead the Bitcoin (OpenTimestamps) anchoring state of the ledger's pending Merkle roots, or — only when action:'anchor' is passed explicitly — request that pending roots be aggregated and submitted to the OTS calendars. Defaults to 'status' (read-only) so a routine call never triggers a batch write. An anchor becomes confirmed only when a real Bitcoin block is found.
  • citeGenerate a citation for a sealed receipt in APA, BibTeX, or MLA format, citing the APEX PSI ledger entry.
  • verify_chainIndependently verify a chain of receipts against the APEX PSI ledger. Recomputes each hash's presence and integrity and reports Merkle chain continuity. Returns a verification report — a recomputation result, not an opinion or a certification.

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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "agent-passport-system-cryptographic-identity-for-ai-agents": {
      "command": "npx",
      "args": [
        "agent-passport-system-mcp"
      ]
    }
  }
}

APEX PSI

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "apex-psi": {
      "command": "npx",
      "args": [
        "-y",
        "apex-psi-mcp"
      ]
    }
  }
}

Frequently asked questions

Agent Passport System — Cryptographic Identity for AI Agents is categorized under Cryptography and uses a local stdio subprocess. APEX PSI belongs to Cryptography and uses a local stdio subprocess. Pick Agent Passport System — Cryptographic Identity for AI Agents for cryptography work and APEX PSI 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. APEX PSI 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 apex-psi 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. APEX PSI has 60/100 (Good) with 1 views, 0 installs and 1 GitHub stars.

Popular comparisons with Agent Passport System — Cryptographic Identity for AI Agents

Popular comparisons with APEX PSI