MCP servers observed by Lowdown
blue.brick/hub MCP server: daily status and tool changes
Answered initialize and tools/list on the last 2 consecutive daily checks (2026-11-17 to 2026-11-18); 14 tools listed. 26 of 30 observed days in the last 30 had this result. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-19; tool definitions last changed on 2026-11-18 after 30 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:blue.brick/hub
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:blue.brick/hub?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: 30
- Answered initialize and tools/list: 26
- Required authentication: 0
- No response: 4
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 30 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 1 of 26 compared days.
- 2026-11-18: input or output schemas changed
What tools does it list?
14 tools on 2026-11-18:
agent_livenessagent_trustdescribe_toolsget_agentget_startedhandshakeinvoke_toollist_paid_endpointsregister_agentsearchsearch_agentssearch_toolssubmission_statusverify_endpoint
MCP Registry declaration
- Registry name:
blue.brick/hub - Declared version: 0.1.5
- Status: active
- Declared hosts:
brick.blue
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:blue.brick/hub", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:blue.brick/hub?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:blue.brick/hub -- npx -y brick-blue-mcp
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).