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.
npx agentmods add mcp/dmitriusan/mcp-db-analyzer/mcp-db-analyzergit clone --depth 1 https://github.com/Dmitriusan/mcp-db-analyzerWrote 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/dmitriusan/mcp-db-analyzer/mcp-db-analyzer)<a href="https://agentmods.dev/mcp/dmitriusan/mcp-db-analyzer/mcp-db-analyzer"><img src="https://agentmods.dev/badge/mcp/dmitriusan/mcp-db-analyzer/mcp-db-analyzer.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mcp-db-analyzer 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 5d 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
{
"mcp-db-analyzer": {
"command": "npx",
"args": [
"-y",
"mcp-db-analyzer"
],
"env": {
"DATABASE_URL": "",
"DB_DRIVER": ""
}
}
}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.
- 5d ago First seen · 13 lines scan A 906421a1287b
mcp-db-analyzer is an MCP server published in the GitHub repository Dmitriusan/mcp-db-analyzer (1 stars, last pushed 19d 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
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.
mcp-devdb
MCP server "mcp-devdb" as configured in aminyx/mcp-devdb. Runs locally from the mcp-devdb npm package.
anchordb
MCP server "anchordb" as configured in jolovicdev/anchor-db. Runs in Docker (ghcr.io/jolovicdev/anchor-db:1.0.6).
mcp-redis-diagnostics
MCP server for Redis diagnostics — analyze memory usage, slowlog, client connections, and keyspace health with AI-powered recommendations. Runs locally from the mcp-redis-diagnostics npm package. Needs 1 environment variable to run.
mcp-migration-advisor
MCP server for database migration risk analysis — Flyway and Liquibase XML/YAML/SQL support with lock detection and conflict analysis. Runs locally from the mcp-migration-advisor npm package.
schema-sentinel
Data processing toolkit: YAML/JSON to relational tables, schema comparison, and metadata management. Runs locally from the schema-sentinel Python package.