01 Readability
Can agents read you?
llms.txt and its size budget, Markdown negotiation, Markdown for real pages rather than a false 404, and content that loads without JavaScript.
///// Open source · MIT
Backwatch checks your live MCP server from outside, the way AI hosts reach it. Nothing to install.
Fix these first
sitemap0 valid sitemap documents, 0 URL entries, 0 invalid documents.markdown-url-fallbackNo usable /index.md with Markdown MIME and an initial H1; no credit without the baseline.json-ld0 JSON-LD blocks; 0 identity entities; 0 with name/description/url; type-appropriate detail: false; 0 invalid Sign-in chain
No MCP server found
example.com has no MCP server, so connectability is unresolved, not failed.
AI bots
13 of 13
can reach the homepage
Works with
///// Why outside
A broken sign-in never reaches your logs, so your dashboards stay green. Tests run before you ship. Hosts change after. Backwatch checks from the side your users are on.
WWW-Authenticate: resource_metadata/.well-known/oauth-protected-resource/.well-known/oauth-authorization-servercode_challenge_methods_supported: S256registration_endpointThe host stops here, and nothing looks wrong on your side.
///// Four pillars
Checked from outside, the way an agent meets your site. Nothing to install on your server, and no account.
01 Readability
llms.txt and its size budget, Markdown negotiation, Markdown for real pages rather than a false 404, and content that loads without JavaScript.
02 Discoverability
/.well-known MCP discovery and server cards, API catalogues, and whether your proxy blocks dot-paths.
03 Connectability
The MCP sign-in chain every host follows: the 401 challenge, protected-resource and authorization-server metadata, PKCE and client registration. With --register, on your own server, it proves each host's callback can register.
04 Presence
Whether your MCP server is listed in the official MCP Registry, where hosts and directories look for it.
///// 1,000 servers, 3 November 2026
We checked a random 1,000 servers from the official MCP Registry on 3 November 2026. Of those that use sign-in, 11% fail before a user ever sees a login page. Most often it is the first step: a 401 that gives the host no way to find the authorization server.
///// CI
Run it in CI. The first run writes a baseline. After that, the job fails only when a check gets worse.
- uses: backwatch/backwatch@v0
with:
url: your-site.com
baseline: .backwatch.json///// Planned pricing
The hosted monitor will run the same checks on a schedule. These are the plans we intend to launch with. Nothing is on sale yet.
Free
$0
Try it on one server
TeamRecommended
$149/mo
One product's MCP server
Business
$399/mo
Several products, or on-call
Annual billing saves about two months. Enterprise plans with multi-region checks and SSO come later.
Compare the plans→--sign-in, you log in yourself in your own browser. No password passes through Backwatch.///// Coming next
The hosted monitor will run these checks on a schedule and tell you when one breaks, and whether it was your deploy or the host. Join the waitlist and we'll tell you when it's ready.
Planned: a free plan, and paid plans from $149 a month.
One email when the monitor is ready. Nothing else, and never shared.