Skills/npm/nodit-mcp-server

nodit-mcp-server@1.4.1

VERIFIED

Publisher claims: "nodit-mcp-server" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher noditlabs · publishing for 565 daysInstalls 465Last detonated 3d ago
$claude mcp add nodit-mcp-server -- npx -y @noditlabs/nodit-mcp-server
WatchReport an issue

Coverage

Server started and answered tools/list.
Tested
MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
Not tested
what the tools do when called with real credentials

Before you give it your token

It will ask for
NODIT_API_KEY
Where it talks to
no vendor host named in the codeAlso nodit.io, lambda256.io — 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
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 nodit.io, lambda256.io as well as its own vendor. The guard injects NODIT_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- npx -y @noditlabs/nodit-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) on 2026-11-11 and scored it 90/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 26 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
4.7sprocessdependency install exit 0
25sclaimed11 tools: list_nodit_api_categories, list_nodit_node_apis, list_nodit_data_apis, list_nodit_webhook_apis, list_nodit_aptos_indexer_api_query_root, get_nodit_aptos_indexer_api_spec, call_nodit_aptos_indexer_api, get_nodit_api_spec, call_nodit_api, list_nodit_multichain_apis, call_nodit_multichain_api
25sprocessscript backend runs setup only
25sprocessno install scripts to re-run

Static findings

MEDIUM
File permission modification commandpackage.json:10 · File permission modification command — agent changes file ownership/permissions…#!/usr/bin/env node' | cat - build/index.js > temp && mv temp build/index.js && chmod 755 build/index.js && mkdir -p build/spec && cp -r spec/reference build/spec/ref…Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
HIGH
Destructive file system command detectedbuild/tools/node-apis.js:59 · Destructive file system command detected- All chains use the format \`{chain}-{methodName}\` (e.g., \`ethereum-eth_blocknumber\`, \`polygon-eth_blocknumber\`, \`aptos-getAccount\`).Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05

Cost to the agent

Instructions loaded
≈45 tok
1 file · 81 in bundle
Tool list per prompt
≈1,456 tok
11 tools · 132 per tool
Handshake
706 ms
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 178

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 @noditlabs/nodit-mcp-server@1.4.1 as of 3d ago. This is the package itself, not its dependencies.