MCP Toolbox for Databases
Website
MCP Toolbox for Databases is an open source MCP server for databases.
Is MCP Toolbox for Databases safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare MCP Toolbox for Databases
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: MCP Toolbox for Databases scores 26.9/100 (Grade D), ranked #1344 of 1371 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 90% of recent commits are signed; last pushed 2026-10-12. Every point is earned from checkable signals — never paid placement. How scoring works →
How MCP Toolbox for Databases could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard to 9.0no OSSF Scorecard result yet +45.4 → 72.3 B · #181 of 781
Chain of custody
Scanners check what the code says. This traces who ships MCP Toolbox for Databases and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Signed
github.com/googleapis/mcp-toolbox, Apache-2.0, last pushed 2026-10-12. 90% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
Review and release Not checked
No OpenSSF Scorecard result yet, so branch protection, code review and release signing are unverified.
-
Published packages None
No registry package. MCP Toolbox for Databases is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of MCP Toolbox for Databases.
Evidence behind this score
Coverage D: 1 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks (missing)
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues MCP Toolbox for Databases’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How MCP Toolbox for Databases compares in MCP Servers
- #775 Fortnox MCP 27.6 +0.7
- #776 Hatago MCP Hub 27.4 +0.5
- #777 MCP Toolbox for Databases 26.9 this agent
- #778 Driflyte MCP Server 26.7 −0.2
- #779 Chat on Steroids 26.7 −0.2
Bars show each HVTrust score; the tick marks MCP Toolbox for Databases’s 26.9.
Where the 26.9 comes from
HVTrust dimensions vs the MCP Servers average
26.9 / 100 · 50.0% confidenceMCP Toolbox for Databases MCP Servers average (781 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 D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
87.9 / 100Common questions about MCP Toolbox for Databases
Does MCP Toolbox for Databases publish package provenance?
Does MCP Toolbox for Databases have an OpenSSF Scorecard?
Is MCP Toolbox for Databases actively maintained?
What license does MCP Toolbox for Databases use?
Are MCP Toolbox for Databases'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
Maintain MCP Toolbox for Databases?
For maintainers
HVTrust scores MCP Toolbox for Databases 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/mcp-toolbox-for-databases)
<a href="https://hvtracker.net/agents/mcp-toolbox-for-databases"><img src="https://hvtracker.net/badge/mcp-toolbox-for-databases.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON