# ResultRail MCP Marketplace Distribution

ResultRail is its own LarryBuildsAI product. Do not merge or cross-list it as Signal Desk, GateCheck, Boundary Guard, or x402 Resource Scanner.

| Priority | Directory | Status | URL |
|---:|---|---|---|
| 1 | Official MCP Registry | server-json-ready; publish with mcp-publisher after GitHub namespace auth | https://registry.modelcontextprotocol.io |
| 2 | Glama | metadata ready; submit repo/remote URL for tool-level indexing and browser inspection | https://glama.ai |
| 3 | Smithery | streamable-http URL-ready; publish remote URL with smithery mcp publish | https://smithery.ai/docs/build/publish |
| 4 | PulseMCP | manual submission packet ready; official registry listing should propagate later | https://www.pulsemcp.com/submit |
| 5 | MCPCentral | server-json-ready; publish to https://registry.mcpcentral.io with mcp-publisher | https://mcpcentral.io/submit-server |
| 6 | xpay Tools | provider-candidate; use ResultRail paid tools as single-provider data endpoint | https://docs.xpay.sh/en/tools |
| 7 | OMA-AI | x402 marketplace candidate; submit as pay-per-success public data MCP | https://www.oma-ai.com |
| 8 | MCP Market | packet-ready; directory already indexes x402-native MCP examples | https://mcpmarket.com |
| 9 | MCP.so | packet-ready; use ResultRail MCP URL, server card, and product card | https://mcp.so |
| 10 | MCP.Directory | packet-ready; remote MCP directory visibility target | https://mcp.directory/servers |
| 11 | mcpservers.org | packet-ready; add after official registry/repo metadata is stable | https://mcpservers.org |
| 12 | Awesome MCP Servers lists | PR-ready once public repo/docs copy is finalized | https://github.com/TensorBlock/awesome-mcp-servers |
| 13 | Anthropic Remote MCP Directory | submission guide identified; submit after stable remote MCP and auth behavior | https://support.claude.com/en/articles/12922490 |

Submission copy: ResultRail by LarryBuildsAI sells pay-per-success public-data result packs for AI agents. Agents call a free quote tool, pay only for a valid domain or URL result, and receive source URLs, confidence, timestamps, and receipt hashes without creating another vendor account.

Buyer keywords: ResultRail, pay-per-success data, x402 data API, MCP data enrichment, domain enrichment, URL extraction, public-data result packs, agent data router, no API keys for agents

Revenue signal: Public MCP/x402 discussions show demand for pay-per-call data tools, but also friction around retry logic, refunds, fiat support, and per-tool billing. ResultRail should sell small, successful, source-attributed results and keep quote/price/receipt metadata explicit.

Publishing notes:
- Publish the official MCP Registry listing first because downstream directories and marketplaces consume it as canonical metadata.
- Keep ResultRail listings scoped to /resultrail/mcp, /v1/resultrail/*, and ResultRail cards only.
- Do not reuse Signal Desk, GateCheck, Boundary Guard, or x402 Resource Scanner copy in directory titles or descriptions.
- Disclose that paid tools use x402 and that the free quote tool is callable before payment.

Claim boundary: This ResultRail packet is crawlable and submission-ready; it does not claim external approval, ranking, featured placement, endorsement, or third-party indexing.