merona — x402 settlement index
REMOTE · API.MERONA.IO
See what actually settles on x402: wash-adjusted volume, payTo checks. Free, no key, no signup.
Available components
Last scanned (14 hours ago)
Scores higher than 88% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 625 tokens (~156/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 +1
- Stability: 0.97 → pass security
- 4 Nov 26 −1
- Stability: pass → 0.97 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://api.merona.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=merona.io | CN=WE1,O=Google Trust Services,C=US | 13 Nov 2026 | 11 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 41f5f4ccc95c78bd1374936f657bc340 |
| SANs: merona.io, *.merona.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.merona.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| merona.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; img-src 'self' data:; font-src 'self' data:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline'; connect-src 'self'; base-uri 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.merona.io/mcp | Verified | 200 | |
| http (plaintext) | http://api.merona.io/mcp | HTTPS enforced | 308 | https://api.merona.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
clean_stats ~80
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| clean | array | – | One entry per chain. |
| error | string | – | Present only on backend failure. |
| note | string | – | Scope and method pointer. |
No examples provided.
mismatch_feed ~93
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| catalog_vs_live | array | – | Endpoints advertising one payout address while asking payers for another (top 10). |
| error | string | – | Present only on backend failure. |
| meta | object | – | Feed provenance: generated-at, counts, method pointer. |
| payto_rotation_count | integer | – | Endpoints with dated payout-address rotation history. |
No examples provided.
payto_check ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Wallet address (0x… or base58) or endpoint URL/hostname to look up. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Present only on backend failure. |
| matches | array | – | Mismatch/rotation records touching the query; empty when none known. |
| note | string | – | Interpretation guidance — dated facts, not accusations. |
| query | string | – | The query as interpreted. |
No examples provided.
trust_score ~171
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. Free — no key or payment needed. Optional: pass payment=<base64 X-PAYMENT payload> to pay $0.001 via x402 and receive a settlement-receipted response.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Seller wallet address to score. |
| api_key | string | – | merona API key. Alternative to per-call x402 payment. |
| chain | string | yes | Chain the seller settles on, e.g. base, polygon, solana. |
| payment | string | – | Base64 X-PAYMENT payload for a single x402 payment. |
| Name | Type | Req | Description |
|---|---|---|---|
| components | object | – | Score component breakdown. |
| delivery | object | – | Paid-probe delivery evidence, when merona has bought from this seller: status delivery_verified (dated) or charged_unserved (payment settled, request refused; settlement tx included). This score cove… |
| error | string | – | Present only on failure. |
| grade | string|null | – | A–F letter; null means unrated (evidence gate, not an adverse signal). |
| payment_required | object | – | x402 payment instructions; present only when the call is unpaid. |
| score | number|null | – | Numeric m.Score behind the letter. |
| snapshot_sha256 | string | – | Snapshot hash for independent re-derivation. |
| suggested_action | object | – | Deterministic action hint (PROCEED/CAUTION/INVESTIGATE/DECLINE/INSUFFICIENT_EVIDENCE) with reasons and rule version. |
| tier | string | – | unrated | provisional | verified. |
No examples provided.
How do I install the merona — x402 settlement index MCP server?
merona — x402 settlement index is a hosted endpoint at https://api.merona.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.merona.io
claude mcp add --transport http io-merona-settlement-index 'https://api.merona.io/mcp'
What is the merona — x402 settlement index MCP server?
merona — x402 settlement index is an MCP server listed in the public MCP registry as io.merona/settlement-index. See what actually settles on x402: wash-adjusted volume, payTo checks. Free, no key, no signup. This page covers its hosted endpoint (https://api.merona.io/mcp).
Is the merona — x402 settlement index MCP server safe to use?
merona — x402 settlement index scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the merona — x402 settlement index MCP server expose?
merona — x402 settlement index exposes 4 tools: payto_check, mismatch_feed, clean_stats, trust_score. Their descriptions and schemas cost roughly 463 tokens of context every time the server is loaded.
Does the merona — x402 settlement index MCP server require authentication?
No. We connected to merona — x402 settlement index without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the merona — x402 settlement index MCP server still maintained?
merona — x402 settlement index is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the merona — x402 settlement index MCP server?
VerifyMCP ran 13 checks on merona — x402 settlement index, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.