Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SmartBear MCP

NPM · @SMARTBEAR/MCP · 3 COMPONENTS

MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.

+5 this week 62 Trust /100

Last scanned (12 hours ago)

Scores higher than 31% of npm servers

Category Testing and QA

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security94
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known medium-severity CVE affects minimatch 10.2.6, reached via swagger-client > @swagger-api/apidom-reference > minimatch. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 46 of 255 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to SmartBear/smartbear-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: the captured schema was too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge it on a partial copy.Unverified
Stability & Change Management73
  • Stability check failed: the tool surface changed between 0.42.0 and 0.43.0: 0 tool removals, 1 breaking changes, 7 additions. See how to fix → Fail
Tool Coverage0
  • Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge them on a partial copy.Unverified
Tool Safety0
  • Tool safety not yet verified: the captured tool definitions were too large for us to store in full (the trim removes the very descriptions this category reads), or the server stopped listing its tools part-way.Unverified
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 3 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

What we tested

Checks we ran (11)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Stability
  • MCP protocol

Checks we could not complete (3)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: the captured schema was too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge it on a partial copy.
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge them on a partial copy.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: the captured tool definitions were too large for us to store in full (the trim removes the very descriptions this category reads), or the server stopped listing its tools part-way.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 −4

    No change was recorded against any check on this day. Stability & Change Management went from 100 to 73.

  • 4 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Nov 26 −5
    • Malware scan: pass → unverified ▼ security
    • Stability: pass → fail ▼ security
    • Provenance: fail → pass ▲ security
    • The attested source repository moved: SmartBear/smartbear-mcp security
    • Package version: 0.42.0 → 0.43.0 functional
  • 31 Oct 26 −1
    • CVE-2026-118764 affects this package: medium ▼ security
    • Known CVEs: partial → fail ▼ security
    • CVE-2026-93753 no longer affects this package ▲ security
    • Stability: fail → pass ▲ security
  • 28 Oct 26 0
    • CVE-2026-93753 affects this package ▼ security
    • Known CVEs: pass → partial ▼ security
  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90.

  • 19 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@smartbear/mcp@0.43.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo SmartBear/smartbear-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/SmartBear/smartbear-mcp/.github/workflows/publish.yaml@refs/tags/v0.43.0
Rekor log index 3663878856
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:199e2fe41be4e3de4eed3081bbca19b961986285aeb065a76677ca352a717af97dd27d0007b7df561a4b7200417ede07b83741c8cda1a371dd43519c1

Background: How many MCP packages publish verified provenance →

Vulnerabilities 2 findings
ID CVE Severity Vector Fix available
GHSA-gcqx-w48m-w2h4 CVE-2026-93753 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N no
GHSA-g3hv-75wg-m249 CVE-2026-118764 medium yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 255 packages
Packages resolved 255
Deprecated 1
Stale 45
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 316 exposed · ~184,008 tokens partial

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
qmetry_bulk_update_test_case_execution_status ~5,047

No description provided.

NameTypeReqDescription
commentsstring––
dropIDnumber|string––
entityIDsstringyes–
entityTypestring––
isAutoExecutedstring––
isBulkOperationboolean––
passwordstring––
projectKeystring––
qmRunObjstring––
qmTsRunIdstringyes–
runStatusIDnumberyes–
typestring––
udfValuesByRunobject––
usernamestring––
viewIdnumber––

No output schema declared.

No examples provided.

qmetry_bulk_update_test_run_udfs ~2,534

No description provided.

NameTypeReqDescription
UDFobjectyes–
projectKeystring––
tcRunIDsarrayyes–

No output schema declared.

No examples provided.

qmetry_create_cycle ~1,411

No description provided.

NameTypeReqDescription
cycleobjectyes–
projectKeystring––

No output schema declared.

No examples provided.

qmetry_create_defect_or_issue ~4,561

No description provided.

NameTypeReqDescription
affectedCyclesarray––
affectedReleasearray––
componentarray––
descriptionstring––
environmentstring––
issueOwnernumber––
issuePrioritynumberyes–
issueStatenumber––
issueTypenumberyes–
projectKeystring––
summarystringyes–
sync_withstring––
tcRunIDnumber––
udfFieldsobject––

No output schema declared.

No examples provided.

qmetry_create_release ~939

No description provided.

NameTypeReqDescription
cycleobject––
projectKeystring––
releaseobjectyes–

No output schema declared.

No examples provided.

qmetry_create_requirement ~1,613

No description provided.

NameTypeReqDescription
associateRelCycboolean––
componentarray––
descriptionstring––
namestringyes–
prioritynumber––
releaseCycleMappingarray––
requirementOwnernumber––
requirementStatenumber––
rqFolderIdstring––
scopestring––
udfFieldsobject––

No output schema declared.

No examples provided.

qmetry_create_test_case ~4,681

No description provided.

NameTypeReqDescription
associateRelCycboolean––
componentarray––
descriptionstring––
estimatedTimenumber––
namestringyes–
prioritynumber––
releaseCycleMappingarray––
skipStepsboolean––
stepsarray––
tcFolderIDstring––
testCaseStatenumber––
testCaseTypenumber––
testcaseOwnernumber––
testingTypenumber––
udfFieldsobject––

No output schema declared.

No examples provided.

qmetry_create_test_suite ~4,067

No description provided.

NameTypeReqDescription
associateRelCycboolean––
descriptionstring––
isAutomatedFlagboolean––
namestringyes–
parentFolderIdstring––
releaseCycleMappingarray––
testSuiteStatenumber––
testsuiteOwnernumber––
udfFieldsobject––

No output schema declared.

No examples provided.

qmetry_execute_quality_gate_report ~1,008

No description provided.

NameTypeReqDescription
cycleIdsarray––
extKeysarray––
gateIdentifierstringyes–
limitnumber––
pagenumber––
projectIdnumberyes–
projectKeystring––
releaseIdnumber––
reportNamestringyes–

No output schema declared.

No examples provided.

qmetry_export_html_report ~343

No description provided.

NameTypeReqDescription
fileNamestringyes–
htmlContentstringyes–
projectKeystring––

No output schema declared.

No examples provided.

qmetry_fetch_api_call_quota ~384

No description provided.

NameTypeReqDescription
projectKeystring––

No output schema declared.

No examples provided.

qmetry_fetch_automation_status ~279

No description provided.

NameTypeReqDescription
projectKeystring––
requestIDnumberyes–

No output schema declared.

No examples provided.

qmetry_fetch_builds ~625

No description provided.

NameTypeReqDescription
filterstring––
limitnumber––
pagenumber––
projectKeystring––
startnumber––

No output schema declared.

No examples provided.

qmetry_fetch_cascade_child_values ~983

No description provided.

NameTypeReqDescription
idintegeryes–
isArchReqboolean––
projectKeystring––

No output schema declared.

No examples provided.

qmetry_fetch_defects_or_issues ~1,567

No description provided.

NameTypeReqDescription
filterstring––
isJiraIntegratedboolean––
limitnumber––
pagenumber––
projectKeystring––
sortstring––
startnumber––
viewIdnumber––

No output schema declared.

No examples provided.

qmetry_fetch_executions_by_test_suite ~2,003

No description provided.

NameTypeReqDescription
filterstring––
gridNamestring––
limitnumber––
pagenumber––
projectKeystring––
startnumber––
tsFolderIDnumber––
tsIDnumberyes–
viewIdnumber––

No output schema declared.

No examples provided.

qmetry_fetch_issue_details ~560

No description provided.

NameTypeReqDescription
defectIdintegeryes–
projectKeystring––

No output schema declared.

No examples provided.

qmetry_fetch_issue_executions ~3,539

No description provided.

NameTypeReqDescription
filterstring––
limitnumber––
linkedAssetIdnumberyes–
pagenumber––
platformIDstring––
projectKeystring––
startnumber––

No output schema declared.

No examples provided.

qmetry_fetch_issues_linked_to_test_case ~1,545

No description provided.

NameTypeReqDescription
filterstring––
getLinkedboolean––
limitnumber––
pagenumber––
projectKeystring––
startnumber––
tcIDnumberyes–

No output schema declared.

No examples provided.

qmetry_fetch_linked_issues_of_test_case_run ~2,200

No description provided.

NameTypeReqDescription
entityIdnumberyes–
filterstring––
getColumnsboolean––
getLinkedboolean––
istcrFlagboolean––
limitnumber––
pagenumber––
projectKeystring––
startnumber––

No output schema declared.

No examples provided.

qmetry_fetch_platforms ~874

No description provided.

NameTypeReqDescription
filterstring––
limitnumber––
pagenumber––
projectKeystring––
sortstring––
startnumber––

No output schema declared.

No examples provided.

qmetry_fetch_qmetry_list_projects ~731

No description provided.

NameTypeReqDescription
filterstring––
limitnumber––
pagenumber––
paramsobjectyes–
projectKeystring––
startnumber––

No output schema declared.

No examples provided.

qmetry_fetch_qmetry_project_info ~591

No description provided.

NameTypeReqDescription
projectKeystring––

No output schema declared.

No examples provided.

qmetry_fetch_quality_gate_configuration ~374

No description provided.

NameTypeReqDescription
agentIdentifierstringyes–
projectIdnumberyes–
projectKeystring––

No output schema declared.

No examples provided.

qmetry_fetch_releases_and_cycles ~595

No description provided.

NameTypeReqDescription
projectKeystring––
showArchiveboolean––

No output schema declared.

No examples provided.

qmetry_fetch_requirement_details ~488

No description provided.

NameTypeReqDescription
idnumberyes–
projectKeystring––
versionnumberyes–

No output schema declared.

No examples provided.

qmetry_fetch_requirements ~2,542

No description provided.

NameTypeReqDescription
filterstring––
filterTypestring––
folderPathstring––
folderSortColumnstring––
folderSortOrderstring––
getSubEntitiesboolean––
hideEmptyFoldersboolean––
isJiraFilterboolean––
limitnumber––
pagenumber––
projectKeystring––
scopestring––
sortstring––
startnumber––
udfFilterstring––
viewIdnumber––

No output schema declared.

No examples provided.

qmetry_fetch_requirements_linked_to_test_case ~1,682

No description provided.

NameTypeReqDescription
filterstring––
getLinkedboolean––
limitnumber––
pagenumber––
projectKeystring––
rqFolderPathstring––
startnumber––
tcIDnumberyes–

No output schema declared.

No examples provided.

qmetry_fetch_test_case_details ~741

No description provided.

NameTypeReqDescription
limitnumber––
pagenumber––
projectKeystring––
startnumber––
tcIDnumberyes–

No output schema declared.

No examples provided.

qmetry_fetch_test_case_executions ~4,025

No description provided.

NameTypeReqDescription
filterstring––
limitnumber––
pagenumber––
projectKeystring––
scopestring––
startnumber––
tcidnumberyes–
tcversionnumber––

No output schema declared.

No examples provided.

qmetry_fetch_test_case_runs_by_test_suite_run ~4,978

No description provided.

NameTypeReqDescription
filterstring––
limitnumber––
pagenumber––
projectKeystring––
showTcWithDefectsboolean––
startnumber––
tcrUdfFilterstring––
tsrunIDstringyes–
udfFilterstring––
viewIdnumber––

No output schema declared.

No examples provided.

qmetry_fetch_test_case_steps ~530

No description provided.

NameTypeReqDescription
idnumberyes–
limitnumber––
pagenumber––
projectKeystring––
startnumber––
versionnumber––

No output schema declared.

No examples provided.

qmetry_fetch_test_case_steps_with_udf ~844

No description provided.

NameTypeReqDescription
limitnumber––
pagenumber––
projectKeystring––
startnumber––
tcIDnumberyes–
versionnumber––
viewIdnumber––

No output schema declared.

No examples provided.

qmetry_fetch_test_case_version_details ~506

No description provided.

NameTypeReqDescription
idnumberyes–
projectKeystring––
scopestring––
versionnumberyes–

No output schema declared.

No examples provided.

qmetry_fetch_test_cases ~2,086

No description provided.

NameTypeReqDescription
filterstring––
folderIDnumber––
folderPathstring––
folderSortColumnstring––
folderSortOrderstring––
getSubEntitiesboolean––
hideEmptyFoldersboolean––
limitnumber––
pagenumber––
projectKeystring––
restoreDefaultColumnsboolean––
scopestring––
showRootOnlyboolean––
startnumber––
udfFilterstring––
viewIdnumber––

No output schema declared.

No examples provided.

qmetry_fetch_test_cases_linked_to_requirement ~2,487

No description provided.

NameTypeReqDescription
cycleIDstring––
filterstring––
getColumnsboolean––
getLinkedboolean––
getSubEntitiesboolean––
limitnumber––
pagenumber––
projectKeystring––
releaseIDstring––
rqIDnumberyes–
showEntityWithReleaseCycleboolean––
startnumber––
tcFolderPathstring––

No output schema declared.

No examples provided.

qmetry_fetch_test_cases_linked_to_test_suite ~1,467

No description provided.

NameTypeReqDescription
filterstring––
getLinkedboolean––
limitnumber––
pagenumber––
projectKeystring––
startnumber––
tsIDnumberyes–

No output schema declared.

No examples provided.

qmetry_fetch_test_run_udf_metadata ~608

No description provided.

NameTypeReqDescription
projectKeystring––

No output schema declared.

No examples provided.

qmetry_fetch_test_run_udf_values ~1,931

No description provided.

NameTypeReqDescription
projectKeystring––
sizeinteger––
sourceContextstring––
sourceRowsarray––
startIndexinteger––
tsrunIDstring––
viewIdinteger––

No output schema declared.

No examples provided.

qmetry_fetch_test_suite_details ~322

No description provided.

NameTypeReqDescription
idintegeryes–
projectKeystring––
scopestring––

No output schema declared.

No examples provided.

qmetry_fetch_test_suites ~1,723

No description provided.

NameTypeReqDescription
filterstring––
folderPathstring––
getSubEntitiesboolean––
limitnumber––
pagenumber––
projectKeystring––
scopestring––
sortstring––
startnumber––
udfFilterstring––
viewIdnumber––

No output schema declared.

No examples provided.

qmetry_fetch_test_suites_for_test_case ~1,657

No description provided.

NameTypeReqDescription
filterstring––
getColumnsboolean––
limitnumber––
pagenumber––
projectKeystring––
startnumber––
tsFolderIDnumber––
viewIdnumber––

No output schema declared.

No examples provided.

qmetry_fetch_udf_layout ~2,364

No description provided.

NameTypeReqDescription
entityTypestringyes–
pageNamestring––
projectKeystring––

No output schema declared.

No examples provided.

qmetry_import_automation_test_results ~4,209

No description provided.

NameTypeReqDescription
automationHierarchystring––
buildIDstring––
cycleIDstring––
entityTypestringyes–
filestringyes–
fileNamestringyes–
is_matching_requiredstring––
platformIDstring––
projectIDstring––
releaseIDstring––
skipWarningstring––
tcFolderPathstring––
testcase_fieldsstring––
testsuiteIdstring––
testsuiteNamestring––
testsuite_fieldsstring––
tsFolderPathstring––

No output schema declared.

No examples provided.

qmetry_link_issues_to_testcase_run ~553

No description provided.

NameTypeReqDescription
issueIdsarrayyes–
projectKeystring––
tcrIdnumberyes–

No output schema declared.

No examples provided.

qmetry_link_platforms_to_test_suite ~889

No description provided.

NameTypeReqDescription
projectKeystring––
qmPlatformIdstringyes–
qmTsIdnumberyes–

No output schema declared.

No examples provided.

qmetry_link_requirements_to_testcase ~512

No description provided.

NameTypeReqDescription
rqVersionIdsstringyes–
tcIDstringyes–
tcVersionIdnumberyes–

No output schema declared.

No examples provided.

qmetry_link_test_case_to_issues ~522

No description provided.

NameTypeReqDescription
dfIDsarrayyes–
tcIDstringyes–

No output schema declared.

No examples provided.

qmetry_link_test_cases_to_test_suite ~736

No description provided.

NameTypeReqDescription
fromReqsboolean––
tcvdIDsarrayyes–
tsIDnumberyes–

No output schema declared.

No examples provided.

qmetry_requirements_linked_test_cases_to_test_suite ~773

No description provided.

NameTypeReqDescription
fromReqsboolean––
tcvdIDsarrayyes–
tsIDnumberyes–

No output schema declared.

No examples provided.

Install

How do I install the SmartBear MCP server?

SmartBear MCP runs locally as an npm package, launched with npx -y @smartbear/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @smartbear/mcp

# add to Claude Code
claude mcp add com-smartbear-smartbear-mcp -- npx -y @smartbear/mcp
Common questions

What is the SmartBear MCP server?

SmartBear MCP is listed in the public MCP registry as com.smartbear/smartbear-mcp. MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J. This page covers its npm package (@smartbear/mcp).

Is the SmartBear MCP server safe to use?

SmartBear MCP scores 62 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the SmartBear MCP server still maintained?

SmartBear MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the SmartBear MCP server under?

SmartBear MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the SmartBear MCP server?

VerifyMCP ran 11 checks on SmartBear MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 7 more. 3 items could not be completed, a gap on our side rather than a finding about SmartBear MCP: Schema quality, Tool coverage and Tool safety. 3 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.