updated 2026-10-16 16:07 UTC

MCP Server Motherduck

Repository

Local MCP server for DuckDB and MotherDuck

MCP Servers Python Listed MIT

Is MCP Server Motherduck safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.8 / 10
Provenance None
Signed commits 29%
Last push 9d ago
Advisories None known
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 56.1/100 (Grade C), ranked #804 of 1378 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.8/10; 29% of recent commits are signed; no published advisory affects its latest release (mcp-server-motherduck); last pushed 2026-10-07. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Server Motherduck 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

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

  1. Source Partly signed

    github.com/motherduckdb/mcp-server-motherduck, MIT, last pushed 2026-10-07. 29% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.8/10 (scanned Oct 15, 2026). The checks that decide who can get a change released:

    • Code Review1
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    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 10
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 10

  3. Published packages Not linked

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: mcp-server-motherduck 1.1.0. No published advisory affects it (OSV, checked 2026-10-15).

Changes to this chain

  • 2026-09-09 OSSF Scorecard: 3.1/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 Server Motherduck’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 Server Motherduck compares in MCP Servers

  1. #431 MCP Youtube Transcript 56.2 +0.1
  2. #432 MCP Probe Kit 56.2 +0.1
  3. #433 MCP Server Motherduck 56.1 this agent
  4. #434 Fr24api MCP 56.1 ±0
  5. #435 Ros2 MCP 56.0 −0.1

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

Where the 56.1 comes from

HVTrust dimensions vs the MCP Servers average

56.1 / 100 · 100.0% confidence

MCP Server Motherduck MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.2 / 25
4.3 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
11.7 / 17
0.6 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
14.8 / 20
2.5 above avg 12.3
AdoptionLog-scaled stars · package downloads
11.6 / 20
4.2 above avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-15
Rank Moved
Rank rose 121 spots (#924 → #803)
2026-10-15
HVTrust Changed
HVTrust up 3.6pts (52.5 → 56.1)
2026-10-14
Rank Moved
Rank dropped 10 spots (#914 → #924)
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.
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
59.7
Activity sub-score · out of 100
#433
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 →

Signals refreshed 2026-10-16 16:07 UTC · Repo last pushed 9 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
530
Forks
87
Last Push
2026-10-07
9 days ago
Commits (4 wk)
6
Downloads (7d)
6,204
pypi
HN mentions (30d)
—
Open Issues
0
Rank Change
▼1
was #803

Analysis

Activity Inputs

59.7 / 100
StarsRepository reach
16.4 / 30
FreshnessLast push recency
23.8 / 25
ActivityRecent commits
10.5 / 25
CommunityFork signal
9.0 / 20

Common questions about MCP Server Motherduck

MCP Server Motherduck 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 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.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 MCP Server Motherduck actively maintained?
Maintained. Last push was 9 days ago.
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?
28% 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.
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
Rank 27HVTrust 4Grade 4Score 3Listed 2Scorecard 1Delisted 1MCP 1Surface 1
2026-10-15
Rank Moved
Rank rose 121 spots (#924 → #803)
2026-10-15
HVTrust Changed
HVTrust up 3.6pts (52.5 → 56.1)
2026-10-14
Rank Moved
Rank dropped 10 spots (#914 → #924)
2026-10-13
Rank Moved
Rank dropped 10 spots (#904 → #914)
2026-10-11
Rank Moved
Rank dropped 10 spots (#894 → #904)
2026-10-07
Rank Moved
Rank rose 65 spots (#939 → #874)
2026-10-07
Activity Score Changed
Activity score up 11pts (50 → 61)
2026-10-06
Rank Moved
Rank dropped 15 spots (#924 → #939)
2026-10-01
Rank Moved
Rank rose 19 spots (#936 → #917)
2026-09-30
Rank Moved
Rank dropped 10 spots (#926 → #936)
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
HVTrust 56.1 Grade C
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.4 · Raw JSON