
Agoraverify MCP server
Which MCP servers are Agoraverify'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-24
- Registry namecom.agoraverify/agora-omegaverified in the MCP registry
The registry name sits under agoraverify.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-24
- Tools8
- Server calls itselfagora-omega
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 81 ms.
- Its tools do every use case we checked: verify a supplier against company registry and sanctions lists; check a crypto platform against regulator blacklists; screen an x402 payment request before paying it.
- Checked on 3 of the 7 days it takes to judge reliability.
Once connected
- For "verify a supplier against company registry and sanctions lists", the likely first call is agora_supplier_audit.
- For "check a crypto platform against regulator blacklists", the likely first call is agora_counterparty_check.
- For "screen an x402 payment request before paying it", the likely first call is agora_pay_guard.
- agora_pay_guard change data without a sign-in: anyone with the address can call them.
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: 3 so far
- What an agent can do with it3 of 3 use cases
- Answeredmeasuring3 of the 7 daily checks it takes to print a share
- Median first answer127 ms
- Space in an agent's context≈ 1,131 tokensthe definitions of all its tools (8), which an agent carries on every turn
- Tool definitionsB · 81 of 100
- Typed results0 of 8 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 1 of 8
- Not saying whether it only reads or can destroy: 8 of 8
What an agent can do with it
- can do · verify a supplier against company registry and sanctions lists
- can do · check a crypto platform against regulator blacklists
- can do · screen an x402 payment request before paying it
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
- Tools that change data, on a server that answers without a sign-in: agora_pay_guard
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 →
agora_catalogFree. Lists AGORA Omega paid tools, prices (USDC via x402) and networks.
agora_company_searchOfficial French company data (SIRENE/RNE), cleaned: identity, geolocated HQ, NACE code, headcount, latest revenue and net income. Price: $0.004 USDC per call, paid with x402.
agora_counterparty_checkCounterparty check before paying a platform or crypto provider: French AMF blacklists, ESMA MiCA register (authorised and non-compliant CASPs), sanctions lists (EU, UN Security Council, US OFAC SDN). Official public data, refreshed daily…
agora_verify_deliverableIndependent verifier agent: quality score from 0 to 100, doubtful claims and a verdict (valider = accept, corriger = fix, rejeter = reject). Check another agent's work before paying for it. Price: $0.03 USDC per call, paid with x402.
agora_supplier_auditSupplier due-diligence mission (orchestrated): official French company registry + AMF blacklists + ESMA MiCA register + EU/UN/OFAC sanctions, merged into one pay / verify / do-not-pay decision with confidence score. Run it before paying a…
agora_ai_act_checkEU AI Act art. 50 transparency check: is an AI disclosure required, is it present, plus the disclosure text and machine-readable metadata to add. Price: $0.02 USDC per call, paid with x402.
agora_pay_guardPre-payment guard for AI agents: before paying an x402 endpoint, checks its payment request (official USDC contract, network, price vs your spending policy, payTo address against US OFAC sanctioned crypto addresses and the Chainalysis…
agora_stablecoin_depegAGORA Sentinel: stablecoin depeg risk indicator. Reads the Chainlink price feed on-chain and returns the deviation from 1 USD in basis points, a 0-100 score, a level (calme / tendu / alerte), data age and staleness. A risk indicator, not…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"agora-omega": {
"type": "http",
"url": "https://agoraverify.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http agoraverify https://agoraverify.com/mcpclaude.ai, ChatGPT and other clients: add https://agoraverify.com/mcp as a custom connector in the settings.
OpenAPI spec
7 paths, read 2026-10-24. 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.