
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)登錄記錄,並取得簽章證明與服務清單。