MCP servers observed by Lowdown
ai.cobbles/cobbles MCP server: daily status and tool changes
No Lowdown daily check since 2026-10-17 (11 days ago), so no current connectivity is stated. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-06; 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:ai.cobbles/cobbles
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.cobbles/cobbles?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-10-17: the server did not respond. That check is 11 days old, so it is not a current status.
- Observed days in the last 30: 12
- Answered initialize and tools/list: 0
- Required authentication: 0
- No response: 12
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 12 observed days. Lowdown checks without credentials.
Did its tools change recently?
Fewer than two days with a complete tools/list observation from the same remote, so nothing was compared.
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:
ai.cobbles/cobbles - Declared version: 1.0.0
- Status: deprecated
- Declared hosts:
api.cobbles.ai