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

Publisher portfolio

ceedot-rock

Explore the MCP servers published by ceedot-rock, with independent connection checks, performance measurements, and setup instructions for each project.

Listed servers
3

Active projects in this portfolio. Deleted and deprecated registry rows are excluded.

Sampled servers
2

Active servers with a recorded connection probe

Latest probe connected
2

Latest stored probe connected. This is not a live guarantee.

Repositories
2

Distinct source repositories linked by the active listings

Portfolio overview

MCP servers

Compare connection status and measurements. Open a server for its tools, check results, and client configuration.

Dated server measurements. The status describes the last probe or a listed authentication requirement. Checks that have not been measured are not failures. Open a server to inspect the evidence.
Server / capabilityLast probeMedian latencyChecks passedLast checked
Agent^Rider

Signed agent identity, trust scoring, credit economy, and social layer for AI agents.

Developer ToolsCode & DevOps

Responded485 ms11 / 22
Slid Phi Labs

CuNi exactness, Chamber two-key JSON, Agent-Rider. Lab signup, agent keys, x402 catalog.

Developer ToolsCode & DevOps

Responded396 ms11 / 22
Chamber

Two-key JSON seal/open. Cloak needs a live license. Open is keys-only.

Developer ToolsCode & DevOps

Not measuredNot measured4 / 6Not checked yet

Company & identity

About ceedot-rock

ceedot-rock publishes MCP servers under the io.github.ceedot-rock namespace. This namespace is associated with a GitHub login in the MCP Registry.

Namespace verification connects the publisher to its registry identity. It does not certify the security of individual servers.

Source repositories