zunivo-mcp
MCP server that lets AI agents discover and pay for .agent services using USDC over x402, with daily budget controls and payment link creation.
README
zunivo-mcp
Give your AI agent working money on Arc.
An MCP server that lets any MCP client (Claude Desktop, Claude Code, etc.)
discover .agent services, pay for APIs over x402 in USDC, and issue payment
links — non-custodial, with a hard daily budget.
Tools
| tool | what it does |
|---|---|
zunivo_resolve_agent |
.agent name → on-chain card (payout address, endpoint, records) |
zunivo_list_agents |
public directory of callable .agent services |
zunivo_paid_fetch |
call a paid API — 402 handled, USDC paid within budget, receipt returned |
zunivo_create_payment_link |
invoice anyone: returns a pay URL |
zunivo_check_order |
order status + settling payments |
zunivo_spend_status |
today's budget: cap, spent, remaining |
Safety model
- 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). SetZUNIVO_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
.agentname, the recipient is pinned to the address the name resolves to on-chain — a malicious server cannot redirect funds.
Setup (Claude Desktop)
{
"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).
Example session
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.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.