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/keides2/coverity-connect-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/keides2/coverity-connect-mcp/development-coverity-connect-dev)<a href="https://agentmods.dev/mcp/keides2/coverity-connect-mcp/development-coverity-connect-dev"><img src="https://agentmods.dev/badge/mcp/keides2/coverity-connect-mcp/development-coverity-connect-dev.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
coverity-connect-dev 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 8d 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
{
"coverity-connect-dev": {
"command": "python",
"args": [
"-m",
"coverity_mcp_server"
],
"cwd": "C:\\Users\\HP\\Docs\\Security\\coverity-connect-mcp",
"env": {
"COVERITY_HOST": "localhost",
"COVERITY_PORT": "5000",
"COVERITY_SSL": "False",
"COVAUTHUSER": "dummy_user",
"COVAUTHKEY": "dummy_key",
"MCP_DEBUG": "True",
"LOG_LEVEL": "DEBUG"
}
}
}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.
- 8d ago First seen · 19 lines scan A de502972b9f5
coverity-connect-dev is an MCP server published in the GitHub repository keides2/coverity-connect-mcp (14 stars, last pushed 8mo 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-30.
Other mcp servers, from other repositories
sharplens
67 semantic C#/.NET analysis tools via Roslyn: navigation, refactoring, codegen, audit. Runs locally from the sharplens-mcp npm package. Needs 3 environment variables to run.
flyto-indexer
Code intelligence MCP server for AI coding agents with impact analysis, semantic search, dependency graphs, and local release gates. Runs locally from the flyto-indexer Python package.
graphpilot
Structural memory for coding agents: callers, callees, blast radius and symbols over MCP. Runs locally from the @graphpilot-oss/graphpilot npm package. Needs 1 environment variable to run.
ellmos-codecommander-mcp
Developer MCP server: code analysis, JSON repair, imports, diffs, regex, format conversion. Runs locally from the ellmos-codecommander-mcp npm package.
sonde
Local code graph for TypeScript, Python and Swift: who calls this, what breaks if I change it. Runs locally from the @cheppulabs/sonde npm package.
godotlens
Godot's own view of your GDScript project: navigation, diagnostics, engine API, scene checks. Runs locally from the godotlens-mcp npm package. Needs 10 environment variables to run.