zunivo-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENT_PK | Yes | Agent wallet private key (never shown to the model) | |
| ZUNIVO_DAILY_CAP | No | Hard daily budget in USDC (default 5) | 5 |
| ZUNIVO_SPEND_FILE | No | Path to spend file for persistent budget (e.g. ~/.zunivo-spend.json) | ~/.zunivo-spend.json |
| ZUNIVO_MAX_PER_CALL | No | Maximum spend per call in USDC (default 1) | 1 |
| ZUNIVO_RECORDS_ADDRESS | Yes | ZunivoAgentRecords contract address on Arc |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| zunivo_resolve_agentA | Resolve a .agent name to its on-chain agent card: payout address, service endpoint, x402 manifest, description. Accepts 'data.agent', '@data' or 'data'. |
| zunivo_list_agentsA | List every .agent name that has published a callable service (the public agent directory on Arc). |
| zunivo_paid_fetchA | Call a paid HTTP API. If the server responds 402, pay the quoted USDC price from the agent wallet (within budget) and retry automatically. Target is either a full url, or an agent name + path. Returns status, body and the payment receipt if one was made. |
| zunivo_create_payment_linkA | Create a Zunivo payment link (invoice): anyone opening it can pay the given USDC amount to a .agent name or 0x address. Returns the pay URL and order id. |
| zunivo_check_orderA | Check a payment link / order: status (unpaid or paid) and the on-chain payments that settled it. |
| zunivo_spend_statusA | Show today's spending budget for the agent wallet: daily cap, spent so far, remaining, per-call ceiling. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a unique, clearly defined purpose: listing agents, resolving agent details, making paid requests, checking order status, creating payment links, and reviewing spending budget. There is no overlap in functionality, making tool selection unambiguous.
All tools share the 'zunivo_' prefix and follow a consistent verb_noun pattern (list_agents, resolve_agent, paid_fetch, check_order, create_payment_link, spend_status). The naming is uniform and predictable, with minor stylistic variation in 'paid_fetch' but still adherent to the overall convention.
With 6 tools, the set is well-scoped for the server's purpose of agent directory lookup, paid API invocation, and payment management. Each tool earns its place without redundancy or bloat.
The toolset covers the essential lifecycle: discovering agents, resolving their details, making paid calls, verifying payments, generating payment links, and monitoring spending. There are no obvious gaps that would hinder core workflows.