When was npm:nodejsmcp last audited?

Last checked 2026-06-03; wmcp.sh re-checks it on a schedule for tool drift and rug-pulls.

B-

npm:nodejsmcp

Item: npm:nodejsmcp
Rating: 81
Author: wmcp.sh

https://www.npmjs.com/package/nodejsmcp

81/100 · MCP Trust Grade · checked 1mo ago · MCP 1.0.3

Is the npm:nodejsmcp MCP server safe to use?

Independent trust grade B- (81/100). Static analysis of npm package nodejsmcp@1.0.3 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured. wmcp.sh continuously watches npm:nodejsmcp for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.

What it offers — 6 tools · Developer Tools

echo

Echoes any message passed to it.

login

Logs into a forgejo server and saves the token.

get_user

Gets a user from a forgejo server.

search_issues

Searches for issues in a repository.

list_issues

Lists issues for a repository.

create_issue

Creates an issue in a repository.

Spec / packaging20%100

✓ depends on an MCP SDK
✓ declares a bin entry (runnable server)
✓ 6 tool(s) detected in source

Security (OWASP MCP)30%90

no high-risk patterns in sampled source
scanned 1 source file

Maintenance / popularity20%75

last published ~7mo ago
4 published versions

Tool hygiene15%70

no TypeScript types
5 runtime deps

Transparency / provenance15%55

no repository link
✓ MIT license
31 weekly downloads

Findings

INFO Static analysis of npm package nodejsmcp@1.0.3 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.

Grade another server

We re-grade npm:nodejsmcp on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:nodejsmcp grade B-

Share on X Open card image

https://wmcp.sh/mcp/grade/npm%3Anodejsmcp

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade B-](https://wmcp.sh/mcp/grade/npm%3Anodejsmcp/badge.svg)](https://wmcp.sh/mcp/grade/npm%3Anodejsmcp)

HTML

<a href="https://wmcp.sh/mcp/grade/npm%3Anodejsmcp"><img src="https://wmcp.sh/mcp/grade/npm%3Anodejsmcp/badge.svg" alt="MCP Trust Grade B- · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.