esmole
NPM · ESMOLE-MCP
Elasticsearch 7.x/8.x with connections managed at runtime by the agent, SSH tunnels, readonly.
Available components
Last scanned (19 hours ago)
Scores higher than 32% of npm 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 34 of 101 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 952 tokens (~95/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage72
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 18% 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; "remove_connection" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 10 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
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 60
First indexed and scored.
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 4 Nov 2026 · Analysed npm/esmole-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 101 packages
| Packages resolved | 101 |
|---|---|
| Stale | 34 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
add_connection ~158
Add a named Elasticsearch connection. scope "global" (default) saves it to the user store; "project" saves it to .esmole.json in the project root. Auth via user/password or apiKey; optional ssh tunnel, readonly flag, scheme and verifyTls.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | – |
| host | string | yes | – |
| name | string | yes | – |
| password | string | – | – |
| port | integer | – | – |
| queryTimeoutMs | integer | – | – |
| readonly | boolean | – | – |
| scheme | string | – | – |
| scope | string | – | – |
| ssh | object | – | – |
| type | string | – | – |
| user | string | – | – |
| verifyTls | boolean | – | – |
No output schema declared.
No examples provided.
es_cluster_health ~36
Cluster health summary (status, node and shard counts). Wraps GET /_cluster/health.
| Name | Type | Req | Description |
|---|---|---|---|
| connection | string | yes | – |
No output schema declared.
No examples provided.
es_get_mapping ~56
Return an index mapping as a flat field:type list (compact, token-cheap). Pass raw=true for the nested ES JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| connection | string | yes | – |
| index | string | yes | – |
| raw | boolean | – | – |
No output schema declared.
No examples provided.
es_list_indices ~46
List indices matching a pattern with health, doc count and store size. Wraps GET /_cat/indices.
| Name | Type | Req | Description |
|---|---|---|---|
| connection | string | yes | – |
| pattern | string | – | – |
No output schema declared.
No examples provided.
es_request ~175
Generic Elasticsearch REST passthrough: any method, any path. Returns {status, body}. A 4xx/5xx answer is returned as an error: "HTTP <status> <type>: <reason>" plus the trimmed body. Use a string body for NDJSON (_bulk, _msearch). On readonly connections only reads pass: GET, HEAD, POST [/<index>]/_search|_msearch|_count|_field_caps|_pit, POST /_search/scroll, DELETE /_pit and /_search/scroll.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | – |
| connection | string | yes | connection name, see list_connections |
| method | string | yes | – |
| params | object | – | – |
| path | string | yes | path from the ES root, e.g. '/idx/_search' |
No output schema declared.
No examples provided.
es_search ~255
Search an index. Wraps POST /{index}/_search. query is the query DSL only; sort, from, search_after, track_total_hits, highlight, script_fields and source (_source) map to the same-named body keys. size defaults to 10; with aggs and no query it is forced to 0. Page with from+size or sort+search_after. Use source to project fields and keep responses small. Returns {status, body}; a 4xx/5xx is an error with the ES root cause.
| Name | Type | Req | Description |
|---|---|---|---|
| aggs | object | – | – |
| connection | string | yes | – |
| from | integer | – | – |
| highlight | object | – | – |
| index | string | yes | index, alias, comma list or wildcard, e.g. logs-*,metrics |
| query | object | – | query DSL only, e.g. {"bool": {...}} |
| script_fields | object | – | – |
| search_after | array | – | sort values of the last hit |
| size | integer | – | – |
| sort | – | – | e.g. [{"@timestamp": "desc"}] |
| source | – | – | _source projection: list of fields or false |
| track_total_hits | – | – | – |
No output schema declared.
No examples provided.
list_connections ~51
List Elasticsearch connections with the layer each comes from: project (.esmole.json, found by walking up from the project dir) or global (user store). Also shows invalid entries and broken files. Secrets are omitted.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
remove_connection ~40
Remove an ES connection by name from the layer it lives in (invalid entries too) and drop its cached client/tunnel.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
test_connection ~34
Verify an ES connection works end to end (including ssh tunnel). Reports server version and latency.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
update_connection ~101
Patch an ES connection by name in the layer it lives in (project or global). Set a field to null to remove it (e.g. "ssh": null); an ssh object is merged field by field, e.g. { "ssh": { "hostKey": "SHA256:..." } }. queryTimeoutMs sets the per-request deadline (null restores the 60 s default).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| patch | object | yes | – |
No output schema declared.
No examples provided.
How do I install the esmole MCP server?
esmole runs locally as an npm package, launched with npx -y esmole-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · esmole-mcp
claude mcp add ed-smartass-esmole-mcp -- npx -y esmole-mcp
What is the esmole MCP server?
esmole is an MCP server listed in the public MCP registry as io.github.ed-smartass/esmole-mcp. Elasticsearch 7.x/8.x with connections managed at runtime by the agent, SSH tunnels, readonly. This page covers its npm package (esmole-mcp).
Is the esmole MCP server safe to use?
esmole scores 64 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. 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 esmole MCP server expose?
esmole exposes 10 tools: list_connections, add_connection, update_connection, remove_connection, test_connection, and 5 more. Their descriptions and schemas cost roughly 952 tokens of context every time the server is loaded.
Is the esmole MCP server still maintained?
esmole is still listed as active in the MCP registry. We last reached this channel on 4 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 esmole MCP server under?
esmole declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.