Agent Passport System — Cryptographic Identity for AI Agents vs Computeledger

A side-by-side look at the Agent Passport System — Cryptographic Identity for AI Agents and Computeledger 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 requiredComputeledger logoComputeledgerCryptography · Local subprocess (stdio)Signs, hash-chains, and verifies compute usage receipts via an MCP server, no issuer trust required.43FairAuth: not declared

Verdict: choose Agent Passport System — Cryptographic Identity for AI Agents for cryptography work as a local process; choose Computeledger 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

Computeledger logoChoose Computeledger when

  • You need dedicated capabilities in the Cryptography domain.
  • You prefer a local stdio subprocess transport.
Explore Computeledger

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 AgentsComputeledger logoComputeledger
CategoryCryptographyCryptography
Quality signal64/100 · Good43/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars40
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools154Not listed

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

Computeledger tools

No tool names declared yet. Check the project README from the listing page.

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"
      ]
    }
  }
}

Computeledger

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "computeledger": {
      "command": "npx",
      "args": [
        "-y",
        "computeledger-cli"
      ]
    }
  }
}

Frequently asked questions

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