Skills/npm/mcp-server

mcp-server@2.0.149

VERIFIED· install only

Publisher claims: "Velaro MCP server — connect Claude and other AI agents directly to your Velaro account: KB, workflows, bots, conversations, contacts, routing, and more." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher velaro · publishing for 215 daysInstalls 30,386Last detonated 1 h ago
$claude mcp add mcp-server -- npx -y @velaro/mcp-server
WatchReport an issue

Coverage

Bundled scripts ran with no arguments; no agent task scenario for this bundle.
Tested
8 of 76 bundled scripts run with no arguments (the rest were not run: per-bundle cap), with decoy credentials in the environment · every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

What this means for the label: Verified 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
Where it talks to
velaro.com (its own)Also azurewebsites.net, mystore.com — not the publisher's domain; check what for before connecting.
What we saw when it ran
no credential files read · no network
What we could not test
use of the skill by an agent

Connect it under the guard. Bundled scripts ran with no arguments; no agent task scenario for this bundle. The code names no credential variable and talks to velaro.com, its own; the guard pins the network to what the honeypot saw and logs every call.

$vet-skills run --net declared -- npx -y @velaro/mcp-server

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

What changed since 2.0.131

vet-skills diff mcp-server 2.0.131 2.0.149

In the sandbox, this version reached for nothing 2.0.131 did not. Compared from the two recorded runs, not from source.

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-20 and scored it 87/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 1 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.0sprocessbundled script run in the sandbox with no arguments
0.1sprocessbundled script run in the sandbox with no arguments
0.2sprocessbundled script run in the sandbox with no arguments
0.3sprocessbundled script run in the sandbox with no arguments
0.4sprocessbundled script run in the sandbox with no arguments
0.5sprocessbundled script run in the sandbox with no arguments
0.6sprocessbundled script run in the sandbox with no arguments
0.7sprocessbundled script run in the sandbox with no arguments
0.8sprocess8 of 76 bundled scripts run with no arguments (the rest were not run: per-bundle cap)
0.8sprocessscript backend runs setup only
0.8sprocessscript backend runs setup only
0.8sprocessno install scripts to re-run

Static findings

MEDIUM
npx invocation of non-well-known packageupdate-check.js:39 · npx invocation of non-well-known package — may execute untrusted codeif (kind === 'npx') return `${head} Point your MCP client at "npx -y @velaro/mcp-server@latest" and restart it.`;Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packageupdate-check.js:1 · npx invocation of non-well-known package — may execute untrusted code// Update notice for the self-hosted MCP server (npx @velaro/mcp-server). Once a day it asks the npm registryFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packageupdate-check.js:4 · npx invocation of non-well-known package — may execute untrusted code// updates itself in the background. npx cache runs only get the notice (npx reuses its cache until told otherwise).Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
LOW
Unpinned dependencyupdate-check.js:40 · Unpinned dependencyif (kind === 'global') return `${head} Run: npm install -g @velaro/mcp-server@latest, then restart your MCP client.`;Fix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.
AST06
HIGH
Auto-update or dynamic fetch configurationupdate-check.js:6 · Auto-update or dynamic fetch configuration — agent may load new code at runtime// Opt out: VELARO_MCP_NO_UPDATE_CHECK=1 (no check) or VELARO_NO_AUTO_UPDATE=1 (notice only, no install).Fix: Pin versions and sources; vendor anything fetched at install time.
AST06

Cost to the agent

Instructions loaded
≈76 tok
1 file · 81 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

No advisories in OSV for @velaro/mcp-server@2.0.149 as of 40 min ago. This is the package itself, not its dependencies.

mcp-server@2.0.149 safety verdict: Verified (install only) — KillerSkills