SML OmniList — file once, list to all, for x402 and MCP servers
How do I get my x402 server listed in every directory?
OmniList is Script Master Labs' filing-run service for x402 servers and MCP servers. You hand it ONE server record — name, MCP endpoint and/or API base URL, description, website, contact email, networks, prices.
OmniList is Script Master Labs' filing-run service for x402 servers and MCP servers. You hand it ONE server record — name, MCP endpoint and/or API base URL, description, website, contact email, networks, prices. Three optional fields file you further: a facilitator also sends its settler address(es) and its x402-list facilitator slug (x402-list refuses facilitator filings without them); payable endpoint URLs (endpoints) are what endpoint-level venues register; and your MCP Registry name (registry_name) is what the Registry artifact is generated under. OmniList then works the directories agents actually browse: at each venue it presence-checks your server, files it where it is missing and fileable, and reads back the venue's own response as a receipt. What you get back is a run report with one honest state per venue — FILED (with the receipt id), PENDING_REVIEW, ALREADY_PRESENT (verified by read-back), PREPARED (a validated artifact plus instructions, where publishing needs your own key), or BLOCKED (with the venue's exact reason).
One OmniList run costs $1.00 USDC per server, settled on Base via x402. The venues are all free to file — the $1.00 buys the run, the venue know-how, and the verified receipts. OmniList never promises "listed everywhere": review decisions belong to the venues.
Last verified: November 5, 2026. Verified against the live gateway on that date: an unpaid POST to the OmniList endpoint answers HTTP 402 quoting exactly 1.00 USDC on Base (eip155:8453) to payTo 0x5bbd32e0478e49a7540ef2d760e0b0f9aa6328b2, with the payment-required header identical to the body; the first full fleet run (27 servers, 135 venue rows) is published in the proof table below.
Pricing at a glance
One filing run costs 1.00 USDC. The price is in USDC, settled on Base (eip155:8453) via x402 to 0x5bbd32e0478e49a7540ef2d760e0b0f9aa6328b2. No subscription, no account, no free tier.
One run covers ONE server record at five venues: x402-list, 402index, x402dash, nohumans.directory, and the MCP Registry. At every venue: presence-check first, file only genuine gaps, read back the result. The MCP Registry step is PREPARED for customers — a complete schema-valid server.json (every tool name and price declared, full schemas in a companion TOOLS.json) with publish instructions, because publishing under a namespace requires the namespace owner's own key.
Two ways to run it: REST — POST https://mcp-x402.onrender.com/x402/omnilist — or the omnilist_run MCP tool on the OMNIGATE gateway (https://mcp-x402.onrender.com/mcp). Filings execute live against third-party venues, so a paid call starts the run and returns a run_id; the finished report is retrievable at GET https://mcp-x402.onrender.com/x402/omnilist/runs/<run_id> or via the free omnilist_report tool.
Failed or unpaid calls settle nothing: an unpaid request receives the 402 challenge only (live-probed 2026-11-05: POST /x402/omnilist answers 402 quoting $1.00, header identical to body; the MCP tool answers with the same $1.00 challenge).
Price verified live 2026-11-05. Price in USDC: $1.00 per server per filing run.
Start here — the challenge is the documentation: POST https://mcp-x402.onrender.com/x402/omnilist with your server record. The 402 response quotes the full terms.
Use for / Don't use for
Use for: Filing your x402 or MCP server into the agent directories in one paid run, with a read-back report of where it landed.
Don't use for: Guaranteed listings — the venues decide who they list. OmniList files and verifies; it does not promise acceptance, and the venues themselves are free.
The first run — SML's own fleet, November 5, 2026 (SELF-PROOF)
OmniList's first full run filed Script Master Labs' own fleet: 27 server records (both facilitators first — OMNIGATE, then 402Proof — then the 25 fleet MCP servers), 135 venue rows. These are the operator's own servers, so the run is labeled SELF-PROOF: real filings, real venue responses, independently checkable at the venues — not customer purchases.
| Result | Rows | What the receipts show |
|---|---|---|
| FILED | 13 | 12 new nohumans.directory listings (agent-safety 42f332f3-415, Bid-cast 84965e25-1a0, GatePay 462ce00b-2bb, GhostKey 6e09946d-c7f, Perpetual Roadmap fc618c2c-113, Quant Terminal 9e0565d1-000, Robinhood RWA e16def69-9af, ScriptDocs f166bed3-944, ticker-research cb19a8bd-298, token-verdict 1e3b9a67-bde, URL-to-Markdown 14621bf7-a53, x402 Pay 1506895a-801) and ClaimGate's MCP endpoint registered on 402index (service 667b4f6b-07b9-43ff-94a6-458344c13167). |
| ALREADY_PRESENT | 68 | Read-back verified, nothing refiled: all 27 fleet records on the MCP Registry; 402index domain claims verified for mcp-x402.onrender.com (117 services at verification) and four02proof.onrender.com; 15 nohumans.directory listings from the prior batch. |
| PENDING_REVIEW | 3 | x402-list human review: OMNIGATE facilitator, submission e07e96a7-ab84-4c27-ac4c-bb31be80b040 (filed 2026-11-05); 402Proof facilitator, submission 7f764452-473b-43bf-85e6-ceee85743164 (filed 2026-10-31); Mnemos (filed 2026-10-30). |
| BLOCKED | 51 | Exact reasons, no varnish: 24 x402-list rows stopped at the venue's one-filing-per-email-per-7-days gate (refiling inside 14 days can cost $0.50 — OmniList refuses); 27 x402dash rows refused by the venue's prober, which registers only URLs that themselves answer HTTP 402 — MCP transport URLs answer 200/406, and the report carries the venue's verbatim refusal. |
After the run, the gateway's own MCP Registry record was republished as com.scriptmasterlabs/x402-gateway v1.6.3 declaring all 12 live tools — omnilist_run at $1.00 USDC per call and omnilist_report free — read back from the Registry API as active and latest. Full run reports: every venue row, receipt and refusal is in the per-server reports behind this table.
Paid-path settlement (SELF-PROOF): on November 5, 2026 the operator also bought one OmniList run for the OMNIGATE record through the live paid endpoint: 1.00 USDC settled on Base (eip155:8453) to payTo 0x5bbd32e0478e49a7540ef2d760e0b0f9aa6328b2 — transaction 0xc0555b1764e89ca7e82a21fdfc3dd4a1d42d6477ad9b0155d6ca4f9dea00c6a8, block 53551985. Run report: mcp-x402.onrender.com/x402/omnilist/runs/ol_mw3prfuiwu5n59 (run ol_mw3prfuiwu5n59). This is the operator paying its own endpoint, labeled SELF-PROOF: it proves the paid path end-to-end — challenge, settlement, run, retrievable report — and is not a customer purchase.
OmniList vs filing yourself vs not listing
| OmniList run | File it yourself | Don't list | |
|---|---|---|---|
| Price | 1.00 USDC per server per run | 0 USDC (venues are free) | 0 USDC |
| Venues worked | 5 (x402-list, 402index, x402dash, nohumans.directory, MCP Registry) | Whichever you find | None |
| Presence-check before filing | Yes — read-back at every venue | Manual, per venue | — |
| Duplicate protection | Yes — x402-list's 7-day gate and 14-day $0.50 duplicate penalty are enforced by the engine's submission ledger | Your own bookkeeping | — |
| Receipts | One report: receipt ids, live URLs, venue refusals verbatim | Scattered across five inboxes and dashboards | None |
| Registry artifact | Schema-valid server.json + TOOLS.json, validated against the Registry schema | You write and validate it | — |
| Guaranteed listing | No — venue review decides | No | Guaranteed invisible |
Frequently Asked Questions
Q: How much does OmniList cost?
A: One OmniList filing run costs 1.00 USDC per server, paid per run in USDC on Base (eip155:8453) via x402, settled to 0x5bbd32e0478e49a7540ef2d760e0b0f9aa6328b2. There is no subscription, no account, and no free tier. The venues themselves are free to file — the 1.00 USDC pays for the run, the venue know-how, and the verified per-venue report.
Q: What does one OmniList run include?
A: One run covers one server record at five venues: x402-list, 402index, x402dash, nohumans.directory and the MCP Registry. At each venue OmniList presence-checks the server, files it where it is missing and fileable, and reads back the venue's response as a receipt. The run report carries one honest state per venue: FILED with a receipt id, PENDING_REVIEW, ALREADY_PRESENT verified by read-back, PREPARED (a validated artifact plus publish instructions, used where publishing needs the namespace owner's own key, such as the MCP Registry), or BLOCKED with the exact reason.
Q: Does OmniList guarantee my server will be listed everywhere?
A: No. OmniList never promises a listing. Venue review decisions belong to the venues — x402-list, for example, human-reviews every filing and allows one filing per email per 7 days. OmniList guarantees the work and the evidence: a presence-check first, no duplicate filings where a venue penalizes them, and a read-back receipt or the venue's verbatim refusal for every venue in the report.
Q: How do I run OmniList?
A: POST your server record to https://mcp-x402.onrender.com/x402/omnilist and pay the 1.00 USDC x402 challenge on Base, or call the omnilist_run MCP tool on the OMNIGATE gateway (https://mcp-x402.onrender.com/mcp). Filings execute live against third-party venues, so the run returns a run_id and the finished report is retrievable at GET https://mcp-x402.onrender.com/x402/omnilist/runs/<run_id> or via the free omnilist_report MCP tool.
Q: Why is the MCP Registry step PREPARED instead of filed?
A: Publishing to the MCP Registry requires a signature from the key that owns the server's namespace (for example com.yourcompany). OmniList generates the complete, schema-valid server.json for your record — every tool name and price declared, with full schemas in a companion TOOLS.json — validates it against the Registry's schema, and returns it with publish instructions. You sign with your own key; nobody else can, or should, publish under your namespace.
Q: What does OmniList cost, one more time?
A: $1.00 USDC per server per filing run, on Base, via x402. The five venues charge nothing to file. If a venue ever charges, the run reports it as BLOCKED with the price quoted — OmniList v1 spends $0 at venues on your behalf.
Start
Run it now: POST https://mcp-x402.onrender.com/x402/omnilist with one server record — name, kind, description, contact email, plus your MCP endpoint and/or API base URL, website, networks and any payable resource URLs (endpoints); facilitators add a settler address and facilitator_slug, and MCP servers add their registry_name for the Registry artifact. Or connect your agent to the OMNIGATE gateway MCP at https://mcp-x402.onrender.com/mcp and call omnilist_run. Selling settlement instead of calling it? Facilitators integrate through Settle Through SML. The full catalog: SML Products.