Dbmcp

Database MCP server for MySQL, MariaDB, PostgreSQL, and SQLite - with builtin PII redaction and write-prevention

MCP Servers Rust Listed MIT

Is Dbmcp safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.8 / 10
Provenance None
Signed commits 77%
Last push 8d ago
Compare Dbmcp
Suggest a correction

In detail: Dbmcp scores 48.8/100 (Grade D), ranked #973 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 3.8/10; 77% of recent commits are signed; last pushed 2026-09-18. Every point is earned from checkable signals — never paid placement. How scoring works →

How Dbmcp compares in MCP Servers

  1. #562 Mobile Device MCP 48.9 +0.1
  2. #563 Codex MCP Tool 48.9 +0.1
  3. #564 Dbmcp 48.8 this agent
  4. #565 Debridge MCP 48.8 ±0
  5. #566 Librecrawl — Technical SEO Audit MCP Server 48.8 ±0

Bars show each HVTrust score; the tick marks Dbmcp’s 48.8.

Where the 48.8 comes from

HVTrust dimensions vs the MCP Servers average

48.8 / 100 · 100.0% confidence

Dbmcp MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.6 / 25
1.7 below avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
11.7 / 17
0.5 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
12.1 / 20
in line with avg 12.1
AdoptionLog-scaled stars · package downloads
3.6 / 20
3.6 below avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-25
Rank Moved
Rank dropped 11 spots (#961 → #972)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 93 spots (#1051 → #958)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.8/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.
41.1
Activity sub-score · out of 100
#564

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 →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed 8 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
32
Forks
7
Last Push
2026-09-18
8 days ago
Commits (4 wk)
1?
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
11
Rank Change
▼1
was #972

Analysis

Activity Inputs

41.1 / 100
StarsRepository reach
9.1 / 30
FreshnessLast push recency
23.9 / 25
ActivityRecent commits
3.8 / 25
CommunityFork signal
4.2 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.8 / 10
OpenSSF Scorecard · scanned Sep 20, 2026
Signed Commits
77%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 0
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 0
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 10
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 0

Common questions about Dbmcp

Public trust evidence for Dbmcp 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 Dbmcp publish package provenance?
No published build provenance is currently detected for Dbmcp. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Dbmcp have an OpenSSF Scorecard?
Dbmcp has an OpenSSF Scorecard score of 3.8/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 Dbmcp actively maintained?
Maintained. Last push was 8 days ago.
What license does Dbmcp use?
Dbmcp ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Dbmcp's commits signed?
77% of the last 100 commits to Dbmcp 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
Dbmcp appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
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 Dbmcp'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-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Dbmcp?

For maintainers

HVTrust scores Dbmcp 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
Rank 29HVTrust 11Listed 2Scorecard 1Score 1Delisted 1MCP 1
2026-09-25
Rank Moved
Rank dropped 11 spots (#961 → #972)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 93 spots (#1051 → #958)
2026-09-23
HVTrust Changed
HVTrust up 25.5pts (23.5 → 49.0)
2026-09-22
Newly Listed
First tracked at rank #1051
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 315 spots (#945 → #1260)
2026-09-20
HVTrust Changed
HVTrust down 15.7pts (49.2 → 33.5)
2026-09-18
Rank Moved
Rank rose 49 spots (#995 → #946)
2026-09-18
Activity Score Changed
Activity score up 6pts (36 → 42)
2026-09-16
Rank Moved
Rank rose 285 spots (#1272 → #987)
2026-09-16
HVTrust Changed
HVTrust up 15.2pts (32.5 → 47.7)
2026-09-15
Rank Moved
Rank dropped 284 spots (#988 → #1272)
2026-09-15
HVTrust Changed
HVTrust down 15.3pts (47.8 → 32.5)
2026-09-14
Rank Moved
Rank rose 282 spots (#1270 → #988)
2026-09-14
HVTrust Changed
HVTrust up 15.2pts (32.6 → 47.8)
2026-09-12
Rank Moved
Rank dropped 289 spots (#977 → #1266)
2026-09-12
HVTrust Changed
HVTrust down 15.3pts (48.0 → 32.7)
2026-09-11
Rank Moved
Rank dropped 13 spots (#964 → #977)
2026-09-09
Rank Moved
Rank dropped 24 spots (#938 → #962)
2026-09-08
Rank Moved
Rank dropped 16 spots (#922 → #938)
2026-09-07
Rank Moved
Rank dropped 39 spots (#883 → #922)
2026-09-06
Rank Moved
Rank rose 326 spots (#1209 → #883)
2026-09-06
HVTrust Changed
HVTrust up 15.6pts (33.3 → 48.9)
2026-09-05
Rank Moved
Rank dropped 399 spots (#810 → #1209)
2026-09-05
HVTrust Changed
HVTrust down 15.7pts (49.0 → 33.3)
2026-09-04
Rank Moved
Rank dropped 35 spots (#775 → #810)
2026-09-03
Rank Moved
Rank rose 345 spots (#1120 → #775)
2026-09-03
HVTrust Changed
HVTrust up 15.7pts (33.4 → 49.1)
2026-09-02
Rank Moved
Rank dropped 423 spots (#697 → #1120)
2026-09-02
HVTrust Changed
HVTrust down 15.8pts (49.2 → 33.4)
2026-09-01
Rank Moved
Rank rose 17 spots (#714 → #697)
2026-08-31
Rank Moved
Rank dropped 36 spots (#678 → #714)
2026-08-30
Rank Moved
Rank dropped 22 spots (#656 → #678)
2026-08-29
Scorecard Added
OSSF Scorecard: 4.0/10
2026-08-29
Rank Moved
Rank rose 493 spots (#1149 → #656)
2026-08-29
HVTrust Changed
HVTrust up 26.8pts (20.5 → 47.3)
2026-08-28
Rank Moved
Rank dropped 25 spots (#1124 → #1149)
2026-08-27
Rank Moved
Rank dropped 16 spots (#1108 → #1124)
2026-08-26
Rank Moved
Rank dropped 68 spots (#1040 → #1108)
2026-08-17
Rank Moved
Rank rose 13 spots (#1043 → #1030)
2026-08-16
Rank Moved
Rank dropped 35 spots (#1008 → #1043)
2026-08-13
Rank Moved
Rank dropped 12 spots (#1000 → #1012)
2026-08-12
Rank Moved
Rank rose 14 spots (#1014 → #1000)
2026-08-10
Rank Moved
Rank dropped 61 spots (#948 → #1009)
2026-08-08
Newly Listed
First tracked at rank #941

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 48.8 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/dbmcp.svg)](https://hvtracker.net/agents/dbmcp)
HTML:
<a href="https://hvtracker.net/agents/dbmcp"><img src="https://hvtracker.net/badge/dbmcp.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