MCP Server for NPM Package Info

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

4/4 tools missing one or more hints — getNpmPackageInfo (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); searchNpmPackage (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ReadFile (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +1 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Descriptions match behaviour

1 tool describes read intent but its handler mutates — getNpmPackageInfo (line 26: execSync(`npm view ${packageName}`, {)

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool handlers catch errors

Only 0/4 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

Shell command execution

4 child_process/subprocess calls in production code — runs shell commands (index.js:26, index.js:80, index.js:106)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.10.2 (high), @modelcontextprotocol/sdk@1.10.2 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Tool description accuracy

getNpmPackageInfo: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.