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/ajitpratap0/GoSQLXWrote 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/ajitpratap0/gosqlx/gosqlx-gosqlx)<a href="https://agentmods.dev/mcp/ajitpratap0/gosqlx/gosqlx-gosqlx"><img src="https://agentmods.dev/badge/mcp/ajitpratap0/gosqlx/gosqlx-gosqlx/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/ajitpratap0/gosqlx/gosqlx-gosqlx"><img src="https://agentmods.dev/badge/mcp/ajitpratap0/gosqlx/gosqlx-gosqlx.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
gosqlx 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 yesterday.
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
{
"gosqlx": {
"type": "http",
"url": "${GOSQLX_MCP_URL:-https://mcp.gosqlx.dev/mcp}"
}
}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.
- yesterday First seen · 6 lines scan A 0672e657c4a4
gosqlx is an MCP server published in the GitHub repository ajitpratap0/GoSQLX (120 stars, last pushed today), licensed Apache-2.0. 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-10-22.
Other mcp servers, from other repositories
gograph
MCP server "gograph" as configured in ozgurcd/gograph. Launched with https://github.com/ozgurcd/gograph/releases/download/v1.7.4/gograph_1.7.4_darwin.
homebutler
Tells an agent what changed on a server since it last looked - status, Docker, backups, Proxmox. Runs locally from the homebutler npm package.
lsp
MCP server "lsp" as configured in blackwell-systems/agent-lsp. Launched with agent-lsp go:gopls.
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
sqlike-mcp
SQL static analysis & query-equivalence for Postgres, MySQL, SQLite, and SQL Server. Runs locally from the @sqlike/mcp npm package. Needs 1 environment variable to run.
quarry
AI-native database workbench: one safety-railed query kernel, many faces (CLI / GUI / agent skill / MCP). Runs locally from the quarry-db Python package.