Bugsnag MCP Server (tgeselle/bugsnag-mcp) is an MCP server listed on the M8ven Trust Index. It scores 56 out of 100, grade D. It declares 22 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
56/100

Bugsnag MCP Server

A Model Context Protocol (MCP) server for interacting with Bugsnag. This server allows LLM tools like Cursor and Claude to investigate and resolve issues in Bugsnag.

→ tgeselle/bugsnag-mcp· listed on mcp_so

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

⚡ 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

tgeselle

Source: mcp.so · also 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. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

mcp.sonot scored hereGlamanot 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.

⏳ This MCP is queued for scoring. Check back in a few minutes.
// 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 1 credential: BUGSNAG_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes11 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.

list_organizations

List available Bugsnag organizations

list_projects

List projects in an organization

list_errors

List errors in a project with filtering options

view_error

Get detailed information about a specific error

list_error_events

List events (occurrences) for a specific error

view_latest_event

View the latest event for an error

view_event

View detailed information about a specific event

view_stacktrace

Extract and format stacktrace information from an event

view_exception_chain

View the full chain of exceptions for an event

search_issues

Search for issues using various criteria

view_tabs

View all event data tabs including app, device, user, request, breadcrumbs, metadata, and stacktrace

// known CVEs in dependencies13 high5 medium12 low

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

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

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

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

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

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

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

highaxios@1.8.4GHSA-43fc-jf86-j433

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

highaxios@1.8.4GHSA-4hjh-wcwx-xvwj

Axios is vulnerable to DoS attack through lack of data size check

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.
🔐 secretBUGSNAG_API_KEY"": "your-bugsnag-api-key"
// 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

22/22 tools missing one or more hints — list_organizations (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_projects (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_errors (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +19 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.).

Tool test coverage

Only 2/22 tools referenced in tests (9%)

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

Production dependencies are patched

0 critical, 13 high severity in production deps — @modelcontextprotocol/sdk@0.6.0 (high), axios@1.8.4 (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/tgeselle/bugsnag-mcp?variant=verified)](https://m8ven.ai/mcp/tgeselle/bugsnag-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 149208b6c3c2ece65bee22fa3406e0d726e1e015
code hash: c5abed641c953b4851450613b6b8d2ff8d9142f0b6b84f0e51fa98445de5d601
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