Skills/npm/doit-mcp-server

doit-mcp-server@5.0.0

VERIFIED· not started

Publisher claims: "DoiT official MCP Server" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher doitintl · publishing for 550 daysInstalls 14,873Last detonated 21 min ago
$claude mcp add doit-mcp-server -- npx -y @doitintl/doit-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
AUTH_SERVER_URLDOIT_API_KEYConfiguration, not credentials: AVA_TIMEOUT_MS, CLOUDFLOW_TRIGGER_PATH, CUSTOMER_CONTEXT, DOIT_API_BASE, DOIT_CHANNEL_EVENTS, DOIT_CHANNEL_ONLY, DOIT_CHANNEL_POLL_SECONDS, DOIT_CONSOLE_BASE, DOIT_DEBUG_LEVEL, TENANT_ID, VITEST_WORKER_ID
Where it talks to
no vendor host named in the codeAlso doit.com — 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 doit.com as well as its own vendor. The guard injects AUTH_SERVER_URL, DOIT_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.

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

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

What changed since 4.0.0

vet-skills diff doit-mcp-server 4.0.0 5.0.0

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

4.0.0 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only.

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; not started: dependency install failed; the server itself was not observed) on 2026-11-16 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 · 7 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
6.4sprocessdependency 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-MV32Gv/task/home/.npm/_logs/2026-11-16T08_19_40_932Z-debug-0.log
6.4sclaimednot started: dependency install failed (exit 1); the server itself was not observed
6.4sprocessscript backend runs setup only
6.4sprocessno install scripts to re-run

Static findings

MEDIUM
File permission modification commandpackage.json:37 · File permission modification command — agent changes file ownership/permissions"build": "yarn generate:skills && tsc && shx cp src/tools/generated/openapi.json dist/tools/generated/openapi.json && shx chmod +x dist/*.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
MEDIUM
File type combined with upload actiondist/channel/poller.js:127 · File type combined with upload action — agent may exfiltrate local data filesthis.log(`DoiT channel: could not send event: ${describeError(error)}`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07

Cost to the agent

Instructions loaded
≈46 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

Not checked against OSV yet; the weekly check has not reached this version.