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/Daghis/teamcity-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/daghis/teamcity-mcp/teamcity)<a href="https://agentmods.dev/mcp/daghis/teamcity-mcp/teamcity"><img src="https://agentmods.dev/badge/mcp/daghis/teamcity-mcp/teamcity/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/daghis/teamcity-mcp/teamcity"><img src="https://agentmods.dev/badge/mcp/daghis/teamcity-mcp/teamcity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
teamcity 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 10d 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
{
"teamcity": {
"command": "npx",
"args": [
"-y",
"@daghis/teamcity-mcp",
"-y"
],
"env": {
"TEAMCITY_URL": "",
"TEAMCITY_TOKEN": "",
"MCP_MODE": "dev"
}
}
}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.
- 10d ago First seen · 15 lines scan A 1818e5b35e9e
teamcity is an MCP server published in the GitHub repository Daghis/teamcity-mcp (28 stars, last pushed 9d 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
woodpecker-ci-mcp
Read Woodpecker CI repositories, pipelines and logs, and drive builds, secrets and crons. Runs locally from the @ni-c/woodpecker-ci-mcp npm package. Needs 6 environment variables to run.
woodpecker-mcp
MCP server "woodpecker-mcp" as configured in RikiGomes/woodpecker-mcp. Runs locally from the woodpecker-mcp npm package.
mcp-zuul
MCP server for Zuul CI — build failure analysis, log search, pipeline status, and job configuration. Runs locally from the mcp-zuul Python package. Needs 7 environment variables to run.
nowaikit
ServiceNow MCP server: 450+ tools for Claude, ChatGPT, Copilot & any AI. Read-only by default. Runs locally from the nowaikit npm package. Needs 14 environment variables to run.
servicenow-mcp
400+ ServiceNow tools across all modules — ITSM, CMDB, HRSD, CSM, SecOps, and more. Runs locally from the @aartiq/servicenow-mcp npm package. Needs 10 environment variables to run.
n8n-workflow-builder
A Python library for building, managing, and deploying n8n workflows with configuration-driven templates. Runs locally from the n8n-workflow-builder Python package.