OneTool MCP
🧿 One MCP for developers - no tool tax, no context rot. 100+ tools including Brave, Google, Context7, Excalidraw, AWS, Version Checker, Excel, File Ops, Database, Playwright, Chrome DevTools and many more.
Is OneTool MCP safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare OneTool MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: OneTool MCP scores 38.5/100 (Grade D), ranked #1192 of 1325 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 →
How OneTool MCP compares in MCP Servers
- #708 Unreal MCP Ue4 38.7 +0.2
- #709 Terminal MCP Server 38.5 ±0
- #710 OneTool MCP 38.5 this agent
- #711 Augments MCP Server 38.4 −0.1
- #712 Paypal MCP Server 38.3 −0.2
Bars show each HVTrust score; the tick marks OneTool MCP’s 38.5.
Where the 38.5 comes from
HVTrust dimensions vs the MCP Servers average
38.5 / 100 · 100.0% confidenceOneTool MCP MCP Servers average (775 agents)
Quick Trust Read
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
Activity & Reach
Analysis
Activity Inputs
34.1 / 100Supply Chain Trust
Common questions about OneTool MCP
Does OneTool MCP publish package provenance?
Does OneTool MCP have an OpenSSF Scorecard?
Is OneTool MCP actively maintained?
What license does OneTool MCP use?
Are OneTool MCP's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
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.
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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/onetool-mcp)
<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
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