Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Agent Passport System — Cryptographic Identity for AI Agents

NPM · AGENT-PASSPORT-SYSTEM-MCP · 2 COMPONENTS

Cryptographic identity, delegation, governance, and commerce for AI agents. 154 tools.

+7 this week 93 Trust /100

Last scanned (11 hours ago)

Scores higher than 96% of npm servers

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security94
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Declares code that runs automatically (postinstall) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
  • 0 of 7 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to agent-passport-system/agent-passport-mcp). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 15534 tokens (~100/item across 154 items; 154 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management99
  • Stability check failed: the tool surface changed between 6.1.2 and 8.1.1: 0 tool removals, 3 breaking changes, 2 additions. See how to fix → Fail
Tool Coverage89
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 67% of tool parameters carry a description.Partial
Tool Safety89
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 5 of 9 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_with_context" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 154 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +11
    • CVE-2026-111770 no longer affects this package ▲ security
    • GHSA-f897-62hf-6gxq no longer affects this package ▲ security
    • CVE-2026-111771 no longer affects this package ▲ security
    • CVE-2026-111768 no longer affects this package ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 1.00 ▲ functional
  • 4 Nov 26 −6
    • Known CVEs: fail → unverified ▼ security
    • Dependency health: 1.00 → unverified ▼ functional
    • Package version: 8.1.0 → 8.1.1 functional
  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 96 to 99.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 89 to 92.

  • 28 Oct 26 +1
    • GHSA-f897-62hf-6gxq affects this package: high ▼ security
  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 72 to 76.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 66 to 69.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 59 to 62.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/agent-passport-system-mcp@8.1.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo agent-passport-system/agent-passport-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/agent-passport-system/agent-passport-mcp/.github/workflows/release.yml@refs/tags/v8.1.1
Rekor log index 3686579620
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:69def867768627dcf389cf0368c711623c8f1ef18f667d7cd8d4321c643d097c3f6e4c13ed9a0e5fc913c5473fd944e4dd52caa11e3eb95e458780896

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
postinstall Not reviewed echo '\n🔑 Agent Passport MCP installed! Run: npx agent-passport-system-mcp setup\n Or for zero-install remote: npx agent-passport-system-mcp setup --remote\n'

Background: Why install scripts are a supply-chain risk →

Dependencies 7 packages
Packages resolved 7
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 154 exposed · ~15,534 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
verify_governance_block ~88

Verify a governance block's signature, content hash, DID consistency and expiry against the original content. A block whose expiry cannot be read now fails closed rather than being treated as unexpired.

NameTypeReqDescription
blockstringyesGovernance block JSON string
contentstringyesOriginal content to verify against
publicKeystringyesPublisher's Ed25519 public key (hex)

No output schema declared.

No examples provided.

verify_issuer ~57

Verify that a passport was officially issued by AEOESS. Checks the issuer countersignature against the published AEOESS public key. Returns false for self-signed passports.

NameTypeReqDescription
passportobjectyesThe signed passport object to verify

No output schema declared.

No examples provided.

verify_rotation_chain ~48

Verify all rotation signatures in a DID document's rotation log. Returns true if the full chain is cryptographically valid.

NameTypeReqDescription
did_document–yesRotatableDIDDocument JSON object with rotationLog

No output schema declared.

No examples provided.

vouch_reputation ~79

Create a signed reputation summary that another gateway can import. Receipt history is not included.

NameTypeReqDescription
agent_idstringyes–
diversity_scorenumberyes–
gateway_idstringyes–
gateway_private_keystringyes–
tiernumberyes–
ttl_secondsnumber–Default 30 days

No output schema declared.

No examples provided.

Install

How do I install the Agent Passport System — Cryptographic Identity for AI Agents MCP server?

Agent Passport System — Cryptographic Identity for AI Agents runs locally as an npm package, launched with npx -y agent-passport-system-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · agent-passport-system-mcp

# add to Claude Code
claude mcp add agent-passport-system-agent-passport-mcp -- npx -y agent-passport-system-mcp
Common questions

What is the Agent Passport System — Cryptographic Identity for AI Agents MCP server?

Agent Passport System — Cryptographic Identity for AI Agents is an MCP server listed in the public MCP registry as io.github.agent-passport-system/agent-passport-mcp. Cryptographic identity, delegation, governance, and commerce for AI agents. 154 tools. This page covers its npm package (agent-passport-system-mcp).

Is the Agent Passport System — Cryptographic Identity for AI Agents MCP server safe to use?

Agent Passport System — Cryptographic Identity for AI Agents scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Agent Passport System — Cryptographic Identity for AI Agents MCP server expose?

Agent Passport System — Cryptographic Identity for AI Agents exposes 154 tools: list_profiles, list_tools_for_scope, identify, generate_keys, issue_passport, and 149 more. Their descriptions and schemas cost roughly 15,534 tokens of context every time the server is loaded.

Is the Agent Passport System — Cryptographic Identity for AI Agents MCP server still maintained?

Agent Passport System — Cryptographic Identity for AI Agents is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Agent Passport System — Cryptographic Identity for AI Agents MCP server under?

Agent Passport System — Cryptographic Identity for AI Agents declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Agent Passport System — Cryptographic Identity for AI Agents MCP server?

VerifyMCP ran 16 checks on Agent Passport System — Cryptographic Identity for AI Agents, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.