How to submit an MCP server to PulseMCP

PulseMCP's submit page does not have a form today. It has a notice: new server and client submissions are paused, and so are changes to listings that already exist^[1]. The notice is dated 3 Sept 2026 and it still stood when I read it on 1 Oct 2026. This page is about what you can do while that holds.

What the pause covers

• New MCP servers and new MCP clients.
• Edits to a listing that is already there, such as a corrected description.
• There is no reopening date. The notice says it will reopen the page when ready rather than promise one^[1].

The reason it gives is an overhaul of the directory pipeline and of listing management, so that listings are accurate and changes are handled more quickly^[1].

What PulseMCP asks you to do instead

1. Publish the server to the official MCP Registry. The notice calls that the best first step even when submissions are open, and says PulseMCP will pick the server up automatically after it reopens^[1].
2. Follow the route on the official registry's page, then check that the entry is visible.
3. Look for your server in PulseMCP every so often. There is nothing to press in the meantime.

The registry route is a command-line one, with a login and a publish^[3]. Once you are in, the GitHub MCP Registry is the next place that reads it.

What a PulseMCP listing shows

Each server card on the directory carries a classification such as Official, an estimated weekly visitor count, and a release date, and the list can be sorted by a Recommended order^[2]. Those fields come from PulseMCP's own pipeline, which is the part its notice says needs the overhaul, so they cannot be set from your side while the pause lasts.

Why the check shows nothing

The commonest false alarm is in the check itself. One registry user published successfully, then searched with q= and saw nothing. A maintainer replied that the parameter is search=, and that an unknown parameter is ignored and returns the default alphabetical list^[4].

# your server in the official registry (note: search=, not q=)
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=your-server-name"

# your server in PulseMCP (a search that works on its servers page)
https://www.pulsemcp.com/servers?q=your-server-name

If a re-publish says the version is a duplicate, the entry exists, which is what the same issue's author used to confirm it^[4].

By hand

There is no by-hand submission while the notice stands, so there is no form to press and no queue to join. The by-hand work is the registry publish. On 1 Oct 2026 the directory listed 21,765 servers and showed an update earlier that day^[2]. For other directories that do take submissions, see the full list.

Current status, 1 Oct 2026

Paused since the notice was last updated on 3 Sept 2026, with no date to reopen^[1].