Skills/npm/netsapiens-mcp

netsapiens-mcp@3.1.0

VERIFIED· not started

Publisher claims: "MCP server for the NetSapiens API: per-user sign-in, role-aware tools, version-aware availability" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher phoneware · publishing for 370 daysInstalls 16,395Last detonated 21 min ago
$claude mcp add netsapiens-mcp -- npx -y netsapiens-mcp
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
FIRESTORE_AUTH_CODES_COLLECTIONFIRESTORE_RESUME_TOKENS_COLLECTIONMCP_SESSION_SECRETMCP_TOKEN_LIFETIME_HOURSMCP_TOKEN_STORE_PATHNETSAPIENS_API_TOKENNETSAPIENS_AUTH_MODENETSAPIENS_OAUTH_CLIENT_IDNETSAPIENS_OAUTH_CLIENT_SECRETNETSAPIENS_OAUTH_PASSWORDNETSAPIENS_OAUTH_USERNAMEConfiguration, not credentials: GOOGLE_CLOUD_PROJECT, MCP_BASE_URL, MCP_CONFIRM_DESTRUCTIVE, MCP_CONFIRM_FALLBACK, MCP_CORS_ORIGIN, MCP_DISABLE_DESTRUCTIVE, MCP_DISABLE_ROLE_FILTER, MCP_DISABLED_ACTIONS, MCP_DISABLED_TOOLS, MCP_HOST, MCP_ICON_URL, MCP_PERSISTENCE, MCP_PLATFORMS, MCP_PORT, MCP_READ_ONLY, MCP_SERVER_TITLE, MCP_STATELESS, MCP_STORE_NAMESPACE, MCP_STORE_PATH, MCP_SYNCHRONOUS_WRITES, MCP_TOOL_MODE, MCP_TOOLS_PAGE_SIZE, MCP_TRANSPORT, MCP_WEBSITE_URL, NETSAPIENS_API_URL, NETSAPIENS_PLATFORMS, NETSAPIENS_VERSION_TTL_SECONDS, V2_BASE_PATH
Where it talks to
no vendor host named in the code
What we saw when it ran
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. It asks for FIRESTORE_AUTH_CODES_COLLECTION, FIRESTORE_RESUME_TOKENS_COLLECTION, MCP_SESSION_SECRET, MCP_TOKEN_LIFETIME_HOURS, MCP_TOKEN_STORE_PATH, NETSAPIENS_API_TOKEN, NETSAPIENS_AUTH_MODE, NETSAPIENS_OAUTH_CLIENT_ID, NETSAPIENS_OAUTH_CLIENT_SECRET, NETSAPIENS_OAUTH_PASSWORD, NETSAPIENS_OAUTH_USERNAME and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --net declared -- npx -y netsapiens-mcp

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

Static findings

MEDIUM
MCP server using network transport (SSE/HTTP)build/config/env.js:30 · MCP server using network transport (SSE/HTTP) — data sent over network{ name: 'MCP_SERVER_TITLE', transports: ['http', 'stdio'], required: false, default: null, effect: 'Server title.' },Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
File permission modification commandbuild/store/sqlite.js:110 · File permission modification command — agent changes file ownership/permissionsthrow new StoreConfigError(`${path} is readable by other users; chmod 600 ${path}`);Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05

Cost to the agent

Instructions loaded
≈61 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.