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

LuminariSoftwares

Explore the MCP servers published by LuminariSoftwares, 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
Code Guardian

Safe to run? Will it work? Complete? An A-F grade for any repo, plus a verify loop. Never runs it.

Developer ToolsCode & DevOps

Not measuredNot measured4 / 6Not checked yet
Context Guardian

40 turns: 1,130,722 tokens upstream -> 161,141. A fail-open compaction proxy for local models.

Developer ToolsCode & DevOps

Not measuredNot measured4 / 6Not checked yet
Stack Guardian

Health doctor for a home AI stack: Ollama nodes, GPUs and tailnet, with graded confidence.

Developer ToolsCode & DevOps

Not measuredNot measured4 / 6Not checked yet
Tool Guardian

Too many MCP servers eating your context? A router that loads each tool's schema only when needed.

Developer ToolsCode & DevOps

Not measuredNot measured4 / 6Not checked yet

Company & identity

About LuminariSoftwares

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