SmartBear/smartbear-mcp (SmartBear/smartbear-mcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it yet. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Caution
74/100

SmartBear/smartbear-mcp

MCP server for interacting SmartBear Products

→ SmartBear/smartbear-mcp· npm: @smartbear/mcp· listed on npm

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

SmartBear

Source: npm · also listed on Glama, 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

npmscored separatelyGlamanot scored hereGitHub

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: 1 critical, 2 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 4 credentials: API_HUB_API_KEY, ENVFALLBACK_AUTH_TOKEN, MCP_SERVER_BUGSNAG_API_KEY, SWAGGER_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 critical2 high1 medium1 low

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

criticalvitest@3.2.4GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

highjs-yaml@4.3.1GHSA-2883-xcg3-v3hh

js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources

highvite@7.3.2GHSA-fx2h-pf6j-xcff

vite: `server.fs.deny` bypass on Windows alternate paths

mediumvite@7.3.2GHSA-v6wh-96g9-6wx3

launch-editor: NTLMv2 hash disclosure via UNC path handling on Windows

lowvitest@3.2.4GHSA-82fw-gwwq-j7x9

Vitest: Path Traversal / Arbitrary File Read via @vitest/mocker Redirect Mock

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.
configALLOWED_ORIGINS
🔐 secretAPI_HUB_API_KEY
configBASE_URL
configCACHE_ENABLED
configCACHE_TTL
🔐 secretENVFALLBACK_AUTH_TOKEN
configMCP_ALLOWED_ENDPOINTS
configMCP_CLIENTS
🔐 secretMCP_SERVER_BUGSNAG_API_KEY
configMCP_SHUTDOWN_TIMEOUT_MS
configMCP_TOOLSETS
configMCP_TRANSPORT
configOAUTH_AUTHORIZATION_SERVER_URL
configQMETRY_BASE_URL
🔐 secretSWAGGER_API_KEY
configZEPHYR_CUSTOM_BASE_URL
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Production dependencies are patched

0 critical, 2 high severity in production deps — js-yaml@4.3.1 (high), vite@7.3.2 (high)

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

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

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 2 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/smartbear/smartbear-mcp?variant=verified)](https://m8ven.ai/mcp/smartbear/smartbear-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 657ed57924e970e2cd156fb954ce3a8ccab90c70
code hash: e971586e8392445d95abe4f158a3dbc5c1d8235d8ec5a8b8174e156557758f7e
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