Snapshot — 2026-06-02

MCP Endpoint Reachability & Health Snapshot

Unauthenticated HTTP probe of 34 remote MCP endpoints on 2026-06-02. We measured what is fairly observable without credentials: HTTP reachability, TLS validity, and response latency. Re-test any server live at /tools/mcp-check.

This is not a quality ranking

An unauthenticated probe cannot assess the quality, reliability, tool depth, schema correctness, or true uptime of services that correctly require credentials — which is most production MCP servers. Requiring OAuth or an API key is correct security practice, not a defect. Stripe, GitHub Copilot, HubSpot, Notion, and the other 28 auth-required servers here are not graded or ranked. They are grouped by their expected auth model and listed by HTTP response latency as a neutral infrastructure signal only.

Endpoints Probed 34

HTTP Reachable 32

Auth-Required (correct) 31

Public No-Auth Demo 1

TLS / Reach Issues 2

Probed On 2026-06-02

Methodology & Limitations

Each endpoint was probed once from our VPS using the Hatchloop MCP Checker (open source, reproducible — re-run any server yourself). The probe is unauthenticated: it sends an HTTP request and, where the server permits, attempts an MCP initialize handshake without credentials.

Critical limitation: Production MCP servers correctly gate the initialize handshake behind OAuth or an API key. Our unauthenticated probe cannot see past that gate. We therefore do not score or rank auth-required servers. The only neutral signals measurable without credentials are: HTTP reachability, TLS certificate validity, and response latency. Those are the only columns shown for auth-required servers. Credentialed probing — which would reveal tool count, schema quality, and handshake reliability — is the roadmap for our verified quality registry.

What We Found — 2026-06-02

32 of 34 endpoints are HTTP-reachable — strong infrastructure availability across the ecosystem.
31 endpoints correctly require authentication before completing the MCP handshake. This is the expected, secure design for services that handle user data or have per-account tools.
20 of those 31 auth-required servers respond in under 300ms on HTTP — solid infrastructure even before credentials.
1 server has a TLS certificate hostname mismatch (Useful AI MCP) — a genuine infrastructure issue preventing secure connections.
1 server timed out (402.bot MCP) — no response within the probe window.
1 public no-auth endpoint found — AgentBroker, operated by Hatchloop (us). It is a demo. See the disclosure section below.

Group 1: Auth-Required Endpoints 31 servers — authentication is correct security practice, not a defect — sorted by HTTP response latency

Server	Auth Model	HTTP	TLS	HTTP Latency	Notes
Supabase MCPDatabase	API Key	✓	✓	100ms	Project API key required.
Notion MCPProductivity	OAuth	✓	✓	105ms	OAuth token required for MCP session.
Jina AI MCPSearch & AI	API Key	✓	✓	105ms	Jina API key required.
Airtable MCPDatabase	API Key	✓	✓	106ms	Auth token required to begin session.
Webflow MCPWeb Platform	OAuth	✓	✓	107ms	OAuth required to proceed.
Attio MCPCRM	OAuth	✓	✓	111ms	OAuth required.
PayPal MCPPayments	OAuth	✓	✓	117ms	OAuth required.
Tally MCPForms	API Key	✓	✓	128ms	Tally API key required.
Linear MCPProject Management	OAuth	✓	✓	135ms	OAuth required for MCP session.
Egnyte MCPFile Storage	OAuth	✓	✓	147ms	OAuth required.
Neon MCPDatabase	API Key	✓	✓	157ms	API key required.
Intercom MCPCustomer Support	OAuth	✓	✓	175ms	OAuth required.
Prisma MCPDatabase	API Key	✓	✓	180ms	Access token required.
Sentry MCPDeveloper Tools	OAuth	✓	✓	190ms	OAuth token required.
Ramp MCPFinance	API Key	✓	✓	192ms	Ramp credentials required.
Exa MCPSearch	API Key	✓	✓	199ms	Exa API key required.
Vercel MCPDeveloper Tools	Token	✓	✓	219ms	Vercel token required.
Microsoft Learn MCPDocumentation	Token	✓	✓	229ms	MS access token required.
Square MCPPayments	OAuth	✓	✓	246ms	OAuth required.
Stripe MCPPayments	OAuth	✓	✓	264ms	OAuth required for all MCP endpoints.
Globalping MCPNetwork Tools	Token	✓	✓	302ms	Token required for session.
Netlify MCPDeveloper Tools	OAuth	✓	✓	356ms	Netlify token required.
CrashStory MCPAnalytics	Token	✓	✓	374ms	Auth required. Railway-hosted.
Asana MCPProject Management	OAuth	✓	✓	383ms	OAuth required.
Apify MCPScraping & Automation	API Key	✓	✓	416ms	Apify API token required.
GitHub Copilot MCPDeveloper Tools	Token	✓	✓	412ms	GitHub/Copilot token required.
Semgrep MCPSecurity	API Key	✓	✓	501ms	Semgrep API key required.
DeepWiki MCPKnowledge	Token	✓	✓	531ms	Token required.
HubSpot MCPCRM	OAuth	✓	✓	536ms	OAuth required.
Stack Overflow MCPKnowledge	API Key	✓	✓	596ms	API key required.
Browserbase MCPBrowser Automation	API Key	✓	✓	704ms	API key required.

Group 2: Infrastructure Issues 2 servers — genuine problems observed unauthenticated

Server	Issue	HTTP	TLS	Details
Useful AI MCPUtilities	TLS Error	✕	✕	SSL certificate hostname mismatch. TLS handshake fails before any HTTP response. Needs cert reissue for the correct hostname.
402.bot MCPAI/Commerce	Timeout	✕	✕	No HTTP response within probe window. Server may be down, rate-limiting this IP, or paused.

Disclosure: Our Own Endpoint AgentBroker — operated by Hatchloop, the team that built this checker — listed separately for full transparency

Server	Auth Model	HTTP	Init	Tools	# Tools	Latency	Notes
AgentBroker Hatchloop — our server AI Agents	Public / No Auth	✓	✓	✓	14	305ms	We built this checker and operate this endpoint. It is a public demo that intentionally requires no auth — that is why an unauthenticated probe can complete the full handshake. This is a design choice for a demo, not a meaningful comparison with production auth-gated services.

Check any MCP server yourself

This is a point-in-time snapshot from 2026-06-02. MCP servers change. Re-probe any server above — or test your own — with our free live checker. Runs server-side (no CORS issues), takes ~2 seconds, results are neutral.

Run a Live Check → Browse MCP Servers

What this page cannot tell you

An unauthenticated probe cannot reveal: tool count, schema correctness, actual uptime SLA, handshake reliability, or agent-native features for any auth-required server. For production services, those dimensions matter far more than a raw HTTP response time. We are building a verified registry where server owners supply credentials for authenticated probing, earn a verified badge, and get continuous uptime monitoring. That is the product that would make this data genuinely meaningful. Interested in early access? →

Sources & Methodology

Server list sourced from: awesome-remote-mcp-servers, jaw9c/awesome-remote-mcp-servers, the official MCP registry, and direct discovery. Only servers with public HTTP endpoints are included. One probe per server. All data is a single point-in-time snapshot and may not reflect current state.

Server owner? If you want authenticated data published here, or want to correct a listing, reach out about the verified registry program.