Neuronto Payments: x402 facilitator

x402 facilitator: settlement prices, live networks, a catalogue of paid resources, integration code

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
70%
Naming quality
90%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~446Tokens (tool definitions)
~614 BTypical response size
Minimal attention impact (0.35% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "x402-payments-facilitator": {
      "url": "https://pay.neuronto.com/mcp"
    }
  }
}

Remote endpoints

https://pay.neuronto.com/mcpstreamable-http

What it can do

Tool inventory

Tools (4)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
facilitator_status

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

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
settlement_price(network)

What a settlement costs through this facilitator, per network, with the basis it was computed from. Free while the service is in launch pricing.

Input Schema

{
  "type": "object",
  "properties": {
    "network": {
      "type": "string",
      "description": "CAIP-2 network, for example eip155:8453. Omit for every network."
    }
  },
  "additionalProperties": false
}
🟢find_paid_resource(query, network, limit)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Words to match in the URL or description."
    },
    "network": {
      "type": "string",
      "description": "CAIP-2 network to restrict to."
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 50
    }
  },
  "additionalProperties": false
}
🟡integration_snippet(language, framework, role)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "language": {
      "type": "string",
      "enum": [
        "typescript",
        "python"
      ]
    },
    "framework": {
      "type": "string",
      "enum": [
        "express",
        "hono",
        "next",
        "fastapi"
      ]
    },
    "role": {
      "type": "string",
      "enum": [
        "server",
        "client"
      ],
      "description": "server to charge for a route, client to pay for one."
    }
  },
  "additionalProperties": false
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded4 tools