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/ZhenGtai123/groundtruth-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/zhengtai123/groundtruth-mcp/checkout-flow-checkout-flow)<a href="https://agentmods.dev/mcp/zhengtai123/groundtruth-mcp/checkout-flow-checkout-flow"><img src="https://agentmods.dev/badge/mcp/zhengtai123/groundtruth-mcp/checkout-flow-checkout-flow/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/zhengtai123/groundtruth-mcp/checkout-flow-checkout-flow"><img src="https://agentmods.dev/badge/mcp/zhengtai123/groundtruth-mcp/checkout-flow-checkout-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
checkout-flow 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 11d 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
{
"checkout-flow": {
"command": "python",
"args": [
"-m",
"groundtruth_mcp.cli",
"--config",
"examples/checkout-flow/groundtruth.toml",
"serve"
],
"env": {}
}
}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.
- 11d ago First seen · 13 lines scan A 705bf247edf0
checkout-flow is an MCP server published in the GitHub repository ZhenGtai123/groundtruth-mcp (1 stars, last pushed 25d 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
proofspec
A thin layer that makes your test suite the living spec. Runs locally from the proofspec npm package. Needs 1 environment variable to run.
mcp-server
Flaky test detection, root cause analysis, and fix suggestions for development teams. Remote server at mcp.trunk.io.
behavior-mcp
MCP server "behavior-mcp" as configured in putervision/state-memory-mcp. Launched with behavior-mcp run. Needs 1 environment variable to run.
servicenow
MCP server "servicenow" as configured in serac-labs/serac. Runs locally from the servicenow-mcp-stdio npm package.
state-memory-mcp
MCP server "state-memory-mcp" as configured in putervision/state-memory-mcp. Launched with state-memory-mcp run.
teamcity
MCP server exposing JetBrains TeamCity CI/CD workflows to AI coding assistants. Runs locally from the @daghis/teamcity-mcp npm package. Needs 3 environment variables to run.