MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

Terms of use

Effective 11 November 2026. Last updated 11 November 2026.

These terms cover the MCP Heartbeat website, MCP endpoint, and JSON API at mcpheartbeat.com. By using the service, you agree to them. The privacy policy explains how information is handled.

The service

MCP Heartbeat publishes automated measurements of public MCP servers. Figures are timestamped probe results. They are not a review, rating, grade, certification, or recommendation. Catalog metadata comes from the Official MCP Registry under CC0. MCP Heartbeat is not the Official MCP Registry and is not endorsed by it.

Probes only run against endpoints listed in the Official MCP Registry, in our manual seed list, or submitted to us, and only with initialize, notifications/initialized, and tools/list.

Acceptable use

You may use the directory, the MCP endpoint, and the JSON API for your own research and to build on the published measurements. You must stay within the published rate limits: 60 MCP calls per minute per hashed network address, and 100 JSON API calls per UTC day per hashed network address. Do not attempt to bypass those limits, disrupt the service, or submit false claims or listings.

Publishers may request a listing claim through the claim form. We may accept, reject, or reverse a claim.

No warranty

The service is provided as is, without warranties of any kind. Measurements can be incomplete, delayed, or wrong. We may change, rate-limit, or discontinue any part of the service.

Contact

Questions about these terms: support@mcpheartbeat.com.