@rail402.dev/mcp-discovery, whose binary is rail402-mcp.
Use the hosted instance
Rail402 runs a public testnet MCP server. If you only need an endpoint to point an agent at, use it:Run it yourself
Install it, or run it without installing throughnpx:
--http to serve Streamable HTTP instead, which is what you want for a hosted deployment:
/mcp and a /health check. By default it talks to the hosted facilitator at https://facilitator.rail402.dev. Point it at your own facilitator with --bazaar, and enable paying by giving it a funded testnet signer with --secret:
Without
--secret, the server can search but cannot pay. Give it a funded stellar:testnet signer to enable the paid-call tool, because paying settles a real payment on-chain.The tools it exposes
The server exposes two tools, both with strict JSON input and output schemas, and every rejection carries a coded, non-null reason:search_stellar_resourcessearches the Bazaar. It returns structured results and pays nothing.pay_and_callpays for and calls a discovered resource under a mandatory spend cap. It never pays an unbounded amount, and the cap is enforced against the quote actually paid, not a probe.
Next steps
Buyer and agent quickstart
Point an agent at the MCP server and pay for a discovered resource.
Security and trust boundaries
Why the private-hosts flag is off, and the SSRF guard.
How search works
What ranking the search tool runs on.
Error reference
Coded reasons an agent reads, including the spend-cap refusals.