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/vivekchand/clawmetry/software-factory-clawmetrygit clone --depth 1 https://github.com/vivekchand/clawmetryWrote 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/vivekchand/clawmetry/software-factory-clawmetry)<a href="https://agentmods.dev/mcp/vivekchand/clawmetry/software-factory-clawmetry"><img src="https://agentmods.dev/badge/mcp/vivekchand/clawmetry/software-factory-clawmetry.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
software-factory-clawmetry 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
{
"software-factory-clawmetry": {
"type": "http",
"url": "https://api.factory.8090.dev/v2/mcp",
"headers": {
"X-Sofa-Mcp-Project-Id": "b415065f-ab2f-4f53-8864-0c009fd098cb"
}
}
}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 · 9 lines scan A f1a280d5701d
software-factory-clawmetry is an MCP server published in the GitHub repository vivekchand/clawmetry (405 stars, last pushed today), 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
signoz-mcp-server
MCP server "signoz-mcp-server" as configured in SigNoz/signoz-mcp-server. Runs in Docker (docker.io/signoz/signoz-mcp-server:v0.9.0).
superlog
Open-source agent that observes and fixes your application. Query logs, traces, metrics, incidents. Remote server at api.superlog.sh.
Dynatrace-mcp
MCP server "Dynatrace-mcp" as configured in dynatrace-oss/dynatrace-mcp. Runs locally from the @dynatrace-oss/dynatrace-mcp-server npm package. Needs 5 environment variables to run.
aegisflow
MCP server "aegisflow" as configured in saivedant169/AegisFlow. Launched with bash scripts/mcp-stdio-bridge.sh.
zabbix-mcp
MCP server for Zabbix management. Runs locally from the zabbix-mcp Python package. Needs 16 environment variables to run.
mcp-vmanomaly
MCP server "mcp-vmanomaly" as configured in VictoriaMetrics/mcp-vmanomaly. Runs in Docker (ghcr.io/victoriametrics/mcp-vmanomaly:0.3.4). Needs 12 environment variables to run.