Home / MCP registry index / dev.ghlmcp/highlevel-agency-mcp
HighLevel Agency & Builder MCP
dev.ghlmcp/highlevel-agency-mcp in the official MCP registry.
Endpoint https://ghlmcp.dev/mcp. Source: github.com/mooshee/highlevel-agency-mcp.
The registry describes it as: Full-stack GoHighLevel (GHL) MCP for funnels, client DNS/SSL, LeadShield spam blockers & snapshots.
We read its 13 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
ghl_agency_connection_health ghl_agency_tools_search ghl_agency_tools_enable ghl_agency_contexts ghl_agency_doctor ghl_agency_locations ghl_snapshot_diff_audit ghl_site_builder_sync ghl_domain_ssl_onboard ghl_workflow_ivr_builder ghl_custom_values_audit ghl_phone_wallet_audit ghl_user_role_governance
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/dev-ghlmcp-highlevel-agency-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.