SmartBear MCP
NPM · @SMARTBEAR/MCP · 3 COMPONENTS
MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.
Last scanned (15 hours ago)
Scores higher than 31% of npm servers
Category Testing and QA
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 →
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 →
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.
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 →
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 →
zephyr_get_test_case_links ~169
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| testCaseKey | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| issues | array | – | – |
| self | string | – | – |
| webLinks | array | – | – |
No examples provided.
zephyr_get_test_case_steps ~543
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | integer | – | – |
| startAt | integer | – | – |
| testCaseKey | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| isLast | boolean | – | – |
| maxResults | integer | yes | – |
| next | – | – | – |
| startAt | integer | yes | – |
| total | integer | – | – |
| values | array | – | – |
No examples provided.
zephyr_get_test_cases ~588
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| folderId | integer | – | – |
| limit | integer | – | – |
| projectKey | string | – | – |
| startAtId | integer | – | – |
| updatedAfter | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | yes | – |
| next | – | – | – |
| nextStartAtId | – | yes | – |
| values | array | – | – |
No examples provided.
zephyr_get_test_cycle ~163
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| testCycleIdOrKey | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| customFields | object | – | – |
| description | string|null | – | – |
| folder | – | – | – |
| id | integer | yes | – |
| jiraProjectVersion | – | – | – |
| key | string | yes | – |
| links | object | – | – |
| name | string | yes | – |
| owner | – | – | – |
| plannedEndDate | – | – | – |
| plannedStartDate | – | – | – |
| project | object | yes | – |
| status | object | yes | – |
No examples provided.
zephyr_get_test_cycle_links ~199
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| testCycleIdOrKey | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| issues | array | – | – |
| self | string | – | – |
| testPlans | array | – | – |
| webLinks | array | – | – |
No examples provided.
zephyr_get_test_cycles ~666
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| folderId | integer | – | – |
| jiraProjectVersionId | integer | – | – |
| maxResults | integer | – | – |
| projectKey | string | – | – |
| startAt | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| isLast | boolean | – | – |
| maxResults | integer | yes | – |
| next | – | – | – |
| startAt | integer | yes | – |
| total | integer | – | – |
| values | array | – | – |
No examples provided.
zephyr_get_test_cycles_linked_to_a_jira_issue ~129
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| issueKey | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| testCycles | array | yes | – |
No examples provided.
zephyr_get_test_execution ~203
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| testExecutionIdOrKey | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| actualEndDate | string | – | – |
| assignedToId | – | – | – |
| automated | boolean | – | – |
| comment | string|null | – | – |
| customFields | object | – | – |
| environment | – | – | – |
| estimatedTime | – | – | – |
| executedById | – | – | – |
| executionTime | – | – | – |
| id | integer | yes | – |
| jiraProjectVersion | – | – | – |
| key | string | – | – |
| links | object | – | – |
| project | object | yes | – |
| testCase | object | yes | – |
| testCycle | – | – | – |
| testExecutionStatus | object | yes | – |
No examples provided.
zephyr_get_test_execution_links ~207
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| testExecutionIdOrKey | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| issues | array | – | – |
| self | string | – | – |
No examples provided.
zephyr_get_test_execution_steps ~740
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | integer | – | – |
| startAt | integer | – | – |
| testDataRowNumber | integer | – | – |
| testExecutionIdOrKey | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| isLast | boolean | – | – |
| maxResults | integer | yes | – |
| next | – | – | – |
| startAt | integer | yes | – |
| total | integer | – | – |
| values | array | – | – |
No examples provided.
zephyr_get_test_executions ~887
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| actualEndDateAfter | string | – | – |
| actualEndDateBefore | string | – | – |
| includeStepLinks | boolean | – | – |
| jiraProjectVersionId | integer | – | – |
| limit | integer | – | – |
| onlyLastExecutions | boolean | – | – |
| projectKey | string | – | – |
| startAtId | integer | – | – |
| testCase | string | – | – |
| testCycle | string | – | – |
| updatedAfter | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | yes | – |
| next | – | – | – |
| nextStartAtId | – | yes | – |
| values | array | – | – |
No examples provided.
zephyr_get_test_executions_linked_to_a_jira_issue ~133
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| issueKey | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| testExecutions | array | yes | – |
No examples provided.
zephyr_get_test_plans ~583
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| projectKey | string | – | – |
| startAtId | integer | – | – |
| updatedAfter | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | yes | – |
| next | – | – | – |
| nextStartAtId | – | yes | – |
| values | array | – | – |
No examples provided.
zephyr_get_test_script ~292
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| testCaseKey | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | – | – |
| text | string | yes | – |
| type | string | yes | – |
No examples provided.
zephyr_update_test_case ~1,180
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| component | – | – | – |
| customFields | object | – | – |
| estimatedTime | – | – | – |
| folder | – | – | – |
| id | integer | – | – |
| key | string | – | – |
| labels | array | – | – |
| name | string | – | – |
| objective | string|null | – | – |
| owner | – | – | – |
| precondition | string|null | – | – |
| priority | object | – | – |
| project | object | – | – |
| status | object | – | – |
| testCaseKey | string | yes | – |
No output schema declared.
No examples provided.
zephyr_update_test_cycle ~1,185
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| customFields | object | – | – |
| description | string|null | – | – |
| folder | – | – | – |
| id | integer | – | – |
| jiraProjectVersion | – | – | – |
| key | string | – | – |
| name | string | – | – |
| owner | – | – | – |
| plannedEndDate | – | – | – |
| plannedStartDate | – | – | – |
| project | object | – | – |
| status | object | – | – |
| testCycleIdOrKey | string | yes | – |
No output schema declared.
No examples provided.
zephyr_update_test_execution ~752
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| actualEndDate | string | – | – |
| assignedToId | – | – | – |
| comment | string|null | – | – |
| environmentName | string | – | – |
| executedById | – | – | – |
| executionTime | integer | – | – |
| statusName | string | – | – |
| testExecutionIdOrKey | string | yes | – |
No output schema declared.
No examples provided.
zephyr_update_test_execution_steps ~500
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| steps | array | – | – |
| testExecutionIdOrKey | string | yes | – |
No output schema declared.
No examples provided.
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
claude mcp add com-smartbear-smartbear-mcp -- npx -y @smartbear/mcp
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.