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/Pawangunjkar/jenkins-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/pawangunjkar/jenkins-mcp/jenkins-mcp)<a href="https://agentmods.dev/mcp/pawangunjkar/jenkins-mcp/jenkins-mcp"><img src="https://agentmods.dev/badge/mcp/pawangunjkar/jenkins-mcp/jenkins-mcp/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/pawangunjkar/jenkins-mcp/jenkins-mcp"><img src="https://agentmods.dev/badge/mcp/pawangunjkar/jenkins-mcp/jenkins-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
jenkins-mcp 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 2d 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.
This is a copy
100% identical to jenkins-mcp — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{ "jenkins-mcp": { "command": "uvx", "args": [ "jenkins-mcp" ] } }
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.
- 2d ago First seen · 8 lines scan A 500be955ab9e
jenkins-mcp is an MCP server published in the GitHub repository Pawangunjkar/jenkins-mcp (0 stars, last pushed 3d 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 is 100% identical to jenkins-mcp, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
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.
github-actions
GitHub Actions MCP — view runs, read logs, re-run jobs, and manage CI/CD. Runs locally from the mcp-server-github-actions npm package.
release-readiness-triage-mcp
Aggregates CI failures, cross-references flakiness history, and outputs GO/NOGO release verdicts. Runs locally from the release-readiness-triage-mcp npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.
codex_message_board
MCP server "codexmessageboard", hosted remotely at 127.0.0.1, as configured in openai/codex.