MCP servers observed by Lowdown
ai.agent-bev/bev-door MCP server: daily status and tool changes
Answered initialize and tools/list on all 30 daily checks recorded in the last 30 days (2026-10-20 to 2026-11-18); 9 tools listed. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-06; no tool definition change in 30 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:ai.agent-bev/bev-door
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.agent-bev/bev-door?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: 30
- Required authentication: 0
- No response: 0
- 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?
No change in tool schemas, descriptions or names across 30 compared days.
- 2026-11-14: server version changed
- 2026-11-05: server version changed
What tools does it list?
9 tools on 2026-11-18:
accept_offercompare_drinkscreate_order_intentfind_producerget_offersget_order_routeget_recordlist_nodessearch_drinks
MCP Registry declaration
- Registry name:
ai.agent-bev/bev-door - Declared version: 0.2.8
- Status: active
- Declared hosts:
mcp.bev-buyer.ai
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:ai.agent-bev/bev-door", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.agent-bev/bev-door?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:ai.agent-bev/bev-door -- npx -y @agent-bev/mcp-server
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).