io.github.spanlens/mcp-server
io.github.spanlens/mcp-server
Is the io.github.spanlens/mcp-server MCP server down? No. It is up and needs network, probed 2026-10-27.
Query Spanlens LLM observability from Cursor, Claude Desktop, or Continue via MCP.
needs network probed 2026-11-14 · unchanged since 2026-10-27
MCP error -32000: Connection closed [spanlens-mcp] auth failed: fetch failed
- Run it
- npx -y @spanlens/mcp-server@0.3.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/spanlens/Spanlens
- Registry
- active, updated 2026-09-28 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- SafeNode MCP Gateway io.github.sp3ak/safenode-mcp-gateway · crashed on start
- Sunstone Weave: Local Semantic Code Search io.github.space-bacon/blackwindow-weave-mcp · needs env
- io.github.spacecowboyian/brains · needs env
- io.github.spacepacket1/e3d-pilot · crashed on start
- spec-guard io.github.spec-family/spec-guard · alive
- spec-harness io.github.spec-family/spec-harness · crashed on start
- io.github.specshield-io/specshield-mcp-server · alive
- io.github.specshield26/specshield-mcp-server · alive
Servers that mention observability or continue.
- AnomalyArmor ai.anomalyarmor/armor-mcp · needs auth
- ai.diezx/diezx · no DNS
- ai.getvda/llm-observability-orchestration · newer protocol
- ai.getvda/llm-observability-orchestration-agent-langchain · newer protocol
- ai.getvda/llm-observability-orchestration-agent-langchain-community · newer protocol
- ai.getvda/llm-orchestration-observability-agent · newer protocol
- ai.noveum/noveum · needs auth
- Lukija app.lukija/lukija · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server tries to reach the network on start. The probe runs in a container with the network off, so a server that connects lazily, on the first tool call, is measured.