About the project

Independent MCP server monitoring.

MCP Status Hub helps developers understand which published MCP servers are reachable, which protocol capabilities they expose, and how reliably they respond over time.

What we measure

For public remote endpoints, monitoring separates network reachability, MCP protocol negotiation, and safe tools/list capability discovery. We record qualified status, latency, uptime aggregates and incidents without executing arbitrary MCP tools.

Where the data comes from

Server names, descriptions, packages and endpoint metadata come from the official MCP Registry. Operational observations are collected independently by MCP Status Hub and display their freshness and monitoring limitations.

What a status means

  • Operational means the required network and MCP checks succeeded.
  • Auth Required means a remote endpoint exists but cannot be fully tested without credentials.
  • Local Only means public uptime monitoring does not apply.
  • Unknown means there is not enough recent comparable evidence.

Independent project

MCP Status Hub is an independent service. It is not the official MCP Registry and is not affiliated with or endorsed by Anthropic. Registry metadata remains attributable to its original publishers and sources.