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/jvm/usql-mcpWrote 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/jvm/usql-mcp/usql-mcp)<a href="https://agentmods.dev/mcp/jvm/usql-mcp/usql-mcp"><img src="https://agentmods.dev/badge/mcp/jvm/usql-mcp/usql-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
usql-mcp 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 6d 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
{ "usql-mcp": { "command": "npx", "args": [ "-y", "usql-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.
- 6d ago First seen · 9 lines scan A 2fdbf49254fb
usql-mcp is an MCP server published in the GitHub repository jvm/usql-mcp (3 stars, last pushed 6mo 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
dryrun
PostgreSQL schema intelligence from a committed snapshot. No connection, no credentials. Runs locally from the @boringsql/dryrun npm package.
remem
Local-first automatic memory for Claude Code and Codex: capture, distill, recall from SQLite. Runs locally from the @remem-ai/remem npm package.
alloydb-omni
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package.
migrationpilot
112 rules that catch dangerous PostgreSQL migrations, plus a pass/fail gate to call before any DDL. Runs locally from the migrationpilot npm package.
mcp-registry-finder
MCP server "mcp-registry-finder" as configured in bharat3645/mcp-registry-finder. Runs locally from the mcp-registry-finder npm package.
litescope
Operations toolchain for SQLite, Cloudflare D1 & Turso: inspect, diff, migrate, monitor & repair. Runs locally from the litescope npm package. Needs 2 environment variables to run.