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

Back to MCP Trust IndexM8ven
C
Emerging
74/100
1 month ago

Jenkins MCP Server

Enables Jenkins CI/CD integration with job management, pipeline monitoring, artifact handling, and batch operations via MCP.

→ avisangle/jenkins-mcp-server· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

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

avisangle

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 →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

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.
🔐
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_URL"http://your-jenkins-server:8080"
configMCP_HOST
configMCP_PORT
configJENKINS_USER"your-username"
🔐 secretJENKINS_API_TOKEN"your-api-token"
configJENKINS_MAX_RETRIES
configJENKINS_RETRY_BASE_DELAY
configJENKINS_RETRY_MAX_DELAY
configJENKINS_RETRY_BACKOFF_MULTIPLIER
configJENKINS_DEFAULT_TIMEOUT
configJENKINS_HEALTH_TIMEOUT
configJENKINS_CRUMB_CACHE_MINUTES
configJENKINS_CACHE_STATIC_TTL3600 # 1 hour for static data
configJENKINS_CACHE_SEMI_STATIC_TTL300 # 5 minutes for semi-static
configJENKINS_CACHE_DYNAMIC_TTL30 # 30 seconds for dynamic data
configJENKINS_CACHE_SHORT_TTL10 # 10 seconds for short-lived
configJENKINS_CACHE_STATIC_SIZE
configJENKINS_CACHE_SEMI_STATIC_SIZE
configJENKINS_CACHE_DYNAMIC_SIZE
configJENKINS_CACHE_PERMANENT_SIZE
configJENKINS_CACHE_SHORT_SIZE
configJENKINS_MAX_LOG_SIZE
configJENKINS_MAX_CONTENT_SIZE
configJENKINS_MAX_ARTIFACT_SIZE_MB
configJENKINS_DEFAULT_MAX_DEPTH
configJENKINS_DEFAULT_MAX_BUILDS
// 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

21/21 tools missing one or more hints — trigger_job (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_job_info (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_build_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +18 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 inputs are validated

18/21 tool handlers declare input schemas (86%)

Declare an inputSchema with zod/joi/yup on every tool definition.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tests exist

No test files found

Add tests that exercise each declared tool.

No arbitrary install scripts

Has postinstall/preinstall script — runs arbitrary code on npm install

Remove postinstall/preinstall hooks unless they’re essential.

Domain consistency

npm scope @ashwinighuge doesn't match GitHub owner avisangle

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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 7 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/avisangle/jenkins-mcp-server)](https://m8ven.ai/mcp/avisangle/jenkins-mcp-server)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: c83c9f77c5f8c30c08061beb67d5d9107f290c5b
code hash: 753b850b62aae5479f5683c18bf0c746fe837546aa34ba49bef448a935c43e49
verified: 8/6/2026, 2:57:49 PM
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