mcp-error-tracing (wycCome/mcp-error-tracing) is an MCP server listed on the M8ven Trust Index. It scores 56 out of 100, grade D. It declares 7 tools. No publisher has claimed this listing.

Caution

56/100

mcp-error-tracing

Item: mcp-error-tracing
Rating: 56
Author: M8ven

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

Caution. Specific findings reduced this grade. They are listed on the page. 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 push why connect →

Who stands behind it

wycCome

Source: Glama · also listed on ModelScope

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 ModelScopenot 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

⚠️

Known vulnerabilities in dependencies: 13 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.

// tools this server exposes7 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

find_code_owner

Find the code owner and commit ID for a specific file and line number using Bitbucket blame API

get_pull_request

Get pull request information by commit ID from Bitbucket

get_commits_by_path

Get commits for a specific directory path from Bitbucket. Filters commits by time (default: last 7 days). Useful for analyzing recent changes in a module or package.

get_method_code

create_jira_ticket

investigate_error

track_error_full

Complete workflow: find code owner, get PR info, and create JIRA ticket for an error

// known CVEs in dependencies13 high6 medium11 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.24.3GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

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

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

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

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

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

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

highaxios@1.13.2GHSA-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 →

// 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.

configBITBUCKET_BASE_URL

🔐 secretBITBUCKET_PASSWORD

configBITBUCKET_PROJECT

configBITBUCKET_REPO

configBITBUCKET_USERNAME

configCOMPATIBLE_PORT兼容模式默认端口：3001（通过 .env 中配置）

configDEFAULT_BRANCH确保文件路径相对于仓库根目录，检查 DEFAULT_BRANCH 配置

configHTTP_PORTHTTP 模式默认端口：3000（通过 .env 中配置）

configJIRA_BASE_URL

configJIRA_COMPONENT_ID

configJIRA_ISSUE_TYPE_ID

🔐 secretJIRA_PASSWORD

configJIRA_PRIORITY_ID

🔐 secretJIRA_PROJECT_KEY

configJIRA_USERNAME

configPR_TARGET_BRANCH

// 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

7/7 tools missing one or more hints — find_code_owner (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_pull_request (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_commits_by_path (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4 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.

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.

Production dependencies are patched

0 critical, 13 high severity in production deps — @modelcontextprotocol/sdk@1.24.3 (high), @modelcontextprotocol/sdk@1.24.3 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

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 5 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 Verified](https://m8ven.ai/badge/mcp/wyccome/mcp-error-tracing?variant=verified)](https://m8ven.ai/mcp/wyccome/mcp-error-tracing)

Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.

commit: c9d54178c9d1cac448a486af7f9d45511a050cb6

code hash: 4e64bd2887e4d81f23cc1f1a42eb1d1b18dd4c5ef3a0f8bbacef44029aad01d1

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