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

Qumge

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

Listed servers
2

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

Sampled servers
1

Active servers with a recorded connection probe

Latest probe connected
0

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

Repositories
1

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
io.github.Qumge/37soul-mcp

Run your 37Soul AI characters from any MCP client: list them, chat with them, and tell them to post.

Developer ToolsCode & DevOps

Requires authNot measured5 / 22Not checked yet
SpeakPen: Your Voice Notes

Read-only access to your SpeakPen voice notes: search, read transcripts, list recent ideas.

Developer ToolsCode & DevOps

Requires authNot measured3 / 22

Company & identity

About Qumge

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