HighLevel Agency & Builder MCP
REMOTE · WWW.GHLAGENCYMCP.COM
Full-stack GoHighLevel (GHL) MCP for funnels, client DNS/SSL, LeadShield spam blockers & snapshots.
Available components
Last scanned (41 minutes ago)
Scores higher than 13% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 30 Oct 26 −45
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.10 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: fail → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
- DNSSEC: fail → pass ▲ security
- Tool “ghl_agency_locations” rewrote its description, which is the text the model reads security
- Tool “ghl_agency_tools_enable” rewrote its description, which is the text the model reads security
- Tool “ghl_agency_tools_search” rewrote its description, which is the text the model reads security
- Tool “ghl_custom_values_audit” rewrote its description, which is the text the model reads security
- Tool “ghl_site_builder_sync” rewrote its description, which is the text the model reads security
- Tool “ghl_user_role_governance” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- “ghl_agency_tools_enable” added an optional parameter “policyPreset” cosmetic
- “ghl_agency_tools_search” added an optional parameter “category” cosmetic
- “ghl_user_role_governance” added an optional parameter “locationId” cosmetic
- “ghl_agency_tools_search” reworded the description of “query” cosmetic
- “ghl_user_role_governance” reworded the description of “preset” cosmetic
- “ghl_agency_locations” dropped the optional parameter “action” cosmetic
- “ghl_agency_locations” dropped the optional parameter “yes” cosmetic
- “ghl_agency_tools_enable” dropped the optional parameter “pack” cosmetic
- “ghl_agency_tools_enable” dropped the optional parameter “tools” cosmetic
- “ghl_agency_tools_search” dropped the optional parameter “pack” cosmetic
- “ghl_custom_values_audit” dropped the optional parameter “action” cosmetic
- “ghl_user_role_governance” dropped the optional parameter “action” cosmetic
- Tool “ghl_agency_locations” changed its title: Manage HighLevel Sub-Account Locations → Inspect HighLevel Sub-Account Location cosmetic
- Tool “ghl_agency_tools_enable” changed its title: Enable HighLevel Agency Tool Pack → Configure Safe-Writes Policy Preset cosmetic
- Tool “ghl_agency_tools_search” changed its title: Search HighLevel Agency MCP Tools → Search HighLevel Blueprints & Templates cosmetic
- Tool “ghl_custom_values_audit” changed its title: Sync Custom Values & Audit Merge Tags → Audit Custom Values & Merge Tags cosmetic
- Tool “ghl_site_builder_sync” changed its title: Sync Funnel & Website Page Layouts → Sync Funnel Step Layout cosmetic
- Tool “ghl_user_role_governance” changed its title: Manage Least-Privilege User Role Presets → Audit Least-Privilege User Role Presets cosmetic
- 26 Oct 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://www.ghlagencymcp.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ghlagencymcp.com | CN=WE1,O=Google Trust Services,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 787ddfa9ed72904a0e649e5125e6d989 |
| SANs: ghlagencymcp.com, www.ghlagencymcp.com, *.www.ghlagencymcp.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of www.ghlagencymcp.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ghlagencymcp.com. | present | 2371 | 13 | Verified |
| www.ghlagencymcp.com. | Verified address RRset verified with the apex keys |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 308 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'none'; frame-ancestors 'none'; base-uri 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.ghlagencymcp.com/mcp | Redirected | 308 | https://ghlagencymcp.com/mcp |
| http (plaintext) | http://www.ghlagencymcp.com/mcp | HTTPS enforced | 308 | https://ghlagencymcp.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ghl_agency_connection_health Check HighLevel Agency MCP Connection Health ~93
Check HighLevel Agency MCP connection health, active Safe-Writes Policy preset, and progressive discovery status. Example: ghl_agency_connection_health({"context":"moosh-growth","includeDoctor":true})
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Optional HighLevel company ID override. |
| context | string | – | Target HighLevel agency account context. |
| includeDoctor | boolean | – | Run an inline PIT and session readiness doctor check. |
No output schema declared.
No examples provided.
ghl_agency_contexts List HighLevel Account Contexts ~56
List configured HighLevel agency account contexts and known sub-account locations without mutating state. Example: ghl_agency_contexts({"context":"moosh-growth"})
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Optional HighLevel context name to inspect. |
No output schema declared.
No examples provided.
ghl_agency_doctor Run HighLevel Agency Doctor Audit ~70
Verify HighLevel agency Private Integration Token (PIT), CRM session, company, and seed location readiness. Example: ghl_agency_doctor({"context":"moosh-growth"})
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Optional HighLevel company ID. |
| context | string | – | Target HighLevel agency context. |
No output schema declared.
No examples provided.
ghl_agency_locations Inspect HighLevel Sub-Account Location ~86
Inspect a HighLevel sub-account location profile, timezone, and readiness configuration without mutating state. Example: ghl_agency_locations({"context":"moosh-growth","location":"loc_123"})
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Optional HighLevel company ID. |
| context | string | – | Target HighLevel agency context. |
| location | string | – | Target sub-account location ID or alias. |
No output schema declared.
No examples provided.
ghl_agency_tools_enable Configure Safe-Writes Policy Preset ~72
Configure the active Safe-Writes Policy preset (read-only, dry-run-first, or standard) for the current HighLevel agency session. Example: ghl_agency_tools_enable({"policyPreset":"dry-run-first"})
| Name | Type | Req | Description |
|---|---|---|---|
| policyPreset | string | – | Safe-Writes Policy preset to apply to the current session. |
No output schema declared.
No examples provided.
ghl_agency_tools_search Search HighLevel Blueprints & Templates ~69
Search HighLevel automation blueprint presets and configuration templates by keyword or category. Example: ghl_agency_tools_search({"query":"funnel","category":"onboarding"})
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional template category filter. |
| query | string | – | Keyword to search across blueprint templates and descriptions. |
No output schema declared.
No examples provided.
ghl_custom_values_audit Audit Custom Values & Merge Tags ~61
Read-only audit of sub-account Custom Values and SMS/email templates for broken merge tags or missing placeholders. Example: ghl_custom_values_audit({"locationId":"loc_123"})
| Name | Type | Req | Description |
|---|---|---|---|
| locationId | string | – | Target HighLevel sub-account location ID. |
No output schema declared.
No examples provided.
ghl_domain_ssl_onboard Onboard Client Domain, DNS & Branded Links ~109
Plan, verify, and attach HighLevel custom funnel domains and branded short-link CNAME/A/TXT records with SSL checks. Example: ghl_domain_ssl_onboard({"locationId":"loc_123","domain":"go.example.com","dryRun":true})
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Custom funnel, website, or branded-link hostname. |
| dryRun | boolean | – | Verify DNS propagation and preview changes before applying. |
| locationId | string | – | Target HighLevel sub-account location ID. |
No output schema declared.
No examples provided.
ghl_phone_wallet_audit Audit LC Phone Numbers for Wallet Drain ~64
Read-only audit of sub-account LC Phone numbers, number pools, forwarding loops, and unassigned monthly wallet drain. Example: ghl_phone_wallet_audit({"locationId":"loc_123"})
| Name | Type | Req | Description |
|---|---|---|---|
| locationId | string | – | Target HighLevel sub-account location ID. |
No output schema declared.
No examples provided.
ghl_site_builder_sync Sync Funnel Step Layout ~120
Synchronize a HighLevel funnel step layout while preserving 2-step carts and 1-click upsells. Example: ghl_site_builder_sync({"locationId":"loc_123","funnelId":"fnl_1","dryRun":true})
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | Preview layout and CSS diff without mutating the live page. |
| funnelId | string | – | Target funnel or website ID. |
| locationId | string | – | Target HighLevel sub-account location ID. |
| stepId | string | – | Optional funnel step or page ID. |
No output schema declared.
No examples provided.
ghl_snapshot_diff_audit Diff Sub-Account Against Master Snapshot ~83
Compare a live HighLevel client sub-account against a reference Master Snapshot without overwriting assets. Example: ghl_snapshot_diff_audit({"locationId":"loc_123","snapshotId":"snap_456"})
| Name | Type | Req | Description |
|---|---|---|---|
| locationId | string | – | Live HighLevel sub-account location ID to audit. |
| snapshotId | string | – | Reference Master Snapshot ID to compare against. |
No output schema declared.
No examples provided.
ghl_user_role_governance Audit Least-Privilege User Role Presets ~93
Read-only audit of sub-account staff permissions against least-privilege role presets (va-support, sales-rep, client-admin, agency-admin). Example: ghl_user_role_governance({"locationId":"loc_123","preset":"va-support"})
| Name | Type | Req | Description |
|---|---|---|---|
| locationId | string | – | Target HighLevel sub-account location ID. |
| preset | string | – | Least-privilege role preset to audit against. |
No output schema declared.
No examples provided.
ghl_workflow_ivr_builder Build Workflows, LeadShield Guards & Spam-Shield IVRs ~107
Synthesize and publish HighLevel workflows, LeadShield contact form spam guards, and call-screening IVRs. Example: ghl_workflow_ivr_builder({"locationId":"loc_123","preset":"leadshield-form-guard","dryRun":true})
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | Preview workflow graph diff before publishing. |
| locationId | string | – | Target HighLevel sub-account location ID. |
| preset | string | – | Workflow or IVR blueprint preset to compile. |
No output schema declared.
No examples provided.
How do I install the HighLevel Agency & Builder MCP server?
HighLevel Agency & Builder MCP is a hosted endpoint at https://www.ghlagencymcp.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.ghlagencymcp.com
claude mcp add --transport http com-ghlagencymcp-highlevel-agency-mcp 'https://www.ghlagencymcp.com/mcp'
What is the HighLevel Agency & Builder MCP server?
HighLevel Agency & Builder MCP is listed in the public MCP registry as com.ghlagencymcp/highlevel-agency-mcp. Full-stack GoHighLevel (GHL) MCP for funnels, client DNS/SSL, LeadShield spam blockers & snapshots. This page covers its hosted endpoint (https://www.ghlagencymcp.com/mcp).
Is the HighLevel Agency & Builder MCP server safe to use?
HighLevel Agency & Builder MCP scores 26 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the HighLevel Agency & Builder MCP server expose?
HighLevel Agency & Builder MCP exposes 13 tools: ghl_agency_connection_health, ghl_agency_tools_search, ghl_agency_tools_enable, ghl_agency_contexts, ghl_agency_doctor, and 8 more. Their descriptions and schemas cost roughly 1,083 tokens of context every time the server is loaded.
Does the HighLevel Agency & Builder MCP server require authentication?
Its publisher declares no required credentials for HighLevel Agency & Builder MCP. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the HighLevel Agency & Builder MCP server still maintained?
HighLevel Agency & Builder MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.