Is mcp-use safe to use?

mcp-use has an HVTrust score of 64.2/100 (Grade C), ranked #253 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for mcp-use?

mcp-use scores 64.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 10.5k GitHub stars and is categorized under Protocols & Tool Integration.

mcp-use

mcp-use/mcp-use

The fullstack MCP framework to develop MCP Apps for ChatGPT / Claude & MCP Servers for AI Agents.

Protocols & Tool Integration TypeScript Grade C Listed MIT

64.2/100

Rank #253 of 1308

Compare mcp-use

How does it stack up against its Protocols & Tool Integration neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-18 · 1d ago

Recent change

Rank +4

Is mcp-use safe? mcp-use scores 64.2/100 (Grade C), ranked #253 of 1308 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.1/10; 79% of recent commits are signed; last pushed 2026-08-18. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

#19 Serena — 65.5 (B) → #20 AG-UI — 64.6 (C) → #22 A2UI — 63.9 (C) → #23 Model Context Protocol / MCP — 63.8 (C) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-08-19

Rank Moved

Rank dropped 13 spots (#240 → #253)

2026-08-17

Rank Moved

Rank rose 14 spots (#247 → #233)

2026-08-14

Rank Moved

Rank rose 19 spots (#257 → #238)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.1/10. Tighten the weakest checks to improve public safety evidence.

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 mcp-use View Protocols & Tool Integration Report missing data

88.8

Activity sub-score · out of 100

#21

In Protocols & Tool Integration

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

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars

10.5k

Forks

1.4k

Last Push

2026-08-18

yesterday

Commits (4 wk)

343

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼13

was #240

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

64.2 / 100 · 100.0% confidence

mcp-use Protocols & Tool Integration average (58 agents)

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

10.3 / 25

1.8 above avg 8.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.9 below avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

12.8 / 17

1.4 above avg 11.4

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

6.0 above avg 13.9

AdoptionLog-scaled stars · package downloads

9.7 / 20

0.6 below avg 10.3

Activity Inputs

88.8 / 100

StarsRepository reach

24.1 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

14.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.1 / 10

OpenSSF Scorecard · scanned Aug 18, 2026

Signed Commits

79%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 9

CII-Best-Practices 0

Code-Review 3

Contributors 10

Dangerous-Workflow 0

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 8

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is mcp-use safe?

mcp-use 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 mcp-use publish package provenance?

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

Does mcp-use have an OpenSSF Scorecard?

mcp-use has an OpenSSF Scorecard score of 5.1/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 mcp-use actively maintained?

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

What license does mcp-use use?

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

Are mcp-use's commits signed?

79% of the last 100 commits to mcp-use 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

mcp-use appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

3 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

Detailed evidence is not shown in the public view.

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

Maintain mcp-use?

For maintainers

HVTrust scores mcp-use 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-08-19

Rank Moved

Rank dropped 13 spots (#240 → #253)

2026-08-17

Rank Moved

Rank rose 14 spots (#247 → #233)

2026-08-14

Rank Moved

Rank rose 19 spots (#257 → #238)

2026-08-13

Rank Moved

Rank dropped 18 spots (#239 → #257)

2026-08-12

Rank Moved

Rank rose 17 spots (#256 → #239)

2026-08-10

Rank Moved

Rank dropped 30 spots (#230 → #260)

2026-08-08

Rank Moved

Rank dropped 42 spots (#175 → #217)

2026-08-06

Rank Moved

Rank rose 23 spots (#204 → #181)

2026-08-03

Rank Moved

Rank rose 30 spots (#229 → #199)

2026-08-03

Activity Score Changed

Activity score up 8pts (81 → 89)

2026-07-25

Rank Moved

Rank dropped 22 spots (#197 → #219)

2026-07-15

Rank Moved

Rank dropped 11 spots (#192 → #203)

2026-07-14

Rank Moved

Rank dropped 12 spots (#180 → #192)

2026-07-13

Rank Moved

Rank dropped 23 spots (#157 → #180)

2026-06-21

Scorecard Added

OSSF Scorecard: 6.0/10

2026-06-21

Grade Changed

Trust grade D → C

2026-06-21

Rank Moved

Rank rose 114 spots (#241 → #127)

2026-06-21

HVTrust Changed

HVTrust up 38.1pts (25.5 → 63.6)

2026-06-20

Newly Listed

First tracked at rank #241

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Protocols & Tool Integration

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