open-devops-agent (open-devops-agent/open-devops-agent) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Emerging
74/100
7 days ago

open-devops-agent

DevOps-AI-Agent to troubleshoot issues while you are away

→ open-devops-agent/open-devops-agent· listed on github_code

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

open-devops-agent

Source: github_code

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

GitHub

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// 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 18 credentials: GITLAB_TOKEN, JENKINS_API_TOKEN, BAMBOO_PASSWORD, EMAIL_SMTP_PASSWORD, GITHUB_TOKEN, JIRA_API_TOKEN, JIRA_PROJECT_KEY, SLACK_BOT_TOKEN, PAGERDUTY_TOKEN, ZOHO_ACCESS_TOKEN, ANTHROPIC_API_KEY, WEBHOOK_SECRET, SLACK_SIGNING_SECRET, ARGOCD_AUTH_TOKEN, STORAGE_ACCESS_KEY, MINIO_ACCESS_KEY, STORAGE_SECRET_KEY, MINIO_SECRET_KEY
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.
configORG_ID"": "acme-corp",
configQUEUE_POLL_INTERVAL_SEC
configAUTO_APPLY"": "false"
configSTORAGE_PROVIDER
configGITHUB_ORG
configFASTMCP_HOST
configFASTMCP_PORT
🔐 secretGITLAB_TOKEN
configGITLAB_URL
configJENKINS_URL
configJENKINS_USERNAME
🔐 secretJENKINS_API_TOKEN
configBAMBOO_URL
configBAMBOO_USERNAME
🔐 secretBAMBOO_PASSWORD
configAZURE_DEVOPS_ORG
configAZURE_DEVOPS_PAT
configAWS_REGION
configGCP_PROJECT_ID
configAZURE_SUBSCRIPTION_ID
configEMAIL_ENABLED
configEMAIL_SMTP_HOSTsmtp.gmail.com
configEMAIL_SMTP_PORT
configEMAIL_SMTP_USERdevops-agent@yourcompany.com
🔐 secretEMAIL_SMTP_PASSWORDyour-app-password
configEMAIL_FROMdevops-agent@yourcompany.com
configEMAIL_TOsre-team@yourcompany.com
configEMAIL_CC
🔐 secretGITHUB_TOKEN"": "ghp_...",
configALLOWED_NAMESPACES
configHELM_BIN
configTERRAFORM_BIN
configTERRAFORM_WORKSPACE_DIR
configJIRA_ENABLED
configJIRA_URL
configJIRA_EMAIL
🔐 secretJIRA_API_TOKEN
🔐 secretJIRA_PROJECT_KEY
configJIRA_ISSUE_TYPE
configJIRA_PRIORITY_CRITICAL
configJIRA_PRIORITY_HIGH
configJIRA_PRIORITY_MEDIUM
configJIRA_PRIORITY_LOW
configSLACK_WEBHOOK_URL"": "https://hooks.slack.com/services/...",
configSLACK_APPROVAL_CHANNELdevops-approvals
🔐 secretSLACK_BOT_TOKEN
configZOHO_ENABLED
configESCALATION_TIMEOUT_MINUTES
configPAGERDUTY_ENABLED
configPAGERDUTY_URL
🔐 secretPAGERDUTY_TOKEN
configPAGERDUTY_SERVICE_ID
configPAGERDUTY_FROM_EMAIL
configPAGERDUTY_URGENCY_CRITICAL
configPAGERDUTY_URGENCY_HIGH
configPAGERDUTY_URGENCY_MEDIUM
configPAGERDUTY_URGENCY_LOW
configAGENT_EMERGENCY_STOPfalse # Set true to disable agent
configREQUIRE_APPROVAL_FOR
configSSH_STRICT_HOST_KEY_CHECKING
configSSH_REMOTE_USER
configSSH_CONNECT_TIMEOUT
configSSH_KNOWN_HOSTS
configZOHO_DESK_ORG_ID
🔐 secretZOHO_ACCESS_TOKEN
configZOHO_DEPARTMENT_ID
configZOHO_DESK_URL
configZOHO_CONTACT_EMAIL
configMAX_AGENT_STEPS
configCLAUDE_API_RETRIES
configCLAUDE_RETRY_DELAY_SEC
configCLAUDE_MODEL
🔐 secretANTHROPIC_API_KEY"": "sk-ant-...",
🔐 secretWEBHOOK_SECRET
🔐 secretSLACK_SIGNING_SECRET
configARGOCD_INSECURE_SKIP_VERIFY
configARGOCD_SERVER_URL
🔐 secretARGOCD_AUTH_TOKEN
configENABLE_DATABASE_COLLECTION
configKUBECONFIG"": "/path/to/kubeconfig",
configENABLE_SECURITY_SCANNING
configENABLE_COMPLIANCE_CHECKS
configCOMPLIANCE_FRAMEWORKS
configHOST
configUVICORN_WORKERS
configESCALATION_ENABLED
configESCALATION_CHANNELS
configESCALATION_ON_DB_ISSUES
configESCALATION_ON_UNRESOLVED
configESCALATION_ON_AI_FAILURE
configORG_IDS
configAUDIT_RETENTION_DAYS
configAZURE_STORAGE_ACCOUNT
configSTORAGE_BUCKET
configSTORAGE_CONTAINER
configSTORAGE_ENDPOINT_URL
configMINIO_ENDPOINT
🔐 secretSTORAGE_ACCESS_KEY
🔐 secretMINIO_ACCESS_KEY
🔐 secretSTORAGE_SECRET_KEY
🔐 secretMINIO_SECRET_KEY
configAZURE_STORAGE_ACCOUNT_URL
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
deployAZURE_STORAGE_CONNECTION_STRING
// 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

8/8 tools missing one or more hints — configure_org_credentials (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_org_config_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); enqueue_incident (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +5 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 test coverage

3/8 tools referenced in tests (38%)

Write tests that reference each tool by name so every tool has at least one test.

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 3 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/open-devops-agent-open-devops-agent-1f6a21)](https://m8ven.ai/mcp/open-devops-agent-open-devops-agent-1f6a21)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 2e6bcf00d0b15e478fa9a8b90402452111852124
code hash: fb4ac51468cd380dc530124991c9ebd0f9a8c174a795a24cc814cb1635f2def7
verified: 8/19/2026, 9:20:16 AM
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