Jenkins MCP Server (Pawangunjkar/jenkins-mcp) is an MCP server listed on the M8ven Trust Index. It scores 71 out of 100, grade C. It declares 53 tools. No publisher has claimed this listing.

C
Limited view
71/100

Jenkins MCP Server

A comprehensive MCP server with 53 tools for managing Jenkins CI/CD operations, including job, build, pipeline, node, credential, and plugin management, enabling AI assistants to control Jenkins servers through natural language.

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

Pawangunjkar

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: JENKINS_API_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configJENKINS_MCP_CACHE_DIRNo ~/.jenkins-mcp-cache Credential cache directory
configJENKINS_URLYes — Jenkins server URL (e.g., http://localhost:8080)
🔐 secretJENKINS_API_TOKENyour-api-token-here
configJENKINS_SSL_VERIFYNo true Set to false for self-signed certificates
configJENKINS_USERNAMEYes admin Jenkins username
configJENKINS_TIMEOUTNo 30 Request timeout in seconds
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

53/53 tools missing one or more hints — jenkins_connect (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); jenkins_disconnect (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); jenkins_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +50 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool handlers catch errors

Only 1/53 tool handlers wrap calls in try/catch (2%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/pawangunjkar/jenkins-mcp)](https://m8ven.ai/mcp/pawangunjkar/jenkins-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 1a83ad64c55f17436ca074da618e85479efaca5b
code hash: 32012484dce41dc63feb0b5d614812ace09559db2d9594e04d274fabc679fd52
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client