mcp server
merona — x402 settlement index
Wash-aware x402 trust: free payTo checks, mismatch feed, and paid seller trust scores.
Description as published by the maintainer. Source
- version 1.0.0
- active
active — Registry entry last updated 2026-08-06.
What this server can do
4 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
clean_stats- Get wash-adjusted x402 settlement volume per chain — spend that survives removal of funded loops and self-dealing cycles, which can differ from raw transfer totals by orders of magnitude. Returns clean settlement count, clean volume in USD and an as-of date per chain. Takes no arguments. Free, no key. These are the figures published on merona.io.
mismatch_feed- List x402 endpoints currently advertising one payout address while asking payers for another, from merona's nightly probe of the public catalog — the top 10 entries with advertised vs live addresses, full counts and as-of dates (complete feed, uncapped: merona.io/mismatches.json). Takes no arguments. Free, no key. Use payto_check instead when you already have a specific address or endpoint to check.
payto_check(query)- Check whether an x402 endpoint or wallet pays out where it claims to, before your agent sends funds. Takes one wallet address or endpoint URL. Returns any catalog-vs-live payout mismatch, dated payout-rotation history, and whether the address has settled on chain. Free, no key. Use mismatch_feed instead to list every known mismatch. Records are dated facts, not accusations, and no record found is not a clearance. Required: query.
trust_score(chain, address, api_key, payment)- Score a specific seller wallet before paying it: wash-aware m.Score with an A–F grade, component breakdown, wash flags including multi-hop cycle detection, and the snapshot SHA so the result can be re-derived independently. Requires chain and address. Paid, $0.005 per call: pass payment=<base64 X-PAYMENT payload> to pay via x402, or api_key=<key>. Called without either, it returns x402 payment instructions rather than an error. Required: chain, address.
Last successful function declaration observed on . Source: https://api.merona.io/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://api.merona.io/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-08-06 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-08-06 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 4 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | api.merona.io | |
| mcp endpoint status | ok | The server listed 4 functions when asked. | as of probe | api.merona.io |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json