Skills/npm/mcp

mcp@1.0.0-beta6

CAUTION· startup only

Publisher claims: "elastic.io Model Context Protocol (MCP) Server" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher elastic.io · publishing for 45 daysInstalls 2,795Last detonated 3d ago
What would fix thisWatchDispute verdict

Coverage

Startup only; authenticated tool behavior not tested.
Tested
server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
Not tested
the tool list (the server exited before answering) · what the tools do when called with real credentials
Needs
ELASTICIO_API_KEY — give it to the server where it runs, through vet-skills run --secrets, so the value never enters the server's environment. Never paste a credential into a chat, a ticket or a report.

What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
no credential variables read in the code; at startup it asked for ELASTICIO_API_KEY
Where it talks to
no vendor host named in the codeAlso elastic.io, nodejs.org, webhook.site — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
the tool list (the server exited before answering) · what the tools do when called with real credentials

Connect it under the guard. Startup only; authenticated tool behavior not tested. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.

$vet-skills run --net declared -- npx -y @elastic.io/mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-11 and scored it 79/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 58 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
17sprocessdependency install exit 0
37sprocessrelaunched with a decoy ELASTICIO_API_KEY (tagged; nothing real)
57sclaimedstartup only: exited before answering, asking for ELASTICIO_API_KEY (a decoy value was refused)
57sprocessscript backend runs setup only
57sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathsdist/index.js:209 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system fileslogger.error('[Error] Missing elastic.io credentials. For local Stdio mode, please set ELASTICIO_API_EMAIL and ELASTICIO_API_KEY in your environment or .env file.');Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/setup.js:47 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesconst allEnv = { PATH: nodePath, ...env };Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/config.js:5 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesdotenv.config({ path: path.resolve(__dirname, '../.env') });Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/setup.js:33 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesenv: { PATH: nodePath, ...env },Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/api/verification.js:24 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesconst credentials = secret?.credentials || secret?.attributes?.credentials || {};Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/setup.js:42 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files// Remove all existing elasticio sections (main + sub-tables like .env, .tools.*)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Image alt text carrying instructionsREADME.md:27 · Image alt text carrying instructionsWhere to find the curl command on your profile pageFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01
HIGH
Access to sensitive file pathsdist/api/verification.js:37 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesverifyFields = { ...credentials, ...fields };Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/tools/handlers/auth.js:9 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesconst clientCredentials = { ...credentials };Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
npx invocation of non-well-known packagedist/setup.js:7 · npx invocation of non-well-known package — may execute untrusted code// Resolve the full path to npx at setup time so clients that don't inheritFix: Pin versions and sources; vendor anything fetched at install time.
AST06
HIGH
Image alt text carrying instructionsREADME.npm.md:27 · Image alt text carrying instructionsWhere to find the curl command on your profile pageFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01

Cost to the agent

Instructions loaded
≈49 tok
1 file · 81 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for @elastic.io/mcp@1.0.0-beta6 as of 3d ago. This is the package itself, not its dependencies.

What would make this Verified

1 point to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim elastic.io: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Hidden instructions≈ +6 on the totalRemove HTML comments, zero-width characters and white-on-white text that carry instructions. Everything the agent is meant to read should be visible to the person reading the file.
  3. Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
  4. npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
Publish a new version to npm, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim elastic.ioPropose a patch to the maintainer