
Agent Passport
io.github.johnInarti由 GitHub 账号 johnInarti 发布v0.2.6更新于 Oct 24, 2026
Post-quantum (ML-DSA-65/FIPS-204) agent identity + AI-decision receipts, verifiable offline.
发布方自己的服务:Passport.Me
概览
为 AI 代理签发并验证后量子(ML-DSA-65)护照与决策收据,支持离线验签,并提供按次付费的 x402 证明工具。
- 可以做什么
- 验证护照与收据:重算内容哈希、离线校验 ML-DSA-65 签名并读取链上代理状态
- 为代理 ID 加签名断言签发护照,未付款时返回支付挑战
- 查询 FRC-55 公共注册表中的代理与统计信息,并列出实时证明目录
- 列出已注册代理,获取或验证代理清单,包括按地区签名的索引
- 按次购买后量子证明:封装消息、验证证明、KYA 校验、决策公证、来源证明、训练与 CBOM 封装
- 适用场景
- 当助手需要确认某个代理身份及特定断言在密码学上完整无损时适用;也适合在对话或代理流程中签发、公证和验证后量子签名的证明与收据。
- 运行要求
- 通过 npx 以 stdio 在本地运行 npm 包,需要 Node.js 以及访问 FractalAI 网页端点和 L1 JSON-RPC 节点的网络。无需账号或 API 密钥。可选环境变量 FRACTALAI_BASE_URL、FRACTALAI_RPC_URL、FRACTALAI_PINNED_RECEIPT_KEY 和 AGENT_PASSPORT_AUTODEMO。
安装
在 SourceWeft 中
- 打开 控制台中的 Agent Passport,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
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.
来源:README.md,提交 fe82838
工具
0版本历史
3- v0.2.6最新Oct 9, 2026
- v0.2.5Sep 30, 2026
- v0.2.3Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
其他 Passport 集成
Passport.Me
me.passport官方发布者
远程 MCP 端点,让助手访问用户的 Gmail、日历、云端硬盘、GitHub、Oura、钱包以及已确认的个人资料信息。
A2A Passport — one GTIN, one call, everything GSC knows, signed
由 GitHub 账号 greencore-solutions 发布
远程 MCP 服务器,为商品(GTIN)或零售横幅签发签名护照,内容实时取自 GSC 各枢纽,并提供列表与签名校验。

Agent Passport System — Cryptographic Identity for AI Agents
由 GitHub 账号 agent-passport-system 发布
通过 154 个工具为 AI 代理提供加密身份、签名护照、受限委派、治理记录与代理间消息传递能力。

Scopeblind Passport
由 GitHub 账号 tomjwxf 发布
为助手提供可移植的加密身份:Ed25519 密钥对与签名清单,通过 stdio 在本地运行。

Hive Passport
由 GitHub 账号 srotzin 发布
一个远程 MCP 服务器,让助手查询 Hive Knowledge Token(HKTN)注册记录,并获取签名证明与服务清单。