Neuronto Payments: x402 facilitator and API gateway MCP server
com.neuronto/x402-payments-facilitatorneuronto.comstreamable-httpv1.1.0Scanned
Put any API behind x402 in one call, settle USDC on Base, buy credits, find paid resources
6 tools: 4 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Neuronto Payments: x402 facilitator and API gateway MCP server can do
The Neuronto Payments: x402 facilitator and API gateway MCP server is published by neuronto.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (4 tools: settlement_price, integration_snippet, monetize_api and buy_credits), but cannot delete data. 2 tools only read.
1 tool brings in text other people can write (find_paid_resource).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 4Claude Code: ask
buy_creditsHow 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, ga…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
integration_snippetWorking 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
monetize_apiPut 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 stra…No findings
Why it is in this group
- The description's first verb is "put": a word for a change.
Description, as the server wrote it 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.
settlement_priceWhat a settlement costs through this facilitator, per network, with the basis it was computed from.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it What a settlement costs through this facilitator, per network, with the basis it was computed from. Free while the service is in launch pricing.
Only reads 2Show 2 read-only tools
facilitator_statusWhat 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 sett…No findings
Why it is in this group
- The name "facilitator_status" says "status": a word for reading.
Description, as the server wrote it 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.
find_paid_resourceSearch 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 the…Reads text others writeNo findings
Why it is in this group
- The name "find_paid_resource" says "find": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "search" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:43 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://pay.neuronto.com/mcp: tools/list returned 6 tools to an anonymous client, including settlement_price (write), integration_snippet (write), monetize_api (write), buy_credits (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http x402-payments-facilitator https://pay.neuronto.com/mcpclaude mcp add --transport http x402-payments-facilitator https://pay.neuronto.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__x402-payments-facilitator__facilitator_status",
"mcp__x402-payments-facilitator__find_paid_resource"
],
"ask": [
"mcp__x402-payments-facilitator__settlement_price",
"mcp__x402-payments-facilitator__integration_snippet",
"mcp__x402-payments-facilitator__monetize_api",
"mcp__x402-payments-facilitator__buy_credits"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as x402-payments-facilitator. Review it before you use it.
Capability tags behind 1 rule
- mcp__x402-payments-facilitator__find_paid_resource untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.neuronto/x402-payments-facilitator/verify?hash=f043c351f01b9e23d53660e4878665285aa24260b808a536e7a5fd6c1a236721" | jq -e '.changed == false'Pinned hash f043c351f01b, from Nov 10, 2026, 21:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.neuronto/x402-payments-facilitator/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.neuronto/x402-payments-facilitator)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:59 UTC.
Neuronto Payments: x402 facilitator and API gateway MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Neuronto Payments: x402 facilitator and API gateway MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Neuronto Payments: x402 facilitator and API gateway MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Neuronto Payments: x402 facilitator and API gateway MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Neuronto Payments: x402 facilitator and API gateway MCP server have?
- 6 tools: 4 write, 2 read. settlement_price, integration_snippet, monetize_api, buy_credits, facilitator_status and find_paid_resource.
Does the Neuronto Payments: x402 facilitator and API gateway MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Neuronto Payments: x402 facilitator and API gateway MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Neuronto Payments: x402 facilitator and API gateway MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.