---
title: "For MCP Server Owners | mcp.tc"
description: "Get your MCP server listed on mcp.tc and keep it accurate: what we read, checks every 3 hours, editing your listing, the checkmark, badges and embeds, removal."
url: "https://mcp.tc/docs/server-owners"
markdown: "https://mcp.tc/docs/server-owners.md"
lang: "en"
---

# For server owners

How your MCP server gets on mcp.tc, how you edit its listing, and what you can add: a checkmark, a badge for your README and a card for your website.

## Get listed

Paste your server’s URL on the [Submit](https://mcp.tc/submit) page: a remote endpoint, a GitHub repository, or an npm or PyPI page. There’s no account. Your status page updates by itself and shows the link when it’s ready, usually within a few minutes. A script can send the same suggestion as JSON: [Suggest a server from a script](https://mcp.tc/docs/api#submit) shows how. Many servers are added without anyone asking: from a curated list of well-known servers, and from the official MCP Registry, which we check every hour.

### What we read

Our checker connects the way a client would. It never sends credentials and never runs your code. It identifies itself as `mcp.tc-bot/1.0 (+https://mcp.tc/about)` in the User-Agent and as `mcp.tc-indexer` in the MCP handshake, and it stops after 25 requests or 60 seconds.

- The MCP handshake (`server/discover` or `initialize`): `serverInfo` with its name, title, version, description, website and icons, and the server’s `instructions`.
- `tools/list`, with each tool’s `readOnlyHint` and `destructiveHint`. They become the Read-only, Writes and Can delete hints on the page. `prompts/list` and `resources/list` too, when the server offers them.
- How sign-in works: a 401 with `WWW-Authenticate`, and OAuth protected resource metadata (RFC 9728).
- Your server card at `{endpoint}/server-card` and `/.well-known/ard.json` (or `/.well-known/ai-catalog.json`) on your site.
- Your entry in the official MCP Registry (`server.json`).
- Your repository (`server.json`, `package.json`, `pyproject.toml`, `manifest.json`, the README), your npm or PyPI page, and your website’s title, description and icons.

An AI model then drafts the listing from that public data: the summary, category, what you can do and a few example prompts. It runs with no tools, so instructions hidden in a manifest can’t make it do anything, and fixed checks decide what happens next. A suggestion goes live on its own only when the server answered, nothing was flagged, and the name or vendor matches the domain of the server’s URL (for a local server, the repository owner, npm scope or registry namespace). Everything else waits for a person. The [terms](https://mcp.tc/terms#moderation) list every check.

The listing is written in English. The same model then translates its text into Italian, French, German and Spanish for the site’s other language versions; a translation follows when the English changes.

### Help the listing come out right

- Fill in `title`, `description`, `websiteUrl` and `icons` in `serverInfo`, with icons as PNG, WebP or JPEG (we skip SVG and ICO icons). Icons from the live server win over those from the registry, the server card and your website.
- Annotate your tools with `readOnlyHint` and `destructiveHint`. Without them, the page can’t say which tools only read.
- If `tools/list` needs a sign-in, we can’t read your tools or watch them for changes. The page then says why the list is empty.
- Publish to the official MCP Registry under your own namespace. The listing then carries that name, in our [registry API](https://mcp.tc/docs/api#registry) too.
- The link comes from the server’s name, without words like “MCP server”: a server called Acme Docs MCP gets `mcp.tc/i/acme-docs`.

## Keep it accurate

Every 3 hours we read again the tool list of each remote server that shows it without sign-in, and the `manifest.json` of servers whose tools come from an MCP bundle. For a local server published on npm or PyPI, we look up its latest version. When the tools change and a second read confirms it, the listing shows the new list straight away, and its **History** tab records what changed: tools added or removed, new descriptions, schemas and hints, and new server instructions. A new tool appears with your server’s own title or description. People who follow the listing get an email about it. [Change history and alerts](https://mcp.tc/docs/changes) has the rules.

Once a day we also repeat the handshake with every remote server to refresh its health. Neither check rewrites the description. A server that keeps failing for more than three days gets a **Last check failed** badge; one that suddenly answers from a different URL gets it at once, until the listing is updated. We never run local servers.

Edits made by a person stick, yours included: the automatic updates never overwrite them. The quickest way to fix your listing is to [edit it yourself](https://mcp.tc/docs/server-owners#account). The name, the vendor and a move to another domain go through the [report page](https://mcp.tc/report): tell us there, so the listing and every setup step follow.

## Edit your listing

[Sign in](https://mcp.tc/account) with GitHub or a code sent by email, then claim your listing. We show you a DNS TXT record, a file or a meta tag to add on the domain your server lives on: the domain of its URL, or of its homepage for a local server. Once we find it, you can edit the listing: its descriptions, category, tags, what you can do, example prompts, setup notes, links and icon. Changes go live as soon as you save, and every edit is logged.

- Keep the record, file or tag in place. We check it every day, and if it’s missing for a week, editing pauses until you prove it again.
- The server URL can move only within the domain you proved, and an npm package only within its scope. After a new URL or package, we check the server again, so the tools and sign-in shown on the page follow.
- If you signed in more than 15 minutes ago, changing a link, the server URL, the package or the setup notes asks you to confirm it’s you first.
- Each change you save appears in the listing’s public History as a change by the server owner, with the text before and after (for setup notes, only that they changed) but without your name or account, and is emailed to people who follow the listing. If we undo an edit, we hide its entry.
- With a DNS record, you can also request the verified checkmark from your account.
- Your account shows each listing’s stats: daily views, clicks on its buttons (copy, add to a client, setup tabs, links), where visitors came from, their countries and the page language. The counts are anonymous, one per visitor a day, without bots; see the [privacy policy](https://mcp.tc/privacy).

## The verified checkmark

The checkmark after a server’s name says who runs it. It isn’t a security review. Official servers of well-known vendors get it after a check by hand. Anyone else can prove they control the domain with a DNS record:

1. Search for your listing on the [checkmark page](https://mcp.tc/verify) and open it.
2. Add the TXT record it shows, `mcp-tc-verification=…`, under `_mcp-tc` or on the domain itself.
3. Press **Request the checkmark**. We look the record up right away, and if it’s there, a person reviews the request.
4. Keep the record. We check it every day, and if it’s gone, we review the listing and usually remove the checkmark.

The domain is the one in your server’s URL. Your homepage’s domain counts when the server runs locally or its URL is on a hosting platform’s domain. Once a listing is verified, automatic updates no longer change its URLs, package or vendor.

## Badges and embeds

Show your listing in your README or on your website. Every embed uses your server’s own URL or package, links back to the listing, and sets no cookies. Replace `deepwiki` with your listing’s name.

### README badge

`Markdown`:

```
[![DeepWiki on mcp.tc](https://mcp.tc/i/deepwiki/badge.svg)](https://mcp.tc/i/deepwiki)
```

![Badge preview, light](https://mcp.tc/i/deepwiki/badge.svg?theme=light&v=747f8726)![Badge preview, dark](https://mcp.tc/i/deepwiki/badge.svg?theme=dark&v=747f8726)

### Card for your website

One script tag. It shows what the server needs, its URL or install command with a Copy button, and one-click buttons for Claude Code, Cursor, VS Code and claude.ai, for the clients that can use it:

`HTML`:

```
<script src="https://mcp.tc/w/deepwiki.js" async></script>
```

### iframe

For pages that don’t allow scripts:

`HTML`:

```
<iframe src="https://mcp.tc/embed/deepwiki" title="DeepWiki on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>
```

The **Embed** section of your listing has all of these filled in, with live previews. [Badges and embeds](https://mcp.tc/embed) covers themes, sizes and the listing JSON. Embeds are in English unless you add `?lang=it`, `fr`, `de` or `es` to their address.

## From the command line

[mcp-tc](https://mcp.tc/cli), our open-source command-line tool, helps here too. It needs Node.js 20 or later:

- `npx mcp-tc create my-server` starts a new MCP server project from a template: Streamable HTTP on Express, Cloudflare Workers, or a local server over stdio.
- `npx mcp-tc check https://mcp.example.com/mcp` reads your server the way mcp.tc does and lists what would stop clients or the listing from reading it well. It can’t tell you whether the server will be listed.
- `npx mcp-tc card` makes a server card and a `server.json` for the official MCP Registry.
- `npx mcp-tc submit https://mcp.example.com/mcp` sends the same suggestion as the [Submit](https://mcp.tc/submit) page and waits for the result.
- `npx mcp-tc badge <slug>` prints the README badge and the website snippets of your listing.
- `npx mcp-tc dns-check example.com` looks for your `mcp-tc-verification=` TXT record at the domain and under `_mcp-tc`, so you can check it before you request the checkmark.

## Changes and removal

Use the [report page](https://mcp.tc/report) to have a listing removed, your own included, or to correct what you can’t edit yourself. Show that it’s yours with an email from your domain or a commit that mentions mcp.tc. A person reads every report.

A removed listing’s link answers 410 Gone, to browsers and MCP clients alike, and the listing leaves the sitemaps and the registry API (where clients that ask see it as deleted for 180 days). A renamed listing keeps its old link: browsers are sent on to the new one.

Your listing’s link is always a page. A client that tries to connect to it gets an error that names your server’s own URL or install command, so users who paste the wrong link find the right one. mcp.tc never passes MCP traffic on to your server.

---
Source: https://mcp.tc/docs/server-owners. Markdown version for AI agents (ask for `text/markdown` or add `.md` to the address). Site overview: https://mcp.tc/llms.txt
