MCP servers observed by Lowdown

app.ghlmcp/highlevel-agency-mcp MCP server: daily status and tool changes

Did not answer as an MCP server on the last 17 consecutive daily checks (2026-11-02 to 2026-11-18). MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-28; no tool definition change in 2 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.ghlmcp/highlevel-agency-mcp

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

Does it respond?

Latest daily check: 2026-11-18: the server did not answer as an MCP server.

Does it require authentication?

It did not return HTTP 401/403 on any of the 22 observed days. Lowdown checks without credentials.

Did its tools change recently?

No change in tool schemas, descriptions or names across 2 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.ghlmcp/highlevel-agency-mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.ghlmcp/highlevel-agency-mcp?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).