Druid MCP Server

A comprehensive Model Context Protocol (MCP) server for Apache Druid that provides extensive tools, resources, and AI-as

MCP Servers Java Grade D Listed Apache-2.0
45.0/100
Rank #912 of 1320
Compare Druid MCP Server

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-31 · 4d ago
Recent change
Rank +13

Is Druid MCP Server safe? Druid MCP Server scores 45.0/100 (Grade D), ranked #912 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.3/10; 30% of recent commits are signed; last pushed 2026-08-31. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-04
Rank Moved
Rank dropped 17 spots (#895 → #912)
2026-09-03
Rank Moved
Rank rose 259 spots (#1154 → #895)
2026-09-03
HVTrust Changed
HVTrust up 14.3pts (30.8 → 45.1)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.3/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.
40.1
Activity sub-score · out of 100
#497

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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-04 14:03 UTC · Repo last pushed 4 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
17
Forks
7
Last Push
2026-08-31
4 days ago
Commits (4 wk)
1?
Downloads (7d)
HN mentions (30d)
Open Issues
0
Rank Change
▼17
was #895

Analysis

HVTrust Dimensions vs MCP Servers

45.0 / 100 · 100.0% confidence

Druid MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.6 / 25
3.9 below avg 9.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
11.3 / 17
in line with avg 11.8
Maintenance60% last-push freshness · 40% commit activity
12.3 / 20
in line with avg 12.2
AdoptionLog-scaled stars · package downloads
3.0 / 20
3.2 below avg 6.2

Activity Inputs

40.1 / 100
StarsRepository reach
7.5 / 30
FreshnessLast push recency
24.4 / 25
ActivityRecent commits
3.8 / 25
CommunityFork signal
4.2 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.3 / 10
OpenSSF Scorecard · scanned Aug 29, 2026
Signed Commits
30%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 9
CII-Best-Practices 0
Code-Review 0
Contributors 3
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 1
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 8

Is Druid MCP Server safe?

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 3.3/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?
Actively maintained. The repository was pushed to within the last 4 day(s).
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

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.

Reputation Timeline

Signal history
Rank 12HVTrust 4Listed 1Scorecard 1Score 1
2026-09-04
Rank Moved
Rank dropped 17 spots (#895 → #912)
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)
2026-08-10
Rank Moved
Rank dropped 67 spots (#1065 → #1132)
2026-08-08
Newly Listed
First tracked at rank #1063

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 45.0 Grade D
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.3 · Raw JSON