db-mcp (SQLite MCP Server)
Website
Secure Database MCP Server featuring a V8 Isolate Code Mode sandbox that unifies 181+ tools, delivering 70-90% token savings. Built for enterprise with HTTP/SSE transports, OAuth 2.1, dynamic filtering, granular RBAC, audit logging, deterministic error handling, Prometheus metrics, and encryption…
Is db-mcp (SQLite MCP Server) safe? Promising trust profile, but some evidence still deserves review.
Compare db-mcp (SQLite MCP Server)
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: db-mcp (SQLite MCP Server) scores 70.2/100 (Grade B), ranked #374 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.0/10; 34% of recent commits are signed; no published advisory affects its latest release (db-mcp); last pushed 2026-09-29. Every point is earned from checkable signals — never paid placement. How scoring works →
How db-mcp (SQLite MCP Server) 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 from 6.0 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Fuzzing 0 +6.3 → 76.5 B · #141 of 778
- Sign every commit34% signed today +3.3 → 73.5 B · #174 of 778
Chain of custody
Scanners check what the code says. This traces who ships db-mcp (SQLite MCP Server) and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/neverinfamous/db-mcp, MIT, last pushed 2026-09-29. 34% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 6.0/10 (scanned Nov 9, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection1
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions10
- Pinned Dependencies9
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 1CI-Tests 10CII-Best-Practices 0Code-Review 0Contributors 3Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 10Maintained 0Packaging 10Pinned-Dependencies 9SAST 10Security-Policy 10Signed-Releases -1Token-Permissions 10Vulnerabilities 0 -
Published packages Linked and attested
- npm db-mcp Source link points back to this repo Build provenance attested
-
What you install today No known advisories
Latest release checked: db-mcp 5.0.1. No published advisory affects it (OSV, checked 2026-11-10).
Changes to this chain
- 2026-09-23 Package provenance attestation detected
- 2026-08-28 OSSF Scorecard: 6.5/10
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues db-mcp (SQLite MCP Server)’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 db-mcp (SQLite MCP Server) compares in MCP Servers
- #220 Marlinjai Email MCP 70.3 +0.1
- #221 PageIndex MCP 70.3 +0.1
- #222 db-mcp (SQLite MCP Server) 70.2 this agent
- #223 MCP Atlassian 70.1 −0.1
- #224 Unity API Documentation 70.0 −0.2
Bars show each HVTrust score; the tick marks db-mcp (SQLite MCP Server)’s 70.2.
Where the 70.2 comes from
HVTrust dimensions vs the MCP Servers average
70.2 / 100 · 100.0% confidencedb-mcp (SQLite MCP Server) MCP Servers average (778 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 B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
27.5 / 100Common questions about db-mcp (SQLite MCP Server)
Does db-mcp (SQLite MCP Server) publish package provenance?
Does db-mcp (SQLite MCP Server) have an OpenSSF Scorecard?
Is db-mcp (SQLite MCP Server) actively maintained?
What license does db-mcp (SQLite MCP Server) use?
Are db-mcp (SQLite MCP Server)'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 →
- database
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to db-mcp (SQLite MCP Server)'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 db-mcp (SQLite MCP Server)?
For maintainers
HVTrust scores db-mcp (SQLite MCP Server) 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/db-mcp-sqlite-mcp-server)
<a href="https://hvtracker.net/agents/db-mcp-sqlite-mcp-server"><img src="https://hvtracker.net/badge/db-mcp-sqlite-mcp-server.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON