Neuronto Payments: x402 facilitator and API gateway
REMOTE · PAY.NEURONTO.COM
Put any API behind x402 in one call, settle USDC on Base, buy credits, find paid resources
Available components
Last scanned (22 hours ago)
Scores higher than 62% 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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 566 tokens (~94/item across 6 items; 6 tools + 0 resources), lean.Pass
- 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 Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 64% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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 (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
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.
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- 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
- 23 Oct 26 75
- Stability: 0.97 → pass security
- 3 Oct 26 0
- Schema quality: 78 → 94 ▼ functional
- Tool coverage: 57% → 64% ▲ functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “buy_credits” functional
- New tool “monetize_api” 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
- 24 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
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://pay.neuronto.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=neuronto.com | CN=WE1,O=Google Trust Services,C=US | 9 Nov 2026 | 7 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 38bdf1ce28d1a3651387d0bb88acf3b4 |
| SANs: neuronto.com, *.neuronto.com | ||||||
| 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 pay.neuronto.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| neuronto.com. | 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 |
|---|---|
| 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://pay.neuronto.com/mcp | Verified | 200 | |
| http (plaintext) | http://pay.neuronto.com/mcp | HTTPS enforced | 301 | https://pay.neuronto.com/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 →
buy_credits ~73
How to buy Neuronto credits, the one prepaid balance for every paid Neuronto call (searches past the free allowance, multi-step discovery, the change feed, publisher monitoring, gateway fees): the packs, what each thing costs, and the x402 URL to pay.
| Name | Type | Req | Description |
|---|---|---|---|
| pack | string | – | – |
No output schema declared.
No examples provided.
facilitator_status ~61
What this x402 facilitator can settle right now: the live networks and schemes, whether the echo merchant is serving, the state of address screening, observed availability and settlement counts. Call this before advertising a price, because a network that cannot settle is withdrawn here first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
find_paid_resource ~104
Search the catalogue of resources that have been paid for through this facilitator: the URL, the terms, the method, and the input and output shapes where the merchant published them. A resource is listed only after a real settlement and a probe, so nothing here is a claim by its owner.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| network | string | – | CAIP-2 network to restrict to. |
| query | string | – | Words to match in the URL or description. |
No output schema declared.
No examples provided.
integration_snippet ~87
Working code to start charging for a route through this facilitator, in the language and framework you name, plus a live URL to test the client against. Copy it as it is; the only thing to change is the wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | – | – |
| language | string | – | – |
| role | string | – | server to charge for a route, client to pay for one. |
No output schema declared.
No examples provided.
monetize_api ~178
Put an existing HTTPS API behind x402 without changing its code: returns a paid URL that answers 402 with your price, forwards paid calls to your API, and settles each payment straight to your wallet. 1,000 paid calls a month free, then 1% from prepaid credits. Pass your key, or omit it and a new one is returned.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| key | string | – | Your Neuronto key (nc_ or nk_). Omit to get one. |
| name | string | yes | What buyers see, for example 'Weather API'. |
| pay_to | string | yes | Your EIP-55 checksummed wallet address. |
| price_usd | number | yes | Price per call in US dollars, paid in USDC. |
| upstream | string | yes | Your API's https base URL. |
No output schema declared.
No examples provided.
settlement_price ~63
What a settlement costs through this facilitator, per network, with the basis it was computed from. Free while the service is in launch pricing.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | CAIP-2 network, for example eip155:8453. Omit for every network. |
No output schema declared.
No examples provided.
How do I install the Neuronto Payments: x402 facilitator and API gateway MCP server?
Neuronto Payments: x402 facilitator and API gateway is a hosted endpoint at https://pay.neuronto.com/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 · pay.neuronto.com
claude mcp add --transport http com-neuronto-x402-payments-facilitator 'https://pay.neuronto.com/mcp'
What is the Neuronto Payments: x402 facilitator and API gateway MCP server?
Neuronto Payments: x402 facilitator and API gateway is an MCP server listed in the public MCP registry as com.neuronto/x402-payments-facilitator. Put any API behind x402 in one call, settle USDC on Base, buy credits, find paid resources. This page covers its hosted endpoint (https://pay.neuronto.com/mcp).
Is the Neuronto Payments: x402 facilitator and API gateway MCP server safe to use?
Neuronto Payments: x402 facilitator and API gateway scores 75 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 Neuronto Payments: x402 facilitator and API gateway MCP server expose?
Neuronto Payments: x402 facilitator and API gateway exposes 6 tools: facilitator_status, settlement_price, find_paid_resource, integration_snippet, monetize_api, buy_credits. Their descriptions and schemas cost roughly 566 tokens of context every time the server is loaded.
Does the Neuronto Payments: x402 facilitator and API gateway MCP server require authentication?
No. We connected to Neuronto Payments: x402 facilitator and API gateway without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Neuronto Payments: x402 facilitator and API gateway MCP server still maintained?
Neuronto Payments: x402 facilitator and API gateway 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 Neuronto Payments: x402 facilitator and API gateway MCP server?
VerifyMCP ran 12 checks on Neuronto Payments: x402 facilitator and API gateway, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Neuronto Payments: x402 facilitator and API gateway: Authorization. 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.