Is SmartBear MCP safe to use?

SmartBear MCP has an HVTrust score of 70.6/100 (Grade B), ranked #322 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for SmartBear MCP?

SmartBear MCP scores 70.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 44 GitHub stars and is categorized under MCP Servers.

SmartBear MCP

SmartBear/smartbear-mcp

SmartBear's official MCP Server

MCP Servers TypeScript Listed MIT

Is SmartBear MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 7.0 / 10

Provenance None

Signed commits 97%

Last push yesterday

Compare SmartBear MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: SmartBear MCP scores 70.6/100 (Grade B), ranked #322 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 7.0/10; 97% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How SmartBear MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks SmartBear MCP’s 70.6.

Where the 70.6 comes from

HVTrust dimensions vs the MCP Servers average

70.6 / 100 · 100.0% confidence

SmartBear MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

13.6 / 25

3.3 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

14.4 / 17

2.2 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

17.5 / 20

5.5 above avg 12.0

AdoptionLog-scaled stars · package downloads

9.3 / 20

2.1 above avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 355 spots (#665 → #310)

Maintainer Checklist

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent Get email alerts for SmartBear MCP View MCP Servers Report missing data

60.1

Activity sub-score · out of 100

#192

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-25

yesterday

Commits (4 wk)

Downloads (7d)

9,470

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼3

was #319

Analysis

Activity Inputs

60.1 / 100

StarsRepository reach

9.9 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

17.4 / 25

CommunityFork signal

7.9 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

7.0 / 10

OpenSSF Scorecard · scanned Sep 25, 2026

Signed Commits

97%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 10

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 8

SAST 10

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 5

Common questions about SmartBear MCP

SmartBear MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does SmartBear MCP publish package provenance?

No published build provenance is currently detected for SmartBear MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does SmartBear MCP have an OpenSSF Scorecard?

SmartBear MCP has an OpenSSF Scorecard score of 7.0/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is SmartBear MCP actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does SmartBear MCP use?

SmartBear MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are SmartBear MCP's commits signed?

97% of the last 100 commits to SmartBear MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

SmartBear MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to SmartBear MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain SmartBear MCP?

For maintainers

HVTrust scores SmartBear MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 355 spots (#665 → #310)

2026-09-23

HVTrust Changed

HVTrust up 39.3pts (31.6 → 70.9)

2026-09-22

Newly Listed

First tracked at rank #665

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-13

Rank Moved

Rank dropped 21 spots (#281 → #302)

2026-09-05

Grade Changed

Trust grade D → B

2026-09-05

Rank Moved

Rank rose 655 spots (#908 → #253)

2026-09-05

HVTrust Changed

HVTrust up 25.9pts (45.6 → 71.5)

2026-09-04

Rank Moved

Rank dropped 28 spots (#880 → #908)

2026-09-03

Rank Moved

Rank dropped 53 spots (#827 → #880)

2026-09-02

Rank Moved

Rank dropped 39 spots (#788 → #827)

2026-09-01

Rank Moved

Rank dropped 28 spots (#760 → #788)

2026-08-31

Scorecard Added

OSSF Scorecard: 7.1/10

2026-08-31

Rank Moved

Rank rose 374 spots (#1134 → #760)

2026-08-31

HVTrust Changed

HVTrust up 22.1pts (23.4 → 45.5)

2026-08-30

Rank Moved

Rank dropped 38 spots (#1096 → #1134)

2026-08-29

Rank Moved

Rank dropped 43 spots (#1053 → #1096)

2026-08-28

Rank Moved

Rank dropped 25 spots (#1028 → #1053)

2026-08-27

Rank Moved

Rank dropped 23 spots (#1005 → #1028)

2026-08-26

Rank Moved

Rank dropped 94 spots (#911 → #1005)

2026-08-17

Rank Moved

Rank rose 15 spots (#938 → #923)

2026-08-16

Rank Moved

Rank dropped 29 spots (#909 → #938)

2026-08-14

Rank Moved

Rank rose 11 spots (#917 → #906)

2026-08-13

Rank Moved

Rank dropped 13 spots (#904 → #917)

2026-08-10

Rank Moved

Rank dropped 53 spots (#854 → #907)

2026-08-08

Newly Listed

First tracked at rank #850

GitHub → npm: @smartbear/mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/smartbear-mcp.svg)](https://hvtracker.net/agents/smartbear-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/smartbear-mcp"><img src="https://hvtracker.net/badge/smartbear-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON