Is MCP Server Motherduck safe to use?

MCP Server Motherduck has an HVTrust score of 50.8/100 (Grade C), ranked #919 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Server Motherduck?

MCP Server Motherduck scores 50.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 524 GitHub stars and is categorized under MCP Servers.

MCP Server Motherduck

motherduckdb/mcp-server-motherduck

Local MCP server for DuckDB and MotherDuck

MCP Servers Python Listed MIT

Is MCP Server Motherduck safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.0 / 10

Provenance None

Signed commits 27%

Last push 7d ago

Compare MCP Server Motherduck

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP Server Motherduck scores 50.8/100 (Grade C), ranked #919 of 1325 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 3.0/10; 27% of recent commits are signed; last pushed 2026-09-19. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Server Motherduck compares in MCP Servers

#520 SearXNG HTTP MCP 50.9 +0.1
#521 Serpapi MCP 50.9 +0.1
#522 MCP Server Motherduck 50.8 this agent
#523 ASP.NET Core Debugger — MCP Server for AI Agents 50.7 −0.1
#524 MCP Shodan 50.7 −0.1

Bars show each HVTrust score; the tick marks MCP Server Motherduck’s 50.8.

Where the 50.8 comes from

HVTrust dimensions vs the MCP Servers average

50.8 / 100 · 100.0% confidence

MCP Server Motherduck MCP Servers average (775 agents)

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

5.1 / 25

5.2 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.1 / 17

1.1 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

11.5 / 20

0.6 below avg 12.1

AdoptionLog-scaled stars · package downloads

11.3 / 20

4.1 above 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 12 spots (#906 → #918)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Amazon Bedrock

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintainer Checklist

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

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for MCP Server Motherduck View MCP Servers Report missing data

49.3

Activity sub-score · out of 100

#522

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-08-11 2026-09-26

Activity & Reach

Stars

524

Forks

Last Push

2026-09-19

7 days ago

Commits (4 wk)

Downloads (7d)

3,957

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #918

Analysis

Activity Inputs

49.3 / 100

StarsRepository reach

16.3 / 30

FreshnessLast push recency

24.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

9.0 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.0 / 10

OpenSSF Scorecard · scanned Sep 23, 2026

Signed Commits

27%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 1

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 6

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 3

Common questions about MCP Server Motherduck

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

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

MCP Server Motherduck has an OpenSSF Scorecard score of 3.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 Server Motherduck actively maintained?

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

What license does MCP Server Motherduck use?

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

Are MCP Server Motherduck's commits signed?

27% of the last 100 commits to MCP Server Motherduck 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 Server Motherduck 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.

Amazon Bedrock

Credential signal: API keys or service config markers documented.

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 Server Motherduck'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

Provider Added

Runtime surface grew — new detected provider dependency: Amazon Bedrock

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain MCP Server Motherduck?

For maintainers

HVTrust scores MCP Server Motherduck 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-09-25

Rank Moved

Rank dropped 12 spots (#906 → #918)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Amazon Bedrock

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 147 spots (#1050 → #903)

2026-09-23

HVTrust Changed

HVTrust up 27.4pts (23.6 → 51.0)

2026-09-22

Newly Listed

First tracked at rank #1050

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-19

Grade Changed

Trust grade D → C

2026-09-19

Rank Moved

Rank rose 50 spots (#941 → #891)

2026-09-18

Grade Changed

Trust grade C → D

2026-09-18

Rank Moved

Rank dropped 80 spots (#861 → #941)

2026-09-18

Activity Score Changed

Activity score down 9pts (55 → 46)

2026-09-11

Rank Moved

Rank dropped 13 spots (#828 → #841)

2026-09-09

Scorecard Added

OSSF Scorecard: 3.1/10

2026-09-09

Grade Changed

Trust grade D → C

2026-09-09

Rank Moved

Rank rose 434 spots (#1264 → #830)

2026-09-09

HVTrust Changed

HVTrust up 21.5pts (31.3 → 52.8)

2026-09-08

Rank Moved

Rank dropped 12 spots (#1252 → #1264)

2026-09-07

Rank Moved

Rank dropped 11 spots (#1241 → #1252)

2026-09-06

Rank Moved

Rank dropped 17 spots (#1224 → #1241)

2026-09-05

Rank Moved

Rank dropped 22 spots (#1202 → #1224)

2026-09-04

Rank Moved

Rank rose 103 spots (#1305 → #1202)

2026-09-04

HVTrust Changed

HVTrust up 14.1pts (17.4 → 31.5)

2026-09-02

Rank Moved

Rank dropped 12 spots (#1286 → #1298)

2026-08-30

Rank Moved

Rank dropped 11 spots (#1258 → #1269)

2026-08-29

Rank Moved

Rank dropped 13 spots (#1245 → #1258)

2026-08-28

Rank Moved

Rank dropped 12 spots (#1233 → #1245)

2026-08-26

Rank Moved

Rank dropped 34 spots (#1190 → #1224)

2026-08-19

Rank Moved

Rank rose 39 spots (#1224 → #1185)

2026-08-19

Activity Score Changed

Activity score up 9pts (51 → 60)

2026-08-16

Rank Moved

Rank dropped 26 spots (#1200 → #1226)

2026-08-10

Rank Moved

Rank dropped 69 spots (#1124 → #1193)

2026-08-08

Newly Listed

First tracked at rank #1119

GitHub → PyPI: mcp-server-motherduck

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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