MCP servers observed by Lowdown
io.pingoru/status MCP server: daily status and tool changes
On the latest daily check (2026-11-05) its remotes differed: 1 answered tools/list, 1 required authentication. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-29; no tool definition change in 7 compared days; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.pingoru/status
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.pingoru/status?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-05: the server its remotes gave different results.
- Observed days in the last 30: 8
- Answered initialize and tools/list: 0
- Required authentication: 0
- No response: 0
- Remotes differed: 8
Does it require authentication?
It did not return HTTP 401/403 on any of the 8 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 7 compared days.
What tools does it list?
6 tools on 2026-11-05:
component_statusincident_detailprovider_componentsprovider_incidentsprovider_statussearch_providers
MCP Registry declaration
- Registry name:
io.pingoru/status - Declared version: 1.0.0
- Status: active
- Declared hosts:
pingoru.io