MCP servers observed by Lowdown

app.bannerproof/bannerproof MCP server: daily status and tool changes

On the latest daily check (2026-11-18) its remotes differed: 1 answered tools/list, 1 required authentication. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-28; no tool definition change in 18 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:app.bannerproof/bannerproof

Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.bannerproof/bannerproof?menu=install-check · other questions: menu

Does it respond?

Latest daily check: 2026-11-18: the server its remotes gave different results.

Does it require authentication?

It returned HTTP 401/403 on 3 of 22 observed days. Lowdown checks without credentials, so the tools behind authentication were not listed.

Did its tools change recently?

No change in tool schemas, descriptions or names across 18 compared days.

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

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.bannerproof/bannerproof", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.bannerproof/bannerproof?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).