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 產生的概覽

為 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。
安裝前請注意
付費工具需在 Base 上以 USDC 付款(例如 issue_passport 為 0.05 美元),需要相容的 x402 錢包用戶端並設定支出策略;伺服器不持有資金但會轉送付款。有效的護照並不證明斷言為真或代理決策正確,評分也只是登錄表自身的計數。首次啟動會向 FractalAI 節點發出一次真實呼叫,除非將 AGENT_PASSPORT_AUTODEMO 設為 0。簽章驗證並非 FIPS 認證模組。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Agent Passport,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

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.

bash
npx @fractalai/agent-passport-mcp

Tools

ToolCostWhat it REALLY does today
verify_passportfreeGiven an attestation permalink / 0x hash (and optionally the receipt JSON): recomputes the content hashes, reconstructs the exact canonical signed message, verifies the ML-DSA-65 (NIST FIPS 204) signature 100% offline against the published /api/x402/receipt-key, verifies the Dilithium-2 signature server-assisted with a tamper negative-control, and reads the agent's FRC-55 on-chain state. Returns { valid, algorithm, checks[], anchored, decision, agent }.
issue_passportx402 ($0.05 USDC)Binds an agent_id + a signed assertion + a re-verifiable permalink: resolves the agent on the FRC-55 registry (if it's an on-chain id) and seals the assertion through the real x402 attest-decision flow (Dilithium-2 signed, Black-Box chained, anchored on the L1). Without a payment_tx_hash it returns the payment challenge — it never fabricates a passport.
lookup_agentfreePublic FRC-55 registry read on the live node: fractal_getAgent for one agent (name, owner, status, model, total_calls, rating, total_ratings, created_at) or fractal_listAgents for all, always with fractal_getAgentStats.
list_fractalai_proofsfreeSelf-describing discovery: reads the canonical /.well-known/x402.json live and returns the full proof catalog (price, algorithm, endpoint, what each proves) — one call maps the whole x402 surface and auto-heals if it changes, since it reflects the live source of truth rather than a hardcoded copy.
list_agentsfreeFractal Agent Commons: fetches the ML-DSA-65-signed index of registered agents (/.well-known/agents.json, only agents whose latest manifest is current: key = the agent's current key on the node, passport verifies, FRC-55 Active, not expired) and verifies the index signature offline against the notary key pinned in this package. include_all adds non-current agents with their reasons. region (ISO 3166-1 alpha-2, e.g. CO) fetches the separately signed REGIONAL index (?region=CO) and requires its signed scope.region to equal the request — a global index re-served for a regional request is index_scope_mismatch, never a fallback.
get_agent_manifestfreeFetches an agent's fractalai-agent-manifest/1 (current, or an immutable version), recomputes manifest_id (JCS) and verifies the agent's ML-DSA-65 signature only with the key the registry/node reports as the agent's current key — never the manifest's embedded key alone.
verify_agent_manifestfreeOffline verification of a manifest JSON you were handed: alg anchored to ML-DSA-65 (1952-byte key / 3309-byte signature, nothing inferred from sizes), JCS manifest_id, lifetime ≤ 30 d. Verification key = pubkey_b64url you supply (fully offline), else the agent's current key from the registry/node, used only if it equals the embedded key.

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.

ToolPriceWhat it does
seal_ml_dsa$0.02Post-quantum signature over any message/hash — durable, quantum-safe, offline-verifiable.
verify_proof$0.01Verify a signature (auto-detects ML-DSA-65 or Dilithium-2). The floor primitive for any proof pipeline.
verify_agent_kya$0.03Know-Your-Agent: verify another agent's credential + live FRC-55 reputation before you trust/pay it.
notarize_decision$0.05Notarize an AI decision (input, output, model) → auditable, non-repudiable, on-chain (EU AI Act Art. 12).
prove_provenance$0.05Provenance seal over a dataset/content hash + drand timestamp + on-chain anchor.
attest_training$0.05C2PA training-provenance manifest for a model, post-quantum signed.
seal_cbom$0.05Seal a CycloneDX CBOM (crypto inventory) — CNSA 2.0 / procurement PQC-readiness disclosure.

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_passport does not register reputation;
  • lookup_agent ratings 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_dsa65 detached signature is delivered to pilot integrations today (pass it via the receipt argument) 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:

bash
cd integrations/agent-passport-mcpnpm installnpm run build      # tsc → dist/npm test           # handshake: server stands up, tools respond, ML-DSA-65 round-trips

Configure in an MCP client

Claude Desktop (claude_desktop_config.json)

json
{  "mcpServers": {    "agent-passport": { "command": "npx", "args": ["-y", "@fractalai/agent-passport-mcp"] }  }}

Environment

  • FRACTALAI_BASE_URL — web endpoint base (default https://fractalai.net.co).
  • FRACTALAI_RPC_URL — L1 JSON-RPC node (default https://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 to 0 to 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:

python
from langchain_mcp_adapters.client import MultiServerMCPClientclient = MultiServerMCPClient({"agent_passport": {"command": "npx", "args": ["-y", "@fractalai/agent-passport-mcp"], "transport": "stdio"}})tools = await client.get_tools()   # verify_passport, issue_passport, lookup_agentagent = create_react_agent(model, tools)await agent.ainvoke({"messages": "Verify passport https://fractalai.net.co/attestation/0x…"})

CrewAI (Python) — crewai-tools MCP adapter:

python
from crewai_tools import MCPServerAdapterfrom mcp import StdioServerParametersparams = StdioServerParameters(command="npx", args=["-y", "@fractalai/agent-passport-mcp"])with MCPServerAdapter(params) as tools:    Agent(role="Auditor", tools=tools, goal="Verify agent passports", backstory="...")

AutoGen (Python) — autogen-ext MCP workbench:

python
from autogen_ext.tools.mcp import StdioServerParams, mcp_server_toolsparams = StdioServerParams(command="npx", args=["-y", "@fractalai/agent-passport-mcp"])tools = await mcp_server_tools(params)   # verify_passport / issue_passport / lookup_agentagent = AssistantAgent("auditor", model_client=client, tools=tools)

OpenAI Agents SDK (Python):

python
from agents import Agentfrom agents.mcp import MCPServerStdioasync with MCPServerStdio(params={"command": "npx", "args": ["-y", "@fractalai/agent-passport-mcp"]}) as server:    agent = Agent(name="Auditor", instructions="Verify and issue agent passports.", mcp_servers=[server])

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:

js
import { ml_dsa65 } from '@noble/post-quantum/ml-dsa.js';
// 1. Pin the trusted key(s) from the signed, ML-DSA-65-governed directory (fetch once, cache):const dir = await (await fetch('https://fractalai.net.co/.well-known/x402-receipt-keys')).json();// (dir.signature / dir.directory_public_key let you verify the directory itself is unmodified —// see @fractalai/pqc-agent-receipts-conformance for a full conformance-checked example.)
// 2. Given ANY served receipt — e.g. the response of a paid /api/x402/* call — verify offline:const { signature, signed_message, public_key } = receipt; // fields returned by every x402 routeconst valid = ml_dsa65.verify(  Buffer.from(signature, 'base64'),  new TextEncoder().encode(signed_message),  Buffer.from(public_key, 'base64'),);console.log('receipt valid:', valid); // true only if the exact bytes were signed by that key

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
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

3
  1. v0.2.6最新Oct 9, 2026
  2. v0.2.5Sep 30, 2026
  3. v0.2.3Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Passport 整合