syncause-debug-mcp
Enables AI agents to query runtime debugging facts (stack traces, logs, function arguments) captured by Syncause, allowing them to fix root causes with evidence instead of guessing.
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
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
Syncause
Source: Glama
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.
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.
search_debug_tracesEntry point for troubleshooting. Search for relevant error logs, slow queries, or specific business ID execution traces based on user questions or error descriptions.
get_trace_insightGet a complete lifecycle report for a single request, including call tree skeleton, key SQL summaries, and exception logs.
inspect_method_snapshotDeep dive into a specific method for a given request, returning precise input/output parameters, local variables, and logs generated within its scope.
diff_trace_executionCompare the execution paths and data differences between two requests (usually one successful and one failed) to identify the root cause of bugs.
setup_projectInitialize or retrieve a specific project's configuration by its path. Use this when you have a local project path and need its 'projectId'. If you want to see already configured projects, use 'get_project_list' first.
get_project_listList all projects that have already been initialized. This is the preferred way to discover available 'projectId's and their corresponding paths without re-initializing them.
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse
axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`
axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge
Axios is Vulnerable to Denial of Service via __proto__ Key in mergeConfig
Axios: Header Injection via Prototype Pollution
API_KEY"env": { "": "YOUR_API_KEY" }DAEMON_PACKAGELOG_LEVELMODENPM_REGISTRYSERVICE_PROXY_URLSKIP_DAEMONSystemRootXDG_DATA_HOMETool 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
6/6 tools missing one or more hints — search_debug_traces (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_trace_insight (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); inspect_method_snapshot (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 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 2/6 tool handlers wrap calls in try/catch (33%)
Wrap each tool handler body in try/catch and return a structured error response.
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.25.2 (high), axios@1.13.2 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
Dependency freshness
1/7 production deps stale: node-machine-id@2023-05-09 (3.1y)
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.
[](https://m8ven.ai/mcp/syncause/mcp-server)?variant=verified from the URL.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