Claim your server

If you publish an MCP server in the official registry, you can claim it on protogrid. A claim gives you hourly probing of the server instead of every 6 hours, a list of your servers with their quality and trust at a glance, and email alerts when your tools change or a check regresses. For servers published as npm or PyPI packages, monitoring also re-reads the dependency graph every day (instead of monthly) and right after “probe now”, so a new advisory in one of your dependencies reaches you the same day. Claiming is free.

Claiming never changes a server’s scores or checks. The public report is the same for everyone; the server page only adds an owner verified mark.

Sign in

Sign in on protogrid.dev with GitHub and open My servers (/account/servers).

GitHub namespaces

Servers named io.github.<your-login>/… are yours by your GitHub sign-in. Press Claim and every server under that namespace is claimed at once; servers you publish there later are claimed automatically. Case does not matter: io.github.Acme and io.github.acme are the same login.

Organization namespaces (io.github.<org>/…) are not claimable yet.

If you rename your GitHub account, the old namespace’s claim is revoked the next time you sign in, and whoever signs in with a login proves its namespace from then on.

Domain namespaces

Servers named after a domain, such as com.example/…, are proven with a DNS TXT record:

1. Add the domain (example.com) under Domains.
2. Publish the TXT record shown there on that domain: name example.com (often written @ in DNS panels), value protogrid-claim=<token>. The token is yours alone; another account’s record never proves anything for you.
3. Press Verify. DNS changes can take a few minutes to become visible; you can check again every 30 seconds.

A domain covers its own namespace and those of its subdomains: example.com proves com.example/… and com.example.api/…. It never covers GitHub namespaces (io.github.*), which only your GitHub sign-in proves. The domain must cover at least one server that is listed in the registry.

protogrid re-checks the record every day. Keep it published: after 7 consecutive days without it, the proof and the claims made through it are revoked, and My servers says why.

Monitoring

Claimed servers can be monitored: protogrid probes their remote endpoints every hour instead of every 6 hours, and backs off more gently when they fail, so you see a recovery sooner. The free plan monitors up to 20 servers; new claims are monitored automatically until the allowance is used, and you choose which ones in My servers. A paid plan with a larger allowance will come with billing.

Probe now asks for a fresh probe of a claimed server’s remote endpoints, for example right after a deploy. Results appear within a couple of minutes. It is available once a day per server.

Alerts

Monitored servers send you an email when:

• a tool definition changes (a tool that kept its name but changed most of its description is highlighted: review it before an agent trusts it);
• a quality check starts failing;
• every remote endpoint has been failing for more than 2 hours;
• the quality score drops 10 points or more below its recent high.

Recoveries are mentioned in the next email. One email covers all your servers, and each server appears at most once a day; the first alert goes out right away and later ones wait for the next day’s email. Emails go to the address your GitHub account shares with protogrid and come from [email protected]. They carry no tracking pixels or tracked links.

Alerts are on when you monitor a server. Turn them off in My servers, or with the one-click link at the bottom of every email. Send a test email checks that they reach your inbox. The same events can also go to your own systems as signed webhooks.

What “owner verified” means

The mark on a server page, and owner: { verified, method, since } in the descriptor’s identity block, say that someone proved control of the server’s namespace, by GitHub sign-in or by DNS, and since when. They never say who: no login, email or name is shown. It is not an audit of the server or its code, and no score depends on it.

Releasing

Release gives up one server; it is not claimed again automatically through the same proof. Remove on a domain drops the proof and every server claimed through it.