Back to MCP Trust Indexm8ven
54
/ 100
1 month ago
glama

Error Tracker MCP Server

Automates error tracking workflow by finding code owners in Bitbucket, retrieving related pull requests, and creating assigned JIRA tickets for code errors.

→ wycCome/mcp-error-tracing· listed on 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.

Install from

Glama

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

// key findings
⚠️
Known vulnerabilities in dependencies: 16 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 3 credentials: BITBUCKET_PASSWORD, JIRA_PASSWORD, JIRA_PROJECT_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies16 high14 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.0.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.0.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highaxios@1.6.0GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

highaxios@1.6.0GHSA-3g43-6gmg-66jw

axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge

highaxios@1.6.0GHSA-43fc-jf86-j433

Axios is Vulnerable to Denial of Service via __proto__ Key in mergeConfig

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// required environment variables
This server reads these from process.env. You'll be asked to provide them before it can run.
configBITBUCKET_BASE_URL
🔐 secretBITBUCKET_PASSWORD— your_password
configBITBUCKET_PROJECT— your_project
configBITBUCKET_REPO
configBITBUCKET_USERNAME— your_username
configCOMPATIBLE_PORT— 3001 # 兼容模式端口（默认 3001）
configDEFAULT_BRANCH— main # 默认调查分支（默认 main）
configHTTP_PORT— 3000 # HTTP 模式端口（默认 3000）
configJIRA_BASE_URL
configJIRA_COMPONENT_ID
configJIRA_ISSUE_TYPE_ID
🔐 secretJIRA_PASSWORD— your_password
configJIRA_PRIORITY_ID
🔐 secretJIRA_PROJECT_KEY— YOUR_PROJECT
configJIRA_USERNAME— your_username
configPR_TARGET_BRANCH— main # PR 目标分支过滤（默认 main）
// full audit trail
The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.
// improvement guidance — verified publishers only
We have 6 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/wyccome-mcp-error-tracing-em56b5)](https://m8ven.ai/mcp/wyccome-mcp-error-tracing-em56b5)
commit: c9d54178c9d1cac448a486af7f9d45511a050cb6
code hash: 4e64bd2887e4d81f23cc1f1a42eb1d1b18dd4c5ef3a0f8bbacef44029aad01d1
verified: 6/26/2026, 9:45:47 AM
view raw JSON →