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

piiiico

Explore the MCP servers published by piiiico, 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
3

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
check-claim

Check that a source really says what your claim says, before you publish. Verbatim, multi-path.

Developer ToolsCode & DevOps

Responded163 ms14 / 22
Commit — Supply Chain Risk Scoring

Supply chain risk scoring for npm, PyPI, Cargo, and Go. 9 tools. Behavioral signals.

Developer ToolsCode & DevOps

Responded142 ms14 / 22
AgentLair

Give AI agents a real email address, vault, calendar, and task delegation via MCP.

ProductivityCommunication & messaging

Requires authNot measured5 / 22Not checked yet

Company & identity

About piiiico

piiiico publishes MCP servers under the io.github.piiiico 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