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/Smana/cloud-native-refWrote 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/smana/cloud-native-ref/turbot-steampipe)<a href="https://agentmods.dev/mcp/smana/cloud-native-ref/turbot-steampipe"><img src="https://agentmods.dev/badge/mcp/smana/cloud-native-ref/turbot-steampipe/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/smana/cloud-native-ref/turbot-steampipe"><img src="https://agentmods.dev/badge/mcp/smana/cloud-native-ref/turbot-steampipe.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
turbot-steampipe 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 1mo 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
{
"turbot-steampipe": {
"command": "npx",
"args": [
"-y",
"@turbot/steampipe-mcp"
],
"env": {
"STEAMPIPE_MCP_WORKSPACE_DATABASE": "${STEAMPIPE_DATABASE_URL}"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 6. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 1mo ago First seen · 12 lines scan A b625a3d003a5
turbot-steampipe is an MCP server published in the GitHub repository Smana/cloud-native-ref (103 stars, last pushed today), licensed Apache-2.0. 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
mcp-server
Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection. Remote server at app.netdata.cloud.
cloud-sql-mysql
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package.
ceph-aiops
Governed AI-ops for Ceph (ceph-mgr Dashboard REST): HEALTHWARN root-cause analysis, OSD/PG/pool/RBD/CephFS/RGW operations, and destructive-op guardrails with a built-in governance harness (audit, budget, undo, risk tiers). Runs locally from the ceph-aiops Python package.
janus-mcp
Secure Kubernetes MCP server: redacted diagnostics and human-approved writes, credentials never leave the process. Runs locally from the janus-mcp-server Python package.
litescope
SQLite & Cloudflare D1 operations: MCP server, schema diff, migrations, lint, backups, autopilot. Run with npx litescope. Runs locally from the litescope npm package.
cloud-sql-postgres
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package.