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

stcmain

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

Listed servers
4

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

Sampled servers
0

Active servers with a recorded connection probe

Latest probe connected
0

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

Repositories
4

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
What's Allowed

Merged agent permission rules: which settings file wins, and which rules your client ignores.

Developer ToolsCode & DevOps

Not measuredNot measured4 / 6Not checked yet
What's Inherited

What a checkout tells your agent to do: instruction files, hooks, declared MCP servers.

Finance & CryptoPayments & trading

Not measuredNot measured4 / 6Not checked yet
What's Loaded

What fills your agent's context window before a session starts: skill descriptions, memory files.

Developer ToolsCode & DevOps

Not measuredNot measured4 / 6Not checked yet
What's Running

Live OS ground truth for agents: running agent sessions, listening ports, daemons, system load.

Developer ToolsCode & DevOps

Not measuredNot measured4 / 6Not checked yet

Company & identity

About stcmain

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