Is Druid MCP Server safe to use?

Druid MCP Server has an HVTrust score of 48.0/100 (Grade D), ranked #1064 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Druid MCP Server?

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

Druid MCP Server

Repository

Website

A comprehensive Model Context Protocol (MCP) server for Apache Druid that provides extensive tools, resources, and AI-assisted prompts for managing and analyzing Druid clusters. Built with Spring Boot and Spring AI, this server enables seamless integration between AI assistants and Apache Druid…

MCP Servers Java Listed Apache-2.0

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

OSSF Scorecard 2.5 / 10

Provenance None

Signed commits 30%

Last push 8d ago

Compare Druid MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Druid MCP Server scores 48.0/100 (Grade D), ranked #1064 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 2.5/10; 30% of recent commits are signed; last pushed 2026-11-02. Every point is earned from checkable signals — never paid placement. How scoring works →

How Druid 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 2.5 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +13.7 → 61.7 C · #360 of 778
Sign every commit30% signed today +3.5 → 51.5 C · #540 of 778

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Druid MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Partly signed

github.com/iunera/druid-mcp-server, Apache-2.0, last pushed 2026-11-02. 30% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Weak

OpenSSF Scorecard rates the repository's practices 2.5/10 (scanned Nov 8, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 4

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0
Published packages None

Distributed as the container image docker.io/iunera/druid-mcp-server:2.0.0; HVTracker doesn't check that registry's source link yet.

Changes to this chain

2026-08-29 OSSF Scorecard: 3.3/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 Druid 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.

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 Druid MCP Server compares in MCP Servers

#598 Jotform MCP Server 48.2 +0.2
#599 MCP Unity 48.1 +0.1
#600 Druid MCP Server 48.0 this agent
#601 Obsidian Vault MCP Server 48.0 ±0
#602 Ryaker Appstore Connect MCP 48.0 ±0

Bars show each HVTrust score; the tick marks Druid MCP Server’s 48.0.

Where the 48.0 comes from

HVTrust dimensions vs the MCP Servers average

48.0 / 100 · 100.0% confidence

Druid MCP Server MCP Servers average (778 agents)

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

4.6 / 25

6.2 below 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

10.6 / 17

1.7 below avg 12.3

Maintenance60% last-push freshness · 40% commit activity

11.5 / 20

0.7 below avg 12.2

AdoptionLog-scaled stars · package downloads

8.5 / 20

0.9 above avg 7.6

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-11-08

Rank Moved

Rank dropped 12 spots (#1053 → #1065)

2026-11-03

Rank Moved

Rank rose 88 spots (#1133 → #1045)

2026-11-03

HVTrust Changed

HVTrust up 4.1pts (44.8 → 48.9)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.5/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 View MCP Servers Report missing data

35.9

Activity sub-score · out of 100

#600

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 D 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-02

8 days ago

Commits (4 wk)

Downloads (7d)

12,336

docker

HN mentions (30d)

—

Open Issues

Rank Change

▲6

was #1070

Analysis

Activity Inputs

35.9 / 100

StarsRepository reach

7.7 / 30

FreshnessLast push recency

23.9 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

4.2 / 20

Common questions about Druid MCP Server

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

No published build provenance is currently detected for Druid MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Druid MCP Server have an OpenSSF Scorecard?

Druid MCP Server has an OpenSSF Scorecard score of 2.5/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 Druid MCP Server actively maintained?

Maintained. Last push was 8 days ago.

What license does Druid MCP Server use?

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

Are Druid MCP Server's commits signed?

30% of the last 100 commits to Druid MCP Server 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

Druid MCP Server 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 Druid 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.

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Druid MCP Server?

For maintainers

HVTrust scores Druid 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-11-08

Rank Moved

Rank dropped 12 spots (#1053 → #1065)

2026-11-03

Rank Moved

Rank rose 88 spots (#1133 → #1045)

2026-11-03

HVTrust Changed

HVTrust up 4.1pts (44.8 → 48.9)

2026-11-03

Activity Score Changed

Activity score up 9pts (28 → 37)

2026-10-31

Rank Moved

Rank dropped 39 spots (#1093 → #1132)

2026-10-19

Rank Moved

Rank rose 35 spots (#1110 → #1075)

2026-10-15

Rank Moved

Rank dropped 10 spots (#1094 → #1104)

2026-10-10

Rank Moved

Rank dropped 42 spots (#1033 → #1075)

2026-10-09

Rank Moved

Rank dropped 15 spots (#1018 → #1033)

2026-10-06

Rank Moved

Rank rose 35 spots (#1048 → #1013)

2026-10-03

Rank Moved

Rank dropped 30 spots (#1009 → #1039)

2026-09-30

Rank Moved

Rank dropped 44 spots (#960 → #1004)

2026-09-25

Rank Moved

Rank rose 126 spots (#1081 → #955)

2026-09-25

HVTrust Changed

HVTrust up 5.2pts (44.2 → 49.4)

2026-09-24

Rank Moved

Rank dropped 22 spots (#1059 → #1081)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank rose 68 spots (#1127 → #1059)

2026-09-23

HVTrust Changed

HVTrust up 23.5pts (21.5 → 45.0)

2026-09-22

Newly Listed

First tracked at rank #1127

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank dropped 223 spots (#1062 → #1285)

2026-09-20

HVTrust Changed

HVTrust down 14.4pts (44.7 → 30.3)

2026-09-13

Rank Moved

Rank dropped 15 spots (#1037 → #1052)

2026-09-12

Rank Moved

Rank dropped 11 spots (#1026 → #1037)

2026-09-10

Rank Moved

Rank rose 10 spots (#1029 → #1019)

2026-09-09

Rank Moved

Rank dropped 18 spots (#1011 → #1029)

2026-09-07

Rank Moved

Rank rose 240 spots (#1247 → #1007)

2026-09-07

HVTrust Changed

HVTrust up 14.4pts (31.0 → 45.4)

2026-09-06

Rank Moved

Rank dropped 19 spots (#1228 → #1247)

2026-09-05

Rank Moved

Rank dropped 304 spots (#924 → #1228)

2026-09-05

HVTrust Changed

HVTrust down 14.0pts (45.1 → 31.1)

2026-09-04

Rank Moved

Rank dropped 29 spots (#895 → #924)

2026-09-03

Rank Moved

Rank rose 259 spots (#1154 → #895)

2026-09-03

HVTrust Changed

HVTrust up 14.3pts (30.8 → 45.1)

2026-09-02

Rank Moved

Rank dropped 375 spots (#779 → #1154)

2026-09-02

HVTrust Changed

HVTrust down 15.0pts (45.8 → 30.8)

2026-09-01

Rank Moved

Rank dropped 34 spots (#745 → #779)

2026-08-31

Rank Moved

Rank rose 100 spots (#845 → #745)

2026-08-31

HVTrust Changed

HVTrust up 5.3pts (40.6 → 45.9)

2026-08-31

Activity Score Changed

Activity score up 12pts (28 → 40)

2026-08-30

Rank Moved

Rank dropped 35 spots (#810 → #845)

2026-08-29

Scorecard Added

OSSF Scorecard: 3.3/10

2026-08-29

Rank Moved

Rank rose 422 spots (#1232 → #810)

2026-08-29

HVTrust Changed

HVTrust up 22.8pts (17.9 → 40.7)

2026-08-28

Rank Moved

Rank dropped 11 spots (#1221 → #1232)

2026-08-27

Rank Moved

Rank dropped 13 spots (#1208 → #1221)

2026-08-26

Rank Moved

Rank dropped 39 spots (#1169 → #1208)

2026-08-16

Rank Moved

Rank dropped 25 spots (#1138 → #1163)

GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/druid-mcp-server.svg)](https://hvtracker.net/agents/druid-mcp-server)
            
HTML:
            <a href="https://hvtracker.net/agents/druid-mcp-server"><img src="https://hvtracker.net/badge/druid-mcp-server.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.4 · Raw JSON

Druid MCP Server

How Druid MCP Server could raise its score

Chain of custody

Source Partly signed

Review and release Weak

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Druid MCP Server compares in MCP Servers

Where the 48.0 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Druid MCP Server

AI agent surface

Maintain Druid MCP Server?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers