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/rrmistry/tilt-mcp/tiltgit clone --depth 1 https://github.com/rrmistry/tilt-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/rrmistry/tilt-mcp/tilt)<a href="https://agentmods.dev/mcp/rrmistry/tilt-mcp/tilt"><img src="https://agentmods.dev/badge/mcp/rrmistry/tilt-mcp/tilt.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
tilt 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 6d 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
{
"tilt": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-v",
"${HOME}/.tilt-dev:/home/mcp-user/.tilt-dev",
"-v",
"${HOME}/.tilt-mcp:/home/mcp-user/.tilt-mcp",
"--network=host",
"ghcr.io/rrmistry/tilt-mcp:latest"
],
"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.
- 6d ago First seen · 18 lines scan A fe8ed8469a3a
tilt is an MCP server published in the GitHub repository rrmistry/tilt-mcp (6 stars, last pushed 6mo 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. It comes from a forked repository.
Other mcp servers, from other repositories
helm-mcp
Give your AI assistant access to real Helm chart data. No more hallucinated values.yaml files. Remote server at helm-mcp.kubedoll.com.
mcp-proxmox
MCP server for managing Proxmox VE clusters through AI assistants. Runs locally from the mcp-proxmox Python package.
mcp-kubernetes
Kubernetes monitoring & ops for AI agents — safe-by-default access modes and guards. Runs locally from the @dockndevai/mcp-kubernetes npm package. Needs 2 environment variables to run.
mcp-percona-pg
Manage Percona PostgreSQL + PgBouncer on Kubernetes — safe-by-default access modes and guards. Runs locally from the @dockndevai/mcp-percona-pg npm package. Needs 3 environment variables to run.
k8s-mcp
A Model Context Protocol (MCP) server for Kubernetes with 270+ tools, 8 resources, and 8 prompts. Runs locally from the k8s-mcp Python package.
kubernetes
MCP server for interacting with Kubernetes clusters via kubectl. Runs locally from the mcp-server-kubernetes npm package.