Is MCP Toolbox for Databases safe to use?

MCP Toolbox for Databases has an HVTrust score of 27.6/100 (Grade D), ranked #808 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 Toolbox for Databases?

MCP Toolbox for Databases scores 27.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 16.2k GitHub stars and is categorized under MCP Servers.

MCP Toolbox for Databases

googleapis/mcp-toolbox

MCP Toolbox for Databases is an open source MCP server for databases.

MCP Servers Go Grade D Listed Apache-2.0

27.6/100

Rank #808 of 1308

Compare MCP Toolbox for Databases

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 D · 1/5 signals

Last push

2026-08-19 · 0d ago

Recent change

Rank +1

Is MCP Toolbox for Databases safe? MCP Toolbox for Databases scores 27.6/100 (Grade D), ranked #808 of 1308 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; 100% of recent commits are signed; last pushed 2026-08-19. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#387 Greptimedb MCP Server — 27.6 (D) → #388 Apple Docs MCP — 27.6 (D) → #390 Kylas CRM — 27.5 (D) → #391 Scopus MCP — 27.1 (D) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-17

Rank Moved

Rank rose 10 spots (#810 → #800)

2026-08-16

Rank Moved

Rank dropped 17 spots (#793 → #810)

2026-08-10

Rank Moved

Rank dropped 43 spots (#751 → #794)

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

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 Toolbox for Databases View MCP Servers Report missing data

90.2

Activity sub-score · out of 100

#389

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 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

2026-08-11 2026-08-19

Activity & Reach

Stars

16.2k

Forks

1.7k

Last Push

2026-08-19

today

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

128

Rank Change

▼8

was #800

Analysis

HVTrust Dimensions vs MCP Servers

27.6 / 100 · 50.0% confidence

MCP Toolbox for Databases MCP Servers average (775 agents)

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

5.0 / 25

in line with avg 5.0

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.5 below avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

in line with avg 8.8

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

7.6 above avg 12.4

AdoptionLog-scaled stars · package downloads

10.1 / 20

4.3 above avg 5.8

Activity Inputs

90.2 / 100

StarsRepository reach

25.3 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

24.9 / 25

CommunityFork signal

15.0 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

100%

of last 100 commits verified

Is MCP Toolbox for Databases safe?

Public trust evidence for MCP Toolbox for Databases 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 MCP Toolbox for Databases publish package provenance?

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

No OpenSSF Scorecard data is currently published for MCP Toolbox for Databases. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

Is MCP Toolbox for Databases actively maintained?

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

What license does MCP Toolbox for Databases use?

MCP Toolbox for Databases ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MCP Toolbox for Databases's commits signed?

100% of the last 100 commits to MCP Toolbox for Databases 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

medium confidence

Implemented

MCP Toolbox for Databases appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Google Gemini

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Extensions

Extension based 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 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-17

Rank Moved

Rank rose 10 spots (#810 → #800)

2026-08-16

Rank Moved

Rank dropped 17 spots (#793 → #810)

2026-08-10

Rank Moved

Rank dropped 43 spots (#751 → #794)

2026-08-08

Rank Moved

Rank dropped 319 spots (#428 → #747)

2026-07-29

Rank Moved

Rank dropped 11 spots (#409 → #420)

2026-07-15

Rank Moved

Rank dropped 24 spots (#377 → #401)

2026-07-14

Newly Listed

First tracked at rank #377

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mcp-toolbox-for-databases.svg)](https://hvtracker.net/agents/mcp-toolbox-for-databases)
            
HTML:
            <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

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