SmartBear MCP
NPM · @SMARTBEAR/MCP · 3 COMPONENTS · SCANNED SEP 20
MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.
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 Security98
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 143 of 144 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 143 of 144 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 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, so we will not judge it on a partial copy.Unverified
Stability & Change Management0
- Stability not yet verified: the captured schema was too large for us to store in full, and comparing a partial copy would report our own trimming as a change.Unverified
Tool Coverage0
- Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, 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, and the trim removes the very descriptions this category reads.Unverified
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 4 categories
Categories scored 0 because our sandbox run of this package 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 →
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
{
"mcpServers": {
"com-smartbear-smartbear-mcp": {
"command": "npx",
"args": [
"-y",
"@smartbear/mcp"
]
}
}
} {
"servers": {
"com-smartbear-smartbear-mcp": {
"command": "npx",
"args": [
"-y",
"@smartbear/mcp"
]
}
}
} codex mcp add com-smartbear-smartbear-mcp -- npx -y @smartbear/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-smartbear-smartbear-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@smartbear/mcp"
],
"enabled": true
}
}
} openclaw mcp add com-smartbear-smartbear-mcp --command npx --arg -y --arg @smartbear/mcp
mcp_servers:
com-smartbear-smartbear-mcp:
command: "npx"
args: ["-y", "@smartbear/mcp"] {
"McpServers": {
"com-smartbear-smartbear-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@smartbear/mcp"
]
}
}
} assistant mcp add com-smartbear-smartbear-mcp -t stdio -c npx -a -y @smartbear/mcp
{
"mcpServers": {
"com-smartbear-smartbear-mcp": {
"command": "npx",
"args": [
"-y",
"@smartbear/mcp"
]
}
}
} 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.
- 18 Sept 26 0
- Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 0.40.0 → 0.41.0 functional
- 4 Sept 26 +10
- Known CVEs: unverified → partial ▲ security
- Dependency health: unverified → partial ▲ functional
- 3 Sept 26 −10
- Known CVEs: partial → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Dependency health: partial → unverified ▼ functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Package version: 0.39.0 → 0.40.0 functional
- 31 Aug 26 0
- Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Package version: 0.38.0 → 0.39.0 functional
- 28 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Aug 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.37.0 → 0.38.0 functional
- 26 Aug 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Aug 26 0
- Known CVEs: unverified → partial ▲ security
- Dependency health: unverified → partial ▲ functional
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 20 Sept 2026 · Analysed npm/@smartbear/mcp@0.41.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 143 packages
| Packages resolved | 143 |
|---|---|
| Deprecated | 1 |
| Stale | 30 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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_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.
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 43 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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 20 September 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.