com.iunera/druid-mcp-server
OCI · DOCKER.IO/IUNERA/DRUID-MCP-SERVER:2.0.1
AI-powered MCP server for Apache Druid cluster management and analytic
Available components
Last scanned (50 minutes ago)
Scores higher than 92% of OCI servers
Category Databases
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 66 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 938 tokens (~85/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "queryDruidSql" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 0
- Stability: pass → 0.97 functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
- 15 Oct 26 +3
- Source repository: unverified → pass ▲ security
- Stability: pass → 0.80 functional
- 14 Oct 26 −5
- Provenance: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 13 Oct 26 +1
- Provenance: unverified → fail ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Analysed oci/docker.io/iunera/druid-mcp-server:2.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
getCompactionConfig ~77
View compaction configuration or configuration change history for datasources. Parameters: [datasource] (String, optional), and [includeHistory] (Boolean, optional) to retrieve configuration history.
| Name | Type | Req | Description |
|---|---|---|---|
| datasource | string | – | Name of the datasource (optional) |
| includeHistory | boolean | – | Whether to retrieve configuration change history (optional) |
No output schema declared.
No examples provided.
getCompactionStatus ~48
Retrieve the current status of compaction runs and progress. Parameters: [datasource] (String, optional).
| Name | Type | Req | Description |
|---|---|---|---|
| datasource | string | – | Name of the datasource to filter by (optional) |
No output schema declared.
No examples provided.
getDatasources ~98
List all available Apache Druid datasources or get detailed information for a specific datasource. Parameters: [datasourceName] (String, optional) to fetch details for a single datasource, and [detailed] (Boolean, optional) to include schema and column specifications.
| Name | Type | Req | Description |
|---|---|---|---|
| datasourceName | string | – | Name of the datasource to get details for (optional) |
| detailed | boolean | – | Whether to include detailed columns and data types (optional) |
No output schema declared.
No examples provided.
getLookups ~114
Get configuration or status of lookups for all or a specific tier. Parameters: [tier] (String, optional), [lookupName] (String, optional) to fetch a specific lookup, and [includeStatus] (Boolean, optional) to fetch lookup propagation status instead of configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| includeStatus | boolean | – | Whether to fetch lookup propagation status instead of configuration (optional) |
| lookupName | string | – | Name of the lookup (optional) |
| tier | string | – | Name of the lookup tier (optional) |
No output schema declared.
No examples provided.
getRetentionRules ~97
Retrieve retention rules or audit history for a specific datasource or all datasources. Parameters: [datasource] (String, optional) to filter by a specific datasource, and [includeHistory] (Boolean, optional) to fetch change history instead of current rules.
| Name | Type | Req | Description |
|---|---|---|---|
| datasource | string | – | Name of the datasource (optional/required for history) |
| includeHistory | boolean | – | Whether to fetch change history instead of current rules (optional) |
No output schema declared.
No examples provided.
getSegmentLoadQueue ~58
Get the load queue status showing segments currently being loaded. Parameters: [serverName] (String, optional) to filter by a specific server.
| Name | Type | Req | Description |
|---|---|---|---|
| serverName | string | – | Name of the server to get load queue for (optional) |
No output schema declared.
No examples provided.
getSegments ~135
Fetch segments for all or specific datasources, or get details for a single segment. Parameters: [datasource] (String, optional), [segmentId] (String, optional), [detailed] (Boolean, optional), [metadataOnly] (Boolean, optional) to restrict retrieval to core segment metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| datasource | string | – | Name of the datasource (optional) |
| detailed | boolean | – | Whether to include full segment details/metadata (optional) |
| metadataOnly | boolean | – | Whether to only fetch segment metadata from system tables (optional) |
| segmentId | string | – | ID of the specific segment (optional) |
No output schema declared.
No examples provided.
getSupervisors ~56
List all supervisors or query details of a specific supervisor. Parameters: [supervisorId] (String, optional) to get status details for a single supervisor.
| Name | Type | Req | Description |
|---|---|---|---|
| supervisorId | string | – | ID of the supervisor (optional) |
No output schema declared.
No examples provided.
getTaskDetails ~138
Fetch detailed information, specifications, execution reports, or execution logs for a task. Parameters: [taskId] (String, required), [aspect] (Enum: STATUS, RAW_DETAILS, SPEC, REPORTS, LOG, required), and [logOffset] (Long, optional) to begin reading task logs from a specific byte offset.
| Name | Type | Req | Description |
|---|---|---|---|
| aspect | string | yes | Aspect to retrieve: STATUS, RAW_DETAILS, SPEC, REPORTS, LOG (required) |
| logOffset | integer | – | Byte offset to start reading task logs (optional, used with aspect=LOG) |
| taskId | string | yes | ID of the task (required) |
No output schema declared.
No examples provided.
getTasks ~62
List ingestion tasks matching specific states. Parameters: [state] (Enum: RUNNING, PENDING, WAITING, COMPLETED, optional).
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | – | Task state to list: RUNNING, PENDING, WAITING, COMPLETED (optional) |
No output schema declared.
No examples provided.
queryDruidSql ~55
Execute a SQL query against Druid datasources. Provide the SQL query as a parameter. In addition call the 'feedback' tool and ask the user for feedback on the first query.
| Name | Type | Req | Description |
|---|---|---|---|
| sqlQuery | string | yes | – |
No output schema declared.
No examples provided.
How do I install the com.iunera/druid-mcp-server server?
com.iunera/druid-mcp-server runs locally as a container image, launched with docker run --rm -i -e DRUID_ROUTER_URL -e DRUID_COORDINATOR_URL -e DRUID_AUTH_USERNAME -e DRUID_AUTH_PASSWORD -e DRUID_SSL_ENABLED -e DRUID_SSL_SKIP_VERIFICATION docker.io/iunera/druid-mcp-server:2.0.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · docker.io/iunera/druid-mcp-server:2.0.1
claude mcp add com-iunera-druid-mcp-server -- docker run --rm -i -e DRUID_ROUTER_URL -e DRUID_COORDINATOR_URL -e DRUID_AUTH_USERNAME -e DRUID_AUTH_PASSWORD -e DRUID_SSL_ENABLED -e DRUID_SSL_SKIP_VERIFICATION docker.io/iunera/druid-mcp-server:2.0.1
This image reads DRUID_ROUTER_URL, DRUID_COORDINATOR_URL, DRUID_AUTH_USERNAME, DRUID_AUTH_PASSWORD, DRUID_SSL_ENABLED and DRUID_SSL_SKIP_VERIFICATION. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the com.iunera/druid-mcp-server server?
com.iunera/druid-mcp-server is listed in the public MCP registry as com.iunera/druid-mcp-server. AI-powered MCP server for Apache Druid cluster management and analytic. This page covers its container image (docker.io/iunera/druid-mcp-server:2.0.1).
Is the com.iunera/druid-mcp-server server safe to use?
com.iunera/druid-mcp-server scores 54 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.iunera/druid-mcp-server server expose?
com.iunera/druid-mcp-server exposes 11 tools: getCompactionConfig, getCompactionStatus, getDatasources, getLookups, queryDruidSql, and 6 more. Their descriptions and schemas cost roughly 938 tokens of context every time the server is loaded.
Is the com.iunera/druid-mcp-server server still maintained?
com.iunera/druid-mcp-server is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.iunera/druid-mcp-server server under?
com.iunera/druid-mcp-server declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the com.iunera/druid-mcp-server server?
VerifyMCP ran 12 checks on com.iunera/druid-mcp-server, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about com.iunera/druid-mcp-server: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.