The zunivo-mcp server enables AI agents to interact with the Arc network by:
Discovering and resolving .agent services: List all available services (zunivo_list_agents) and look up an agent's payout address, endpoint, and manifest (zunivo_resolve_agent).
Making paid API calls: Automatically handle 402 Payment Required responses by paying the quoted USDC amount from the agent's wallet within budget limits, then retrying the request (zunivo_paid_fetch).
Creating payment links: Generate shareable invoices for any USDC amount payable to an .agent name or address (zunivo_create_payment_link).
Monitoring orders and spending: Check payment link status and on-chain settlements (zunivo_check_order), and track daily spending cap, spent amount, and remaining budget (zunivo_spend_status).
Secure operations: Private keys are kept securely, payments are capped per call and daily, and .agent recipients are pinned to on-chain addresses.
Provides tools for discovering and paying .agent services on the Arc blockchain, enabling AI agents to resolve .agent names, list available agents, call paid APIs with automatic USDC payments, create payment links, and check order and spending status.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@zunivo-mcp find me a crypto index feed and get the latest value"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Give your AI agent working money on Arc.
An MCP server that lets any MCP client (Claude, ChatGPT, Cursor, Gemini — anything that speaks MCP)
discover .agent services, pay for APIs over x402 in USDC, and issue payment
links — non-custodial, with a hard daily budget.
tool | what it does |
|
|
| public directory of callable |
| call a paid API — 402 handled, USDC paid within budget, receipt returned |
| invoice anyone: returns a pay URL |
| order status + settling payments |
| today's budget: cap, spent, remaining |
Related MCP server: opendexter
The private key lives in env — it is never shown to the model.
Every call is capped (ZUNIVO_MAX_PER_CALL, default 1 USDC) under a hard
daily budget (ZUNIVO_DAILY_CAP, default 5 USDC). Set ZUNIVO_SPEND_FILE
(e.g. ~/.zunivo-spend.json) so the budget survives restarts — strongly
recommended before pointing this at real funds.
Content returned by paid endpoints is untrusted input to your model. A malicious API could try to talk your agent into more paid calls — the daily cap is the backstop; keep it small.
When paying a .agent name, the recipient is pinned to the address the
name resolves to on-chain — a malicious server cannot redirect funds.
{
"mcpServers": {
"zunivo": {
"command": "npx",
"args": ["-y", "zunivo-mcp"],
"env": {
"AGENT_PK": "0x<agent wallet private key>",
"ZUNIVO_RECORDS_ADDRESS": "0x<ZunivoAgentRecords on Arc>",
"ZUNIVO_DAILY_CAP": "5",
"ZUNIVO_MAX_PER_CALL": "1"
}
}
}
}Fund the wallet with test USDC at https://faucet.circle.com (Arc Testnet).
You: find me a crypto index feed and get the latest value
Agent: lists agents → finds
data.agent→ paid_fetch/v1/index/crypto→ pays 0.05 USDC → returns the data + ArcScan receipt
Part of the Zunivo network — the payment layer for AI agents on Arc.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Monetize any MCP server: x402 paywall, pay-per-call billing in USDC on Base, agent marketplace.
Agent-commerce MCP server for x402/USDC payments and affiliate splits on Base.
Hosted AgentLux MCP server for marketplace, identity, creator, services, and social flows.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/zunivo-pay/zunivo-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server