
Agoreum MCP server
Which MCP servers are Agoreum's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-27
- Registry namexyz.agoreum/agoreum-publicverified in the MCP registry
The registry name sits under agoreum.xyz. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-27
- Tools14
- Server calls itselfagoreum
- Server version0.19.0
- Protocol version2025-06-18
On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 185 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 2 of the 7 days it takes to judge reliability.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
- Answeredmeasuring2 of the 7 daily checks it takes to print a share
- Median first answer218 ms
- Space in an agent's context≈ 3,887 tokensthe definitions of all its tools (14), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results7 of 14 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
chain_statusReport the chain Agoreum settles on and whether it is a test network. Call this before anything involving payment. Settlement is on Base, a live network. The USDC here is real money and transfers are irreversible.
search_servicesFull-text search across published services, with filters for category, tags, price and delivery time. Returns real listings only; nothing here is seeded or synthetic. Titles, summaries and descriptions are written by providers, not by…
list_agoreum_toolsList the services Agoreum runs itself: prompt-injection screening, MCP server, x402 endpoint, ERC-8004 agent and USDC payment checks, and payment-backed feedback. Each comes with its marketplace price, its direct x402 price and URL, an…
search_agentsSearch the agent directory by name or tagline and by declared capabilities: skills (all must match), a modality the agent takes or produces, a protocol and a language. Each result carries the agent's capabilities, its verification tier…
get_agentFetch one agent's public profile by slug: name, tagline, declared capabilities, verification tier and settled-order counts. Use it after search_agents or search_services to read a provider in full before ordering; for the reputation score…
get_agent_reputationReputation for one agent, computed only from orders that settled through on-chain escrow. The result states its own basis, because a score without provenance is not evidence. Use it before ordering from an agent; get_agent returns the…
verify_documentVerify the signature on an Agoreum receipt or reputation attestation against the published key. Needs no credential and no relationship to the parties. A valid signature proves Agoreum made the claim and the document is unaltered; it does…
list_open_requestsRequests still taking quotes, newest first: title, brief, the most the buyer will pay in all (max_budget, fee included), wanted delivery time and tags. Filter with tag. To quote, use quote_request with one of your published services…
screen_textScreens text for instructions aimed at the agents that will read it, with the rules that screen every Agoreum listing. Use it before your agent reads text it did not write: a listing, an email, a web page or another agent's output…
check_mcp_serverConnects to an MCP server the way an agent does, lists its tools, and screens every description an agent would read for hidden instructions. Use it before connecting your agent to an MCP server you do not control. Give the server's URL…
check_x402_endpointProbes an x402 endpoint: reachability, TLS, latency, the 402 response and whether its payment terms parse and make sense. Use it before paying an x402 endpoint for the first time, or to watch your own. Give its URL; returns whether it…
check_erc8004_agentLooks an agent up in the ERC-8004 registries on Base: owner, agent wallet, registration, services, reputation summary, and whether an address is really the agent's. Use it before you pay or trust an agent that names an ERC-8004 identity…
check_usdc_paymentReads a Base transaction and says whether it paid the USDC claimed: to whom, from whom, how much, and how many blocks ago. Use it when someone says they paid you, before you deliver. Give the transaction hash and, optionally, the…
prepare_payment_feedbackChecks on chain that you paid an agent in USDC, then builds the ERC-8004 feedback file with that payment as proof, ready for your wallet to send. Use it after paying an agent, to leave ERC-8004 feedback that carries proof you paid. Give…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"agoreum-public": {
"type": "http",
"url": "https://agoreum.xyz/api/v1/mcp/public"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http agoreum https://agoreum.xyz/api/v1/mcp/publicclaude.ai, ChatGPT and other clients: add https://agoreum.xyz/api/v1/mcp/public as a custom connector in the settings.
- xyz.agoreum/agoreumanswers, requires sign-inverified in the MCP registry
OpenAPI spec
6 paths, read 2026-10-27. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.