Is OneTool MCP safe to use?

OneTool MCP has an HVTrust score of 39.9/100 (Grade D), ranked #1043 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for OneTool MCP?

OneTool MCP scores 39.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 23 GitHub stars and is categorized under MCP Servers.

OneTool MCP

beycom/onetool-mcp

🧿 One MCP for developers - no tool tax, no context rot. 100+ tools including Brave, Google, Context7, Excalidraw, AWS, V

MCP Servers Python Grade D Listed GPL-3.0

39.9/100

Rank #1043 of 1320

Compare OneTool MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-09-01 · 3d ago

Recent change

Rank +7

Is OneTool MCP safe? OneTool MCP scores 39.9/100 (Grade D), ranked #1043 of 1320 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 2.4/10; recent commits are unsigned; last pushed 2026-09-01. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#583 Parallel Browser MCP — 40.0 (D) → #584 Android MCP Server — 39.9 (D) → #586 Agent Security Scanner MCP — 39.9 (D) → #587 MCP Console Automation — 39.9 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-04

Rank Moved

Rank dropped 14 spots (#1029 → #1043)

2026-09-03

Rank Moved

Rank dropped 58 spots (#971 → #1029)

2026-09-02

Rank Moved

Rank dropped 49 spots (#922 → #971)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.4/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.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

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

36.8

Activity sub-score · out of 100

#585

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 D 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-09-04

Activity & Reach

Stars

Forks

Last Push

2026-09-01

3 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼14

was #1029

Analysis

HVTrust Dimensions vs MCP Servers

39.9 / 100 · 100.0% confidence

OneTool MCP MCP Servers average (778 agents)

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

3.0 / 25

6.5 below avg 9.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

10.5 / 17

1.3 below avg 11.8

Maintenance60% last-push freshness · 40% commit activity

11.8 / 20

in line with avg 12.2

AdoptionLog-scaled stars · package downloads

3.3 / 20

2.9 below avg 6.2

Activity Inputs

36.8 / 100

StarsRepository reach

8.3 / 30

FreshnessLast push recency

24.6 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

3.9 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

2.4 / 10

OpenSSF Scorecard · scanned Aug 27, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 0

Is OneTool MCP safe?

Public trust evidence for OneTool MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does OneTool MCP publish package provenance?

No published build provenance is currently detected for OneTool 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 OneTool MCP have an OpenSSF Scorecard?

OneTool MCP has an OpenSSF Scorecard score of 2.4/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 OneTool MCP actively maintained?

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

What license does OneTool MCP use?

OneTool MCP ships under GPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are OneTool MCP's commits signed?

0% of the last 100 commits to OneTool 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

OneTool MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies 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

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

How this surface has changed

Detected changes to OneTool 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-08-12

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

Maintain OneTool MCP?

For maintainers

HVTrust scores OneTool 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-04

Rank Moved

Rank dropped 14 spots (#1029 → #1043)

2026-09-03

Rank Moved

Rank dropped 58 spots (#971 → #1029)

2026-09-02

Rank Moved

Rank dropped 49 spots (#922 → #971)

2026-09-01

Rank Moved

Rank dropped 34 spots (#888 → #922)

2026-08-31

Rank Moved

Rank dropped 26 spots (#862 → #888)

2026-08-30

Rank Moved

Rank dropped 37 spots (#825 → #862)

2026-08-29

Rank Moved

Rank dropped 46 spots (#779 → #825)

2026-08-28

Rank Moved

Rank dropped 27 spots (#752 → #779)

2026-08-27

Scorecard Added

OSSF Scorecard: 2.4/10

2026-08-27

Rank Moved

Rank rose 468 spots (#1220 → #752)

2026-08-27

HVTrust Changed

HVTrust up 22.4pts (17.7 → 40.1)

2026-08-26

Rank Moved

Rank dropped 32 spots (#1188 → #1220)

2026-08-24

Rank Moved

Rank dropped 29 spots (#1160 → #1189)

2026-08-24

Activity Score Changed

Activity score down 6pts (43 → 37)

2026-08-21

Rank Moved

Rank rose 14 spots (#1179 → #1165)

2026-08-20

Rank Moved

Rank dropped 12 spots (#1167 → #1179)

2026-08-16

Rank Moved

Rank dropped 24 spots (#1143 → #1167)

2026-08-15

Rank Moved

Rank rose 11 spots (#1154 → #1143)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

2026-08-11

Activity Score Changed

Activity score down 11pts (54 → 43)

2026-08-10

Rank Moved

Rank dropped 106 spots (#932 → #1038)

2026-08-10

Activity Score Changed

Activity score down 6pts (61 → 54)

2026-08-08

Newly Listed

First tracked at rank #927

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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