Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/drjerryrelth/ghl-command-feedbackWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/drjerryrelth/ghl-command-feedback/ghl-command)<a href="https://agentmods.dev/mcp/drjerryrelth/ghl-command-feedback/ghl-command"><img src="https://agentmods.dev/badge/mcp/drjerryrelth/ghl-command-feedback/ghl-command/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/drjerryrelth/ghl-command-feedback/ghl-command"><img src="https://agentmods.dev/badge/mcp/drjerryrelth/ghl-command-feedback/ghl-command.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ghl-command scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "ghl-command": { "command": "npx", "args": [ "-y", "@elitedcs/ghl-mcp" ], "env": {} } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 10 lines scan A d19c6215048d
ghl-command is an MCP server published in the GitHub repository drjerryrelth/ghl-command-feedback (1 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
gohighlevel-mcp-starter
MCP server "gohighlevel-mcp-starter" as configured in rockurbusinesscs-ship-it/gohighlevel-mcp-starter. Runs locally from the gohighlevel-mcp-starter npm package.
sharpspring-mcp-server
MCP server "sharpspring-mcp-server" as configured in boyddriesen/sharpspring-mcp-server. Runs locally from the sharpspring-mcp-server npm package. Needs 3 environment variables to run.
ghl-mcp
MCP server "ghl-mcp" as configured in AustinMander/ghl-mcp. Runs locally from the ghl-mcp npm package. Needs 2 environment variables to run.
ghl-mcp
MCP server "ghl-mcp" as configured in vmproductions631-tech/gohighlevel-mcp. Runs locally from the ghl-mcp npm package.
ghl-mcp-server
GoHighLevel MCP Server for Claude Desktop and ChatGPT integration. Runs locally from the ghl-mcp-server npm package.
posthog
MCP server "posthog", hosted remotely at mcp.posthog.com, as configured in macro-inc/macro.