Skills/npm/mcp-server

mcp-server@4.0.1

VERIFIED· not started

Publisher claims: "MCP server for Sharpe crypto derivatives and market data API" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher sharpe-terminal · publishing for 158 daysInstalls 3,084Last detonated 1 h ago
$claude mcp add mcp-server -- npx -y @sharpe-terminal/mcp-server
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

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
MISSING_API_KEY_MESSAGESHARPE_API_KEYConfiguration, not credentials: MISSING_KEY_MESSAGE, SHARPE_API_URL
Where it talks to
no vendor host named in the codeAlso sharpe.ai — 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
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names sharpe.ai as well as its own vendor. The guard injects MISSING_API_KEY_MESSAGE, SHARPE_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.

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

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; not started: dependency install failed; the server itself was not observed) on 2026-11-15 and scored it 92/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 · 8 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
7.7sprocessdependency install exit 1 · (Use `node --trace-warnings ...` to show where the warning was created) npm error Cannot read properties of null (reading 'edgesOut') npm error A complete log of this run can be found in: /tmp/ks-detonate-poFBcQ/task/home/.npm/_logs/2026-11-15T16_43_12_201Z-debug-0.log
7.7sclaimednot started: dependency install failed (exit 1); the server itself was not observed
7.7sprocessscript backend runs setup only
7.7sprocessno install scripts to re-run

Static findings

MEDIUM
npx invocation of non-well-known packagedist/cli.js:49 · npx invocation of non-well-known package — may execute untrusted code` npx @sharpe-terminal/mcp-server <command> ...`,Fix: Pin versions and sources; vendor anything fetched at install time.
AST06

No other findings across 3,673 lines in 23 files.

Cost to the agent

Instructions loaded
≈54 tok
1 file · 23 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 @sharpe-terminal/mcp-server@4.0.1 as of 43 min ago. This is the package itself, not its dependencies.