Skills/npm/mcp-server

mcp-server@1.31.0

VERIFIED· startup only

Publisher claims: "MCP server for SparkDesk — CRM, project management, time tracking, and finance" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher sparkdesk · publishing for 161 daysInstalls 4,562Last detonated 5d ago
$claude mcp add mcp-server -- npx -y @sparkdesk/mcp-server
WatchReport an issue

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

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
SPARKDESK_API_KEYConfiguration, not credentials: SPARKDESK_API_URL
Where it talks to
sparkdesk.io (its own)Also supabase.co — 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 with a scoped credential, under the guard, and read the third-party hosts first. The code names supabase.co as well as its own vendor. The guard injects SPARKDESK_API_KEY only into requests to sparkdesk.io (and its subdomains) and refuses the rest.

$vet-skills run --secrets SPARKDESK_API_KEY=sparkdesk.io -- npx -y @sparkdesk/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; startup only; authenticated tool behavior not tested) on 2026-11-09 and scored it 93/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 · 25 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
4.4sprocessdependency install exit 0
24sclaimedstartup only: exited (0) before answering · code: 'ERR_MODULE_NOT_FOUND', url: 'file:///tmp/ks-detonate-QZENOY/task/home/work/acme-api/.claude/skills/mcp-server/dist/resources/accounts.js' } Node.js v22.23.4
24sprocessscript backend runs setup only
24sprocessno install scripts to re-run

Static findings

No findings across 3,688 lines in 81 files.

Cost to the agent

Instructions loaded
≈58 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 @sparkdesk/mcp-server@1.31.0 as of 5d ago. This is the package itself, not its dependencies.