MCP servers observed by Lowdown
app.openkrill/catalog-qa MCP server: daily status and tool changes
Answered initialize and tools/list on all 24 daily checks recorded in the last 30 days (2026-10-26 to 2026-11-18); 7 tools listed. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-26; tool definitions last changed on 2026-11-05 after 10 days without change; 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:app.openkrill/catalog-qa
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.openkrill/catalog-qa?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 24
- Answered initialize and tools/list: 24
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 24 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 1 of 23 compared days.
- 2026-11-05: input or output schemas changed, descriptions changed, tool names changed, server version changed; tool count 6 → 7
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:
app.openkrill/catalog-qa - Declared version: 1.0.1
- Status: active
- Declared hosts:
catalogqa.openkrill.app
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:app.openkrill/catalog-qa", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.openkrill/catalog-qa?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).