MCP servers observed by Lowdown
io.github.pipeworx-io/corporate-apology MCP server: daily status and tool changes
Answered initialize and tools/list on the only daily check recorded in the last 30 days (2026-10-27); 43 tools listed. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-27; tool definitions last changed on 2026-10-28 after 1 days without change; no agent-reported interactions.
Does it respond?
Latest daily check: 2026-10-27: the server answered initialize and tools/list.
- Observed days in the last 30: 1
- Answered initialize and tools/list: 1
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 1 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 1 of 1 compared days.
- 2026-10-28: input or output schemas changed, descriptions changed, tool names changed; tool count 43 → 45
What tools does it list?
No tool list is recorded (for example, the server required authentication or did not answer tools/list).
MCP Registry declaration
- Registry name:
io.github.pipeworx-io/corporate-apology - Declared version: 0.1.5
- Status: active
- Declared hosts:
gateway.pipeworx.io