MCP servers observed by Lowdown
io.arxo/de-bgb MCP server: daily status and tool changes
No successful response on the last 2 consecutive checks (2026-11-15 to 2026-11-18) (Lowdown checks this server every 3 days). Checked from one network location. 2 of 4 checks in the last 30 days had this result. npm has returned 404 for @arxo/mcp-de-bgb since 2026-11-14; it was available before (checked 2026-11-18). MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; no tool definition change in 1 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.arxo/de-bgb
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.arxo/de-bgb?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server did not respond.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 2
- Required authentication: 0
- No response: 2
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 1 compared days.
What tools does it list?
21 tools on 2026-11-12:
law_answer_capabilitieslaw_arguelaw_asklaw_capture_answerlaw_case_asklaw_editionslaw_explainlaw_inspectlaw_packageslaw_passportlaw_prepare_answerlaw_processlaw_process_runlaw_publish_answerlaw_querylaw_reportlaw_revoke_answerlaw_ruleslaw_screenlaw_searchlaw_sources
MCP Registry declaration
- Registry name:
io.arxo/de-bgb - Declared version: 0.1.9
- Status: active
- Declared hosts:
mcp.arxo.io
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:io.arxo/de-bgb", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.arxo/de-bgb?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:io.arxo/de-bgb -- npx -y @arxo/mcp-de-bgb
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).