Is MCP Sqlite Tools safe to use?

MCP Sqlite Tools has an HVTrust score of 59.1/100 (Grade C), ranked #716 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Sqlite Tools?

MCP Sqlite Tools scores 59.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 20 GitHub stars and is categorized under MCP Servers.

MCP Sqlite Tools

Repository by spences10

A Model Context Protocol (MCP) server that provides comprehensive SQLite database operations for LLMs. This server enables AI assistants to interact with local SQLite databases safely and efficiently, with built-in security features, advanced transaction support, and clear separation between…

MCP Servers TypeScript Listed MIT

Is MCP Sqlite Tools safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.0 / 10

Provenance None

Signed commits 100%

Last push 3d ago

Advisories None known

Compare MCP Sqlite Tools

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP Sqlite Tools scores 59.1/100 (Grade C), ranked #716 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.0/10; 100% of recent commits are signed; no published advisory affects its latest release (mcp-sqlite-tools); last pushed 2026-11-07. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Sqlite Tools 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.

Publish build provenance for its packagesnpm publish --provenance from CI +14.8 → 73.9 B · #170 of 778
Raise the OSSF Scorecard from 5.0 to 9.0lowest checks: Branch-Protection 0, CI-Tests 0, CII-Best-Practices 0 +8.3 → 67.4 B · #260 of 778

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships MCP Sqlite Tools 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 Signed

github.com/spences10/mcp-sqlite-tools, MIT, last pushed 2026-11-07. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 5.0/10 (scanned Nov 5, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflown/a
- Token Permissionsn/a
- Pinned Dependenciesn/a
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow -1

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 10
Published packages Not linked
- npm mcp-sqlite-tools No source link declared No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
What you install today No known advisories

Latest release checked: mcp-sqlite-tools 0.1.1. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

2026-08-26 OSSF Scorecard: 5.0/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 MCP Sqlite Tools’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.

Signed credential (JSON) How to verify

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 Sqlite Tools compares in MCP Servers

Bars show each HVTrust score; the tick marks MCP Sqlite Tools’s 59.1.

Where the 59.1 comes from

HVTrust dimensions vs the MCP Servers average

59.1 / 100 · 100.0% confidence

MCP Sqlite Tools MCP Servers average (778 agents)

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

11.2 / 25

in line with avg 10.8

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.9 below avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

12.8 / 17

in line with avg 12.3

Maintenance60% last-push freshness · 40% commit activity

16.2 / 20

4.0 above avg 12.2

AdoptionLog-scaled stars · package downloads

6.1 / 20

1.5 below avg 7.6

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-10-29

Rank Moved

Rank rose 13 spots (#725 → #712)

2026-10-28

Rank Moved

Rank dropped 21 spots (#704 → #725)

2026-10-22

Rank Moved

Rank dropped 27 spots (#677 → #704)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.0/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.

Compare with another agent View MCP Servers Report missing data

50.0

Activity sub-score · out of 100

#390

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

2026-09-29 2026-11-10

Activity & Reach

Stars

Forks

Last Push

2026-11-07

3 days ago

Commits (4 wk)

Downloads (7d)

161

npm

HN mentions (30d)

—

Open Issues

Rank Change

was #716

Analysis

Activity Inputs

50.0 / 100

StarsRepository reach

7.9 / 30

FreshnessLast push recency

24.6 / 25

ActivityRecent commits

13.9 / 25

CommunityFork signal

3.6 / 20

Common questions about MCP Sqlite Tools

MCP Sqlite Tools has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does MCP Sqlite Tools publish package provenance?

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

MCP Sqlite Tools has an OpenSSF Scorecard score of 5.0/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 MCP Sqlite Tools actively maintained?

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

What license does MCP Sqlite Tools use?

MCP Sqlite Tools ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MCP Sqlite Tools's commits signed?

100% of the last 100 commits to MCP Sqlite Tools 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

high confidence

Implemented

MCP Sqlite Tools 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

low confidence

Unknown

Package source metadata is missing or inconclusive

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 MCP Sqlite Tools'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 MCP Sqlite Tools?

For maintainers

HVTrust scores MCP Sqlite Tools 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-10-29

Rank Moved

Rank rose 13 spots (#725 → #712)

2026-10-28

Rank Moved

Rank dropped 21 spots (#704 → #725)

2026-10-22

Rank Moved

Rank dropped 27 spots (#677 → #704)

2026-10-19

Rank Moved

Rank dropped 14 spots (#662 → #676)

2026-10-10

Rank Moved

Rank dropped 13 spots (#637 → #650)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 249 spots (#857 → #608)

2026-09-23

HVTrust Changed

HVTrust up 33.1pts (27.6 → 60.7)

2026-09-22

Newly Listed

First tracked at rank #857

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank rose 14 spots (#636 → #622)

2026-09-16

Rank Moved

Rank dropped 13 spots (#619 → #632)

2026-09-15

Rank Moved

Rank dropped 25 spots (#594 → #619)

2026-09-07

Rank Moved

Rank dropped 55 spots (#510 → #565)

2026-09-06

Grade Changed

Trust grade D → C

2026-09-06

Rank Moved

Rank rose 593 spots (#1103 → #510)

2026-09-06

HVTrust Changed

HVTrust up 21.6pts (39.5 → 61.1)

2026-09-05

Rank Moved

Rank dropped 34 spots (#1069 → #1103)

2026-09-04

Rank Moved

Rank dropped 29 spots (#1040 → #1069)

2026-09-03

Rank Moved

Rank dropped 53 spots (#987 → #1040)

2026-09-02

Rank Moved

Rank dropped 47 spots (#940 → #987)

2026-09-01

Rank Moved

Rank dropped 32 spots (#908 → #940)

2026-08-31

Rank Moved

Rank dropped 34 spots (#874 → #908)

2026-08-30

Rank Moved

Rank dropped 37 spots (#837 → #874)

2026-08-29

Rank Moved

Rank dropped 43 spots (#794 → #837)

2026-08-28

Rank Moved

Rank dropped 21 spots (#773 → #794)

2026-08-27

Rank Moved

Rank dropped 22 spots (#751 → #773)

2026-08-26

Scorecard Added

OSSF Scorecard: 5.0/10

2026-08-26

Rank Moved

Rank rose 318 spots (#1069 → #751)

2026-08-26

HVTrust Changed

HVTrust up 19.1pts (20.2 → 39.3)

2026-08-17

Rank Moved

Rank rose 17 spots (#1090 → #1073)

2026-08-15

Rank Moved

Rank rose 17 spots (#1102 → #1085)

GitHub → npm: mcp-sqlite-tools

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mcp-sqlite-tools.svg)](https://hvtracker.net/agents/mcp-sqlite-tools)
            
HTML:
            <a href="https://hvtracker.net/agents/mcp-sqlite-tools"><img src="https://hvtracker.net/badge/mcp-sqlite-tools.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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

MCP Sqlite Tools

How MCP Sqlite Tools could raise its score

Chain of custody

Source Signed

Review and release Mixed

Published packages Not linked

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How MCP Sqlite Tools compares in MCP Servers

Where the 59.1 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about MCP Sqlite Tools

AI agent surface

Maintain MCP Sqlite Tools?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers