
Agent Passport
io.github.johnInartiPublished by GitHub account johnInartiv0.2.6Updated Oct 24, 2026
Post-quantum (ML-DSA-65/FIPS-204) agent identity + AI-decision receipts, verifiable offline.
The publisher's own server: Passport.Me
Overview
Issues and verifies post-quantum (ML-DSA-65) passports and AI-decision receipts for agents, with offline signature checks and paid x402 proof tools.
- What you can do
- Verify passports and receipts: recompute hashes, check ML-DSA-65 signatures offline and read on-chain agent state
- Issue a passport for an agent id plus signed assertion, returning a payment challenge when unpaid
- Look up agents and stats in the public FRC-55 registry, and list the live proof catalog
- List registered agents and fetch or verify agent manifests, including region-scoped indexes
- Buy post-quantum proofs per call: seal messages, verify proofs, KYA checks, decision notarization, provenance, training and CBOM seals
- When to use it
- Useful when an assistant must check that an agent identity and a specific attested assertion are cryptographically intact, or when you want to issue, notarize or verify post-quantum signed proofs and receipts from a chat or agent workflow.
- Requirements
- Runs locally over stdio via npx from the npm package; Node.js and network access to the FractalAI web endpoints and L1 JSON-RPC node are needed. No account or API key. Optional environment variables FRACTALAI_BASE_URL, FRACTALAI_RPC_URL, FRACTALAI_PINNED_RECEIPT_KEY and AGENT_PASSPORT_AUTODEMO.
Installation
In SourceWeft
- Open Agent Passport in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Agent Passport — MCP server
The free tool a developer drops in, in ~5 lines, to issue and independently verify a verifiable passport for an AI agent — over the Model Context Protocol, so it works in LangChain, CrewAI, AutoGen, OpenAI Agents, Claude Desktop — anything that speaks MCP.
It talks to the real, public FractalAI deployment: the live L1 JSON-RPC node at
https://api.fractalai.net.co (FRC-55 agent registry) and the web endpoints at
https://fractalai.net.co (attestations, receipt key, x402). Nothing here is mocked.
Tools
x402-paid tools (v0.2.0) — post-quantum proofs, pay-per-call
The 8 supported FractalAI x402 routes are surfaced as auto-payable MCP tools. An x402-aware wallet client
signs an EIP-3009 authorization and pays in USDC on Base using the standard _meta["x402/payment"]
convention. Each served signature is ML-DSA-65 / Dilithium-3 (NIST FIPS 204) and verifiable
offline; each also attempts an on-chain anchor on FractalAI's L1 (the anchor signature is
Dilithium-2 / ML-DSA-44-class, pending the gated consensus cut-over — see "Honest scope"). Uses the
FIPS-204-standardized algorithm via audited @noble/post-quantum (not a FIPS-validated CMVP module).
Call any tool without payment first to get the exact price + payment challenge.
Payment note: paid tools accept the standard _meta["x402/payment"] (auto-pay) and also a plain
payment string arg (base64 X-PAYMENT) as a universal fallback. Nothing is fabricated — the tools
proxy to the live routes and relay exactly what they return, honest scope included.
Honest scope (read this — project Regla 4)
A valid passport proves an identity + a specific attested assertion are cryptographically intact over the exact signed bytes, that the record is internally consistent, and that it is anchored on FractalAI's L1. It does NOT prove:
- that the assertion is true, or that the agent's decision/action was correct;
- any decentralized / consensus-scored reputation —
issue_passportdoes not register reputation; lookup_agentratings are the registry's own counters as reported by the node, not an independent audit.
Signature checks are labeled by trust model: [independent] = computed locally, does not trust
the FractalAI server (the offline ML-DSA-65 check, content hashes); [server-assisted] = calls a
FractalAI endpoint (the Dilithium-2 /api/proofmind/verify check). The ML-DSA-65 verification uses the
FIPS-204-standardized algorithm via the audited @noble/post-quantum library — this is not a
FIPS-validated (CMVP) module.
What is real today vs roadmap
- Real today: offline ML-DSA-65 verification against the published key; server-assisted Dilithium-2 verification + tamper control; FRC-55 on-chain agent reads; the real x402 402→pay→seal flow for issuing.
- Roadmap (not claimed as done): server-issued attestations are currently self-signed by the server
key and anchored on FractalAI's own L1; full on-chain consensus validation and a decentralized,
consensus-scored reputation are future milestones. The
ml_dsa65detached signature is delivered to pilot integrations today (pass it via thereceiptargument) and is being rolled into the public API.
Use it
You don't need to install or build anything — npx fetches and runs the published package
directly (see the config block above). No account, no API key.
Contributing (building from source)
Only needed if you're working on the server itself, inside the FractalAI monorepo:
Configure in an MCP client
Claude Desktop (claude_desktop_config.json)
Environment
FRACTALAI_BASE_URL— web endpoint base (defaulthttps://fractalai.net.co).FRACTALAI_RPC_URL— L1 JSON-RPC node (defaulthttps://api.fractalai.net.co).AGENT_PASSPORT_AUTODEMO— on connect, the server makes one real, free call to the live node (fractal_getAgentStats) and logs the result to stderr, so you can see immediately that this isn't mocked. Fire-and-forget — it never delays or blocks the MCP handshake. Set to0to disable.
5-line examples (per framework)
All of these run the same MCP server (npx @fractalai/agent-passport-mcp) over stdio and call the tools.
LangChain (Python) — langchain-mcp-adapters:
CrewAI (Python) — crewai-tools MCP adapter:
AutoGen (Python) — autogen-ext MCP workbench:
OpenAI Agents SDK (Python):
Independent, no-framework verification
Because a receipt is designed for third-party verification, you don't even need this server (or
any FractalAI code) to check one — just @noble/post-quantum and the public key directory:
For a battle-tested, adversarially-vectored version of this same check (genuine + tampered +
wrong-key forgery vectors across x402/SAR/ACP/JOSE/W3C-VC profiles), see
@fractalai/pqc-agent-receipts-conformance
(npx pqc-receipt-check).
License
MIT
Automated commerce onboarding (0.2.5)
Call list_fractalai_proofs first. It returns the live catalog, payment requirements, input schemas and a supported MCP tool or an explicit HTTP integration path. Prices in discovery are informational: request a fresh challenge before authorizing a purchase. The MCP server does not hold buyer funds; automatic payment requires a compatible wallet client with a configured spending policy.
witness_payment accepts seal_body, optional request_binding and settlement_tx, and the standard x402 payment metadata. Build bound requests with the witness SDK; persist the request and authorization before submitting. The bridge forwards once and never creates a replacement authorization after a timeout. Verify delivered evidence using an independently trusted key. This tool does not replace the buyer's durable recovery store.
Run npm run test:commerce for deterministic MCP transport tests without network or payments.
Source: README.md at commit fe82838
Tools
0Version history
3- v0.2.6LatestOct 9, 2026
- v0.2.5Sep 30, 2026
- v0.2.3Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Passport integrations
Passport.Me
me.passportOfficial publisher
Remote MCP endpoint that gives an assistant access to a user's Gmail, Calendar, Drive, GitHub, Oura, wallet and confirmed profile facts.
A2A Passport — one GTIN, one call, everything GSC knows, signed
Published by GitHub account greencore-solutions
Remote MCP server that issues signed passports for products (GTIN) or retail banners, composed live from GSC hubs, with listing and signature verification.

Agent Passport System — Cryptographic Identity for AI Agents
Published by GitHub account agent-passport-system
Gives AI agents cryptographic identity, signed passports, scoped delegations, governance records and agent-to-agent messaging through 154 tools.

Scopeblind Passport
Published by GitHub account tomjwxf
Gives an assistant a portable cryptographic identity: Ed25519 keypairs and signed manifests, run locally over stdio.

Hive Passport
Published by GitHub account srotzin
A remote MCP server that lets an assistant look up Hive Knowledge Token (HKTN) registry records and fetch signed proofs and service manifests from the Hive Pass