{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm-xenarch-agent-mcp","slug":"xenarch-agent-mcp","name":"@xenarch/agent-mcp","type":"mcp","url":"https://github.com/xenarch-ai/xenarch-mcp#readme","page_url":"https://unfragile.ai/xenarch-agent-mcp","categories":["mcp-servers","app-builders"],"tags":["mcp","mcp-server","model-context-protocol","x402","http-402","ai-agent-payments","claude","cursor","langchain","crewai","usdc","base","base-l2","non-custodial","pay-per-crawl","cloudflare-alternative","tollbit-alternative","machine-to-machine-payments","pay-json","xenarch"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm-xenarch-agent-mcp__cap_0","uri":"capability://tool.use.integration.http.402.payment.gated.api.request.execution","name":"http 402 payment-gated api request execution","description":"Executes HTTP requests to APIs protected by HTTP 402 Payment Required status codes, automatically detecting payment requirements and routing requests through the MCP server's payment settlement layer. The server intercepts 402 responses, extracts payment metadata (amount, recipient, token), and initiates on-chain USDC micropayments on Base L2 before retrying the original request with proof-of-payment headers. This enables seamless agent-to-API interactions without manual payment handling or custodial intermediaries.","intents":["I want my Claude agent to call paid APIs without managing wallets or payment flows manually","I need to access HTTP 402-gated data sources from LangChain agents with automatic micropayment settlement","I want CrewAI to handle payment-required endpoints transparently as part of task execution"],"best_for":["AI agent developers building multi-step workflows that require paid data access","Teams deploying autonomous agents that need to access premium APIs at scale","Builders creating agent-to-agent payment networks without custodial intermediaries"],"limitations":["Requires target API to implement HTTP 402 Payment Required status and x402 payment metadata headers","Base L2 network dependency means settlement latency of 2-12 seconds per payment (vs instant local settlement)","No built-in retry logic for failed on-chain transactions — requires external orchestration for reliability","USDC only — no support for other stablecoins or native tokens without custom adapter implementation"],"requires":["MCP client integration (Claude, Cursor, LangChain, CrewAI with MCP support)","Base L2 RPC endpoint (public or private)","USDC balance in agent's wallet for micropayments","Target API must implement HTTP 402 Payment Required with x402 metadata headers"],"input_types":["HTTP request (method, URL, headers, body)","HTTP 402 response with x402 payment metadata (amount, recipient address, token contract)"],"output_types":["HTTP response from target API after payment settlement","Transaction hash of on-chain USDC transfer","Proof-of-payment headers for authenticated retry"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-xenarch-agent-mcp__cap_1","uri":"capability://tool.use.integration.non.custodial.usdc.micropayment.settlement.on.base.l2","name":"non-custodial usdc micropayment settlement on base l2","description":"Manages cryptographic signing and submission of USDC transfers to Base L2 blockchain without holding agent private keys or funds in escrow. The server accepts payment requests with recipient address and amount, constructs ERC-20 transfer transactions, signs them using the agent's provided key material (or external signer), and broadcasts to Base L2 RPC. Settlement completes on-chain with full transparency and auditability, with no platform-controlled custody or fee extraction.","intents":["I want my agent to pay for API access with cryptographic proof that cannot be disputed or reversed","I need to ensure payments settle directly on-chain without trusting a third-party payment processor","I want to audit all agent spending as immutable blockchain transactions"],"best_for":["Enterprise teams requiring audit trails and non-repudiation for agent spending","Decentralized application builders integrating agent payments into blockchain workflows","Organizations with strict compliance requirements around financial transaction custody"],"limitations":["Requires agent to maintain private key or external signer integration — no passwordless/social recovery options","Base L2 network congestion can cause 5-30 second settlement delays during peak usage","No built-in transaction retry or mempool monitoring — failed transactions require manual resubmission","USDC contract address must be manually configured per Base deployment; no automatic discovery"],"requires":["Agent private key or external signer (e.g., Ledger, Gnosis Safe) with signing capability","USDC token contract address on Base L2 (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913)","Base L2 RPC endpoint with eth_sendRawTransaction support","Sufficient USDC balance in agent wallet (minimum amount depends on API pricing)"],"input_types":["Payment request object: {recipient: address, amount: BigInt, tokenAddress: address}","Agent signing material: private key (hex string) or external signer interface"],"output_types":["Transaction hash (0x-prefixed hex string)","Transaction receipt with gas used and block number","Signed transaction object for external broadcast"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-xenarch-agent-mcp__cap_10","uri":"capability://data.processing.analysis.transaction.history.and.audit.logging","name":"transaction history and audit logging","description":"Maintains immutable transaction history of all USDC payments and API calls, logging transaction hash, timestamp, amount, recipient, and HTTP request/response details. The server stores logs in a queryable format (JSON, database) accessible through MCP tools, enabling agents and operators to audit spending, debug failed payments, and reconstruct payment flows. Logs include both on-chain transaction data and off-chain HTTP metadata.","intents":["I want to audit all agent spending and verify payments were made correctly","I need to debug failed payments and understand what went wrong","I want to reconstruct the full history of an agent's API interactions for compliance"],"best_for":["Enterprise teams with compliance and audit requirements","Builders creating agent-as-a-service platforms with billing","Organizations requiring detailed spending reports and analytics"],"limitations":["Logs are stored locally by default; no distributed audit trail or blockchain-based immutability","Log retention is configurable but not enforced — old logs can be deleted, breaking audit trail","No built-in log encryption or access control — requires external security measures","Log queries are synchronous and may be slow for large transaction volumes (100k+ transactions)"],"requires":["Storage backend for transaction logs (file system, database, or cloud storage)","Configured log retention policy","Query interface (MCP tools or direct database access)"],"input_types":["Transaction data: {txHash, timestamp, amount, recipient, gasUsed}","HTTP request/response metadata: {method, url, statusCode, headers}"],"output_types":["Transaction log entry with full metadata","Query results: filtered logs by date range, agent, recipient, or amount","Audit report: summary of spending by agent, API, or time period"],"categories":["data-processing-analysis","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-xenarch-agent-mcp__cap_11","uri":"capability://automation.workflow.configuration.management.for.payment.parameters.and.api.endpoints","name":"configuration management for payment parameters and api endpoints","description":"Provides centralized configuration for payment parameters (USDC amount, recipient address, spending limits), API endpoint mappings, and RPC provider settings. Configuration is loaded from environment variables, JSON files, or environment-specific profiles, allowing operators to adjust payment rules without restarting the MCP server. Supports hot-reloading of configuration changes for zero-downtime updates.","intents":["I want to change payment amounts or spending limits without restarting the server","I need to configure different payment rules for different APIs or agents","I want to manage RPC endpoints and failover settings centrally"],"best_for":["Operators managing production MCP servers with multiple agents","Teams deploying agents to multiple environments (dev, staging, prod) with different payment rules","Builders creating agent platforms with configurable payment policies"],"limitations":["Configuration validation is basic; invalid configs may not be caught until runtime","Hot-reloading is not atomic — in-flight transactions may use old configuration","No support for configuration versioning or rollback — changes are immediate","Environment variable expansion is limited; no support for secrets management (e.g., HashiCorp Vault)"],"requires":["Configuration file (JSON, YAML, or environment variables)","Restart or hot-reload capability for configuration changes"],"input_types":["Configuration object: {payment: {amount, recipient}, spending: {limit}, rpc: {endpoints}}","Environment-specific overrides"],"output_types":["Loaded configuration object","Configuration validation result: {valid: boolean, errors?: string[]}"],"categories":["automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-xenarch-agent-mcp__cap_2","uri":"capability://tool.use.integration.mcp.protocol.integration.for.claude.cursor.langchain.and.crewai","name":"mcp protocol integration for claude, cursor, langchain, and crewai","description":"Exposes HTTP 402 payment handling and USDC settlement as MCP tools that Claude, Cursor, LangChain, and CrewAI can discover and invoke through the standard Model Context Protocol. The server implements MCP tool schema definitions for payment-gated requests and settlement operations, allowing agents to treat paid API access as first-class capabilities alongside native tools. Integration requires no agent-side SDK changes — agents interact via standard MCP tool-calling semantics.","intents":["I want Claude to call paid APIs as naturally as it calls free APIs, without special payment handling code","I need LangChain agents to compose paid API calls into multi-step workflows without custom integrations","I want CrewAI to manage payments across multiple agents and tasks transparently"],"best_for":["AI agent developers using Claude, Cursor, LangChain, or CrewAI who want to access paid APIs","Teams building multi-agent systems where agents need to pay for shared resources","Developers who want to avoid writing custom payment logic in agent code"],"limitations":["Requires MCP client support — not all LLM platforms have MCP integration (e.g., OpenAI API lacks native MCP)","Tool discovery latency adds ~100-200ms per agent startup as MCP schema is fetched","No built-in rate limiting or quota management — agents can exhaust budgets without guardrails","MCP protocol version pinning required; incompatible with older MCP client versions"],"requires":["MCP-compatible client: Claude (via Claude Desktop or API with MCP support), Cursor, LangChain (with MCP integration), or CrewAI (with MCP support)","MCP server running locally or remotely with network accessibility","MCP client configuration pointing to xenarch-mcp server endpoint"],"input_types":["MCP tool call request with tool name and arguments (JSON)","Tool schema definition (JSON Schema format)"],"output_types":["MCP tool result with HTTP response or payment settlement confirmation","Tool error response with diagnostic information"],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-xenarch-agent-mcp__cap_3","uri":"capability://data.processing.analysis.automatic.http.402.response.detection.and.payment.metadata.extraction","name":"automatic http 402 response detection and payment metadata extraction","description":"Intercepts HTTP responses with 402 Payment Required status codes and extracts payment metadata from response headers (x402-amount, x402-recipient, x402-token) to determine payment requirements. The server parses metadata, validates format and values, and automatically initiates payment settlement without requiring the agent to manually inspect headers or construct payment requests. This enables transparent payment handling where agents see paid API access as a seamless extension of normal HTTP requests.","intents":["I want my agent to automatically detect when an API requires payment and handle it without explicit payment logic","I need to extract payment requirements from API responses and route them to the settlement layer","I want agents to retry failed requests after payment without manual intervention"],"best_for":["Developers building agents that access multiple paid APIs with varying payment schemes","Teams deploying agents to production where manual payment handling is not feasible","Builders creating agent-to-API networks where payment requirements are dynamic"],"limitations":["Requires target API to implement HTTP 402 with x402 metadata headers — no support for proprietary payment schemes","No support for payment negotiation or tiered pricing — assumes fixed amount per request","Metadata parsing is strict; malformed headers cause request failure rather than graceful degradation","No caching of payment requirements — each request triggers new 402 detection and payment"],"requires":["Target API implementing HTTP 402 Payment Required status code","x402 metadata headers in 402 response: x402-amount, x402-recipient, x402-token","MCP server with HTTP request interception capability"],"input_types":["HTTP response with 402 status code","Response headers containing x402 metadata (amount, recipient, token)"],"output_types":["Parsed payment metadata object: {amount: string, recipient: address, token: address}","Validation result: {valid: boolean, error?: string}","Retry request with proof-of-payment headers"],"categories":["data-processing-analysis","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-xenarch-agent-mcp__cap_4","uri":"capability://automation.workflow.multi.framework.agent.orchestration.with.unified.payment.context","name":"multi-framework agent orchestration with unified payment context","description":"Manages payment state and context across multiple agent frameworks (Claude, LangChain, CrewAI) executing in the same workflow, ensuring consistent wallet management, balance tracking, and transaction history. The server maintains a unified payment ledger accessible to all agents, preventing double-spending and enabling cross-agent payment coordination. Agents can query remaining balance, transaction history, and payment status through MCP tools without framework-specific code.","intents":["I want multiple agents (Claude, LangChain, CrewAI) to share a payment budget and coordinate spending","I need to track total spending across agents and enforce budget limits","I want agents to query payment status and balance without accessing blockchain directly"],"best_for":["Teams running multi-agent systems where agents need to coordinate on shared resources","Builders creating agent swarms with centralized payment management","Organizations requiring unified audit trails across multiple agent frameworks"],"limitations":["Requires all agents to connect to the same MCP server instance — no distributed payment ledger","No built-in consensus mechanism for concurrent payments — requires external locking for safety","Payment ledger is in-memory by default; no persistence across server restarts without custom storage","No support for hierarchical budgets or per-agent spending limits — all agents share global balance"],"requires":["Single MCP server instance accessible to all agents","Shared wallet/private key for all agents (or external signer with multi-agent support)","Network connectivity between all agent frameworks and MCP server"],"input_types":["Agent identity/name for ledger tracking","Payment request with agent context","Balance query request"],"output_types":["Unified payment ledger entry with timestamp, agent, amount, recipient","Current balance and spending summary","Transaction history filtered by agent"],"categories":["automation-workflow","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-xenarch-agent-mcp__cap_5","uri":"capability://data.processing.analysis.proof.of.payment.header.generation.and.validation","name":"proof-of-payment header generation and validation","description":"Generates cryptographic proof-of-payment headers (e.g., transaction hash, signature) after successful USDC settlement and attaches them to retry requests, allowing target APIs to verify that payment was completed. The server constructs headers containing transaction hash, block number, and optional signature proof, which APIs can validate against Base L2 blockchain state. This enables APIs to trust that payment occurred without querying the blockchain themselves.","intents":["I want to prove to an API that payment was completed without the API querying the blockchain","I need to attach payment proof to requests so APIs can validate payment synchronously","I want to enable APIs to verify payment without adding blockchain query latency"],"best_for":["API providers implementing HTTP 402 who want to validate payments without blockchain queries","Builders creating payment-gated services that need fast payment verification","Teams building agent-to-API networks with strict latency requirements"],"limitations":["Proof validation requires API to trust the MCP server's signature — no decentralized verification without blockchain query","Transaction hash alone is not cryptographic proof of payment — requires API to query blockchain or trust MCP signature","No support for offline proof generation — requires active connection to Base L2 RPC","Proof expires if transaction is reorged or dropped from mempool — no long-term proof validity"],"requires":["Successful USDC transaction on Base L2 with transaction hash","Base L2 RPC endpoint for block number and transaction confirmation","API endpoint that accepts and validates proof-of-payment headers"],"input_types":["Transaction hash from USDC settlement","Block number and confirmation count","Optional: signature material for cryptographic proof"],"output_types":["HTTP headers: x402-tx-hash, x402-block, x402-signature","Proof validation result: {valid: boolean, reason?: string}"],"categories":["data-processing-analysis","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-xenarch-agent-mcp__cap_6","uri":"capability://automation.workflow.agent.wallet.balance.tracking.and.spending.limits","name":"agent wallet balance tracking and spending limits","description":"Maintains real-time balance tracking for agent wallets by monitoring USDC transfers and caching balance state, allowing agents to query remaining funds and enforce spending limits before initiating payments. The server tracks balance changes from settlement transactions, updates cached state, and prevents payments that would exceed configured limits. Agents can query balance through MCP tools without blockchain queries, reducing latency.","intents":["I want my agent to check its balance before attempting to pay for an API call","I need to enforce spending limits so agents don't exhaust budgets on a single API","I want to track spending over time and alert when balance is low"],"best_for":["Teams deploying agents with limited budgets who need guardrails against overspending","Builders creating agent-as-a-service platforms with per-agent billing","Organizations requiring spending controls and budget enforcement"],"limitations":["Balance cache can become stale if external transfers occur outside MCP server — requires periodic blockchain sync","No support for multi-sig wallets or shared custody — assumes single-key agent wallets","Spending limits are enforced locally; no on-chain enforcement or rollback if limit is exceeded","No support for time-based budgets (e.g., daily limits) — only absolute balance limits"],"requires":["Agent wallet address with USDC balance on Base L2","Base L2 RPC endpoint for balance verification","Configured spending limit (in USDC amount)"],"input_types":["Agent wallet address","Spending limit amount (BigInt or string)","Balance query request"],"output_types":["Current balance (BigInt)","Remaining budget after limit","Spending summary (total spent, transaction count)"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-xenarch-agent-mcp__cap_7","uri":"capability://automation.workflow.http.request.retry.with.payment.aware.backoff","name":"http request retry with payment-aware backoff","description":"Implements intelligent retry logic that distinguishes between payment failures (402 responses) and transient errors (5xx, timeouts), applying different backoff strategies for each. After successful payment settlement, the server retries the original request with proof-of-payment headers; if retry fails, it applies exponential backoff without re-attempting payment. This prevents redundant payments while ensuring requests eventually succeed or fail cleanly.","intents":["I want my agent to retry failed requests after payment without paying multiple times","I need to distinguish between payment failures and API errors to handle them differently","I want intelligent backoff that doesn't waste payments on transient API errors"],"best_for":["Developers building resilient agents that access unreliable paid APIs","Teams deploying agents in production where retry logic is critical","Builders creating payment-gated APIs who want to minimize failed payment attempts"],"limitations":["Retry logic is stateless — no persistence across server restarts, so in-flight retries are lost","No support for circuit breakers or adaptive backoff based on API health — uses fixed exponential backoff","Maximum retry count is hardcoded; no per-request retry configuration","No support for idempotency keys — retries may cause duplicate API side effects if API is not idempotent"],"requires":["HTTP request with method, URL, headers, and body","Target API that supports HTTP 402 and retries with proof-of-payment headers","Configured retry count and backoff parameters"],"input_types":["HTTP request object","HTTP response with 402 or error status","Payment settlement result"],"output_types":["Successful HTTP response after retry","Final error response if retries exhausted","Retry attempt log with timestamps and backoff delays"],"categories":["automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-xenarch-agent-mcp__cap_8","uri":"capability://automation.workflow.base.l2.rpc.endpoint.abstraction.and.failover","name":"base l2 rpc endpoint abstraction and failover","description":"Abstracts Base L2 RPC interactions behind a configurable endpoint layer with automatic failover to secondary endpoints if primary fails. The server supports multiple RPC providers (Alchemy, Infura, public endpoints) and switches between them transparently on connection failures, ensuring payment settlement continues even if a single RPC provider is down. Implements connection pooling and health checks to detect failures quickly.","intents":["I want my agent payments to be resilient to RPC provider outages","I need to use multiple RPC providers without changing agent code","I want automatic failover so payment settlement doesn't block on a single provider"],"best_for":["Teams deploying agents in production where RPC reliability is critical","Builders creating payment infrastructure that needs high availability","Organizations using multiple RPC providers for redundancy"],"limitations":["Failover adds ~500ms-2s latency on RPC provider failure detection","No support for RPC provider load balancing — uses simple failover, not round-robin","Health checks are periodic; transient failures may not be detected immediately","No support for RPC-specific features (e.g., Alchemy's enhanced APIs) — abstracts to common interface"],"requires":["One or more Base L2 RPC endpoints (public or private)","Network connectivity to RPC providers","Configured failover endpoint list"],"input_types":["RPC method name and parameters (e.g., eth_sendRawTransaction)","Endpoint configuration with URLs and health check intervals"],"output_types":["RPC response from primary or failover endpoint","Endpoint health status and failover logs"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-xenarch-agent-mcp__cap_9","uri":"capability://data.processing.analysis.transaction.gas.estimation.and.cost.prediction","name":"transaction gas estimation and cost prediction","description":"Estimates gas costs for USDC transfers on Base L2 before submission, predicting total transaction cost (gas * gwei) and allowing agents to make informed payment decisions. The server calls eth_estimateGas with the constructed transaction, fetches current Base L2 gas price, and returns cost estimate in USDC equivalent. Agents can use estimates to decide whether to proceed with payment or seek alternative APIs.","intents":["I want to know the total cost of a payment before committing to it","I need to compare payment costs across multiple APIs and choose the cheapest","I want to avoid overpaying for gas on congested networks"],"best_for":["Cost-conscious agent developers who want to optimize spending","Teams building agent-to-API networks with price transparency","Builders creating agent routing logic that considers payment costs"],"limitations":["Gas estimates are point-in-time and may be inaccurate if network conditions change between estimate and submission","No support for EIP-1559 dynamic fees — assumes fixed gas price, may underestimate on congested networks","Estimates assume standard USDC transfer; custom token contracts may have different gas costs","No support for batching multiple payments to amortize gas costs"],"requires":["Base L2 RPC endpoint with eth_estimateGas support","Current Base L2 gas price (fetched via eth_gasPrice)","USDC token contract address and transfer function signature"],"input_types":["Transaction object: {to: address, from: address, data: hex}","Token contract address for USDC"],"output_types":["Gas estimate (BigInt, in wei)","Gas price (BigInt, in wei)","Total cost in USDC (string or BigInt)","Cost breakdown: {gas: BigInt, gasPrice: BigInt, totalWei: BigInt, totalUSDC: string}"],"categories":["data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":38,"verified":false,"data_access_risk":"high","permissions":["MCP client integration (Claude, Cursor, LangChain, CrewAI with MCP support)","Base L2 RPC endpoint (public or private)","USDC balance in agent's wallet for micropayments","Target API must implement HTTP 402 Payment Required with x402 metadata headers","Agent private key or external signer (e.g., Ledger, Gnosis Safe) with signing capability","USDC token contract address on Base L2 (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913)","Base L2 RPC endpoint with eth_sendRawTransaction support","Sufficient USDC balance in agent wallet (minimum amount depends on API pricing)","Storage backend for transaction logs (file system, database, or cloud storage)","Configured log retention policy"],"failure_modes":["Requires target API to implement HTTP 402 Payment Required status and x402 payment metadata headers","Base L2 network dependency means settlement latency of 2-12 seconds per payment (vs instant local settlement)","No built-in retry logic for failed on-chain transactions — requires external orchestration for reliability","USDC only — no support for other stablecoins or native tokens without custom adapter implementation","Requires agent to maintain private key or external signer integration — no passwordless/social recovery options","Base L2 network congestion can cause 5-30 second settlement delays during peak usage","No built-in transaction retry or mempool monitoring — failed transactions require manual resubmission","USDC contract address must be manually configured per Base deployment; no automatic discovery","Logs are stored locally by default; no distributed audit trail or blockchain-based immutability","Log retention is configurable but not enforced — old logs can be deleted, breaking audit trail","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.09247959957979121,"quality":0.49,"ecosystem":0.7000000000000001,"match_graph":0.25,"freshness":0.6,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:23.902Z","last_scraped_at":"2026-04-22T08:08:13.653Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":145,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=xenarch-agent-mcp","compare_url":"https://unfragile.ai/compare?artifact=xenarch-agent-mcp"}},"signature":"uzQ4jXmMH2VzNk2E4rhoKcj94aadZS+PrSrCuHOqQXsGXAi7bXDwbKAAtZpex7AlzJMCvNoj2VU5ZE3XqyRXDw==","signedAt":"2026-06-21T22:50:11.588Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/xenarch-agent-mcp","artifact":"https://unfragile.ai/xenarch-agent-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=xenarch-agent-mcp","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}