Get your MCP server indexed faster on Loomal.
Loomal imports from the official MCP registry and ranks by signals you control. Here's how the pipeline decides what to index — and the shortcut that skips the queue entirely.
Loomal's marketplace isn't crawled from the open web — it's imported from the official MCP registry at registry.modelcontextprotocol.io, the canonical source where io.github.* namespaces are GitHub-ownership-verified at publish time. If your server isn't in the registry, Loomal's pipeline can't see it.
Indexing speed therefore comes down to three things: being in the registry at all, carrying metadata that passes the pipeline's trust filters, and ranking well on the signal it sorts by. Each is in your control, and there's a fourth path that bypasses the import queue entirely.
How the pipeline works
Imports pull the registry's server list, apply trust filters, fetch GitHub star counts per repo, and rank by stars before taking a top slice into the marketplace as unclaimed listings. Re-imports run periodically and refresh stars, descriptions, and install metadata on existing listings — but they never touch claim fields, and claimed listings are skipped entirely.
The trust filters matter more than most maintainers realize. The registry verifies namespace ownership but not the repository URL field, so the pipeline requires that an io.github.* entry's repo actually belong to the verified namespace owner — a defense against star-count spoofing. Point your repository URL at someone else's famous repo and you don't look popular; you get filtered out.
Step 1: Publish to the official registry
If you haven't published, this is the whole bottleneck. The registry's publisher CLI generates a server.json from your project, verifies your GitHub namespace, and pushes the entry.
# One-time: install mcp-publisher (see registry docs for your platform)
mcp-publisher init # scaffold server.json from your project
mcp-publisher login github # verify your io.github.* namespace
mcp-publisher publish # push the entry to the official registryStep 2: Make your metadata import-ready
Set the repository URL to a repo owned by your verified namespace — same owner, exactly. Write a description that says what the server does in plain terms: Loomal assigns each listing a category by keyword-scoring the name and description, so a vague description lands you in a vague category, or none that fits.
Declare your packages (npm, PyPI, OCI) and any remote endpoint URL in the entry. Install metadata flows straight onto the listing, and a declared remote is what later lets you connect the live server and publish its real tool list.
Step 3: Accept that stars are the ranking signal
The registry has no popularity metric of its own, so the import ranks candidates by GitHub stars when selecting what enters the marketplace. A brand-new zero-star server is competing for the same slice as established projects — which is unsatisfying but honest about what the signal measures.
The practical move isn't gaming stars; it's the usual open-source distribution work (announce, document, solve a real problem) plus patience for the next import cycle — or skipping the queue, which is step 4.
Step 4: Skip the queue — list directly
Import is how Loomal seeds the directory; it isn't the only door. From the console you can create a priced seller endpoint for your server immediately — no registry entry, no star threshold, no waiting on an import cycle. Priced listings enter discovery through the live marketplace feed, where agents can find the endpoint, read its price, and pay per call in USDC over x402.
Pricing starts at $0.01 per call and changes in one field; the 5% fee on settled transactions is currently waived. If your server later arrives via registry import too, claiming that listing and linking your priced endpoint merges the two paths into one storefront.
FAQ
Why isn't my MCP server on Loomal yet?
Three usual reasons: it isn't published to the official MCP registry, which is Loomal's import source; its repository URL doesn't belong to the verified namespace owner, which trips the anti-spoofing filter; or it didn't make the star-ranked slice of the latest import. Listing a priced endpoint from the console sidesteps all three.
Can I trigger a re-index of my listing?
There's no public re-index button as of mid-2026 — imports re-run periodically and refresh stars, descriptions, and install metadata automatically. For changes you control directly, claim the listing: a claimed listing lets you connect your server and publish its live tool list without waiting on any import.
Do GitHub stars really determine indexing?
For the import path, yes — the registry carries no popularity signal, so Loomal ranks import candidates by stars per repo before taking the top slice. Stars don't affect direct listings from the console, and they never affect claimed listings being preserved across re-imports.
Does publishing to the registry cost anything?
No — the official registry is free to publish to, and Loomal's import is automatic from there. Costs only appear if you attach pricing to an endpoint, where calls start at $0.01 and Loomal's 5% fee on settled transactions is currently waived.
Don't wait for the crawler.
List a priced endpoint from the console and be discoverable today.