{"_id":"@agentpay-ai/mcp-server-arc","name":"@agentpay-ai/mcp-server-arc","dist-tags":{"latest":"0.1.11"},"versions":{"0.1.11":{"name":"@agentpay-ai/mcp-server-arc","version":"0.1.11","type":"module","exports":{".":"./src/index.ts","./hosted-arc-http":"./src/mcp/hosted-arc-http.ts","./hosted-arc-runtime":"./src/runtime/hosted-arc-wallet-runtime.ts","./default-hosted-arc-runtime":"./src/runtime/default-hosted-arc-runtime.ts","./hosted-arc-start":"./src/hosted-arc-start.ts"},"publishConfig":{"access":"public"},"scripts":{"start":"tsx src/index.ts","start:hosted-arc":"tsx src/hosted-arc-start.ts","test":"tsx --test \"src/**/*.test.ts\"","typecheck":"tsc -p ../../tsconfig.json --noEmit"},"dependencies":{"@agentpay-ai/shared-arc":"0.1.3","@circle-fin/adapter-viem-v2":"1.14.0","@circle-fin/app-kit":"1.10.0","@circle-fin/developer-controlled-wallets":"10.8.0","@circle-fin/x402-batching":"3.2.0","@modelcontextprotocol/sdk":"^1.29.0","@noble/hashes":"^2.2.0","@supabase/supabase-js":"^2.110.0","@x402/core":"^2.18.0","@x402/evm":"^2.18.0","ethers":"^6.17.0","viem":"2.55.8","zod":"^4.4.3"},"_id":"@agentpay-ai/mcp-server-arc@0.1.11","description":"AgentPay's MCP server exposes Arc payment tools over stdio or Streamable HTTP. It supports Circle Agent Wallet setup and funding, autonomous budget reads and withdrawal, direct USDC sends, invoice payments and payment requests, batch payouts, x402 paid-se","_nodeVersion":"22.23.0","_npmVersion":"10.9.8","dist":{"integrity":"sha512-kYpWsFNoN3eQRPcpgtvZZprroBqzeiE70zOHI/ye6TER3sKgt1DrAfc3Qt2rEZX86p8YetVSgS53TJCYpif90w==","shasum":"0f0597af2a9ef91a6332970b643a5f7d4a9196d6","tarball":"https://registry.npmjs.org/@agentpay-ai/mcp-server-arc/-/mcp-server-arc-0.1.11.tgz","fileCount":83,"unpackedSize":1143236,"signatures":[{"keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U","sig":"MEUCIGbSQnfzb9cGBLMAsBB21b/N4rYu13EZr36sTvC2kI1eAiEAq7mENZ1AoqR3SnAIULcdpppQlfRtBN/LJFrJCZwyenw="}]},"_npmUser":{"name":"zakyirsyaad","email":"zkyxentertain@gmail.com"},"directories":{},"maintainers":[{"name":"zakyirsyaad","email":"zkyxentertain@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages-npm-production","tmp":"tmp/mcp-server-arc_0.1.11_1785567974950_0.8213431662528823"},"_hasShrinkwrap":false}},"time":{"created":"2026-08-01T07:06:14.772Z","0.1.11":"2026-08-01T07:06:15.130Z","modified":"2026-08-01T07:06:15.373Z"},"maintainers":[{"name":"zakyirsyaad","email":"zkyxentertain@gmail.com"}],"description":"AgentPay's MCP server exposes Arc payment tools over stdio or Streamable HTTP. It supports Circle Agent Wallet setup and funding, autonomous budget reads and withdrawal, direct USDC sends, invoice payments and payment requests, batch payouts, x402 paid-se","readme":"# @agentpay-ai/mcp-server-arc\n\nAgentPay's MCP server exposes Arc payment tools over stdio or Streamable HTTP.\nIt supports Circle Agent Wallet setup and funding, autonomous budget reads and\nwithdrawal, direct USDC sends, invoice payments and payment requests, batch\npayouts, x402 paid-service discovery and purchase, unified balance and\nbridge/swap routes, ERC-8004 identity and reputation, activity receipts with\nArcscan proofs, ERC-8183 escrow jobs, and audit events.\n\nRun the complete config-free local Arc Agent Wallet surface:\n\n```bash\nnpx @agentpay-ai/agentpay-arc agent-wallet-mcp\n```\n\nIt registers 31 local Arc tools and persists process-owned operation state at\n`~/.agentpay/arc-state.json` with owner-only permissions. It accepts no tenant\nID and no hosted credential. Circle login, Terms, and OTP remain manual.\n\nThe package workspace `npm run start` command starts the inherited operator MCP.\nIts local/staging startup values are `SUPABASE_URL`,\n`SUPABASE_SERVICE_ROLE_KEY`, `CELO_RPC_URL`, and `EXECUTOR_PRIVATE_KEY` — the\nkeys `parseAgentPayEnv` requires to start this server. `ARC_TESTNET_RPC_URL` is\nrequired by the separate Arc production readiness gate, not by the local startup\nparser.\n\nAgent Wallet writes run through the safe Circle CLI adapter in\n`src/services/circle-cli.ts`: a fixed `circle` binary, `execFile` with\n`shell: false`, bounded output, timeouts, Zod response validation, secret and\nOTP rejection, option-injection rejection, and exactly one attempt for every\nmutation. The authenticated Circle CLI session stays on the user's machine and\nis never sent to a hosted surface.\n\nReads use an injected Viem public client pinned to Arc Testnet.\n\nFor the public x402 seller gate:\n\n```bash\nAGENTPAY_A2MCP_PAYMENT_ENABLED=true\nAGENTPAY_A2MCP_PAYMENT_PAY_TO=0x...\nAGENTPAY_A2MCP_PAYMENT_PRICE=$0.01\n```\n\nUnpaid calls receive HTTP `402` with `PAYMENT-REQUIRED`; verified calls are\naccepted only when their exact seller terms match configuration, settled before\nfulfilment, and returned with `PAYMENT-RESPONSE`. Durable lifecycle rows prevent\nduplicate fulfilment and write payer, payee, amount, asset, network, and\nsettlement transaction evidence to `payment_events`. `/healthz` is never\npaywalled.\n\nWhen `AGENTPAY_ERC8004_ENABLED=true`, the server exposes\n`/.well-known/agent-registration.json` without OAuth or x402. Publication\nrequires a non-zero deployed `AGENTPAY_ERC8004_AGENT_WALLET`;\n`AGENTPAY_ERC8004_AGENT_ID` is added only after the registry transaction\nconfirms. The document is schema-validated and does not advertise unimplemented\ntrust mechanisms.\n\nThe Arc buyer flow uses `search_paid_services` and `inspect_paid_service` for\nread-only discovery, then `pay_paid_service` executes `circle services pay`\nexactly once against the exact inspected quote. A quote that changed between\ninspection and execution stops the payment. Payment signatures are never\npersisted or returned.\n\nThe inherited Celo owner-signature tools remain registered as compatibility\ncontext on their separate operator surface. They do not define authorization\nfor Circle Agent Wallet spending.\n\nThat legacy path keeps its own x402 flow: search Bazaar with\n`search_x402_services`, prepare a result with `prepare_x402_service_request`\nwhen the user has no URL, and pass both `paymentRequired` and the exact request\nto `parse_x402_payment_required`. The URL, method, body, and safe headers are bound into the owner-signed purpose before payment.\n\nAfter completion,\n`retry_x402_request` accepts only that request shape, attaches the explicitly\nlabeled `agentpay-receipt` proof, and includes `payment-identifier` idempotency\ndata when advertised. This bridge is AgentPay-specific, not a universal\nexact-scheme signer.\n\nTwo environment validators currently coexist and disagree.\n\n`parseAgentPayEnv` in `src/runtime/agentpay-runtime.ts` is the startup path used\nby `mcp/http.ts` and `mcp/stdio.ts`. It still validates the inherited Celo\nenvironment and requires `AGENTPAY_HOME_CHAIN_ID=42220` plus the Celo setup URL\nin production. `validateProductionEnvironment` in\n`src/runtime/production-readiness.ts` expects the Arc environment instead:\n`AGENTPAY_HOME_CHAIN_ID=5042002`, an HTTPS `ARC_TESTNET_RPC_URL`, and the `/arc/`\npublic routes.\n\n`.env.example` carries the values that satisfy the startup parser, because a\nconfig that cannot start is worse than one that is not yet fully migrated.\n`scripts/env-example-runtime.test.ts` enforces this. Reconciling the two\nvalidators is a runtime change and is tracked separately.\n\n`AGENTPAY_ACCOUNT_VERSION=v2` and production-only Supabase aliases are required\nby both. A localhost RPC or a mismatched public route is rejected, and `/readyz`\nstays closed until every readiness check agrees.\n\nProduction stdio is disabled. Setup-web production deployment stays separately\ngated, and all broadcast or external provisioning actions require explicit\noperator approval.\n","readmeFilename":"README.md","_rev":"1-d2403e7d7b1945d3087241cafc9856ab"}