You don't have to submit anything.

We already found your tool. Claim it to reach Verified, fix the listing, and keep it current across every directory.

Prove it's yours in a minute.

Sign in with GitHub or Google.
Prove control: own the repo on GitHub, or add a DNS TXT record.
Scanned tools become Verified. Correct the description any time.

DNS proof looks like this:

_mcpvetted.yourdomain.com  TXT  "mcpvetted-verify=4f2a…"

Claims never change checks. A tool has to pass them before a claim can lift it to Verified.

One listing. Every directory. Every release.

You keep one verified listing here. Each release updates it everywhere you choose. Paying never changes your tier or rank.

Where should we keep you listed?

Official MCP RegistryautomatedPublished with mcp-publisher under the publisher's verified namespace.
PulseMCPautomatedCopies from the Official MCP Registry.
awesome-mcp-serversautomatedOne pull request per tool; a person approves each before it opens.
Smitherydone by a personA person submits the filled packet during the test.
Cursor Directorydone by a personA person submits the filled packet during the test.
mcpservers.orgdone by a personA person submits the filled packet during the test.
Glamadone by a personClaim flow; a person completes it during the test.

Which tool? (slug from its trust page)I authorize submitting my verified listing to these directories on my behalf, as described in the Publisher terms.

Publisher sync

$99 once

covers a full year

Status per directory in your dashboard
Updates on every release
Cancel any time

Checkout opens soon.

Show your tier where people look.

A live badge for your README. It updates on its own, including when a release fails.

[![MCP Vetted tier](https://mcpvetted.com/api/badge/npm-ibm-ibmi-mcp-server)](https://mcpvetted.com/t/npm-ibm-ibmi-mcp-server)