What are the risks of connecting to npm:flow-nexus?

Prompt-injection / hidden-instruction markup found in package source. Overall trust grade F (55/100).

When was npm:flow-nexus last audited?

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

npm:flow-nexus

Item: npm:flow-nexus
Rating: 55
Author: wmcp.sh

https://www.npmjs.com/package/flow-nexus

55/100 · MCP Trust Grade · checked 1mo ago · MCP 0.1.128

Is the npm:flow-nexus MCP server safe to use?

Independent trust grade F (55/100). Prompt-injection / hidden-instruction markup found in package source. wmcp.sh continuously watches npm:flow-nexus for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.

What it offers — 30 tools · AI & ML

flow-nexus-app-store

auth_status

auth_init

template_list

template_get

template_create_from

app_publish

app_update

app_remove

app_list

app_get

analytics_app_stats

analytics_user_stats

analytics_store_overview

challenge_list

challenge_get

challenge_submit

achievement_list

+12 more tools

Spec / packaging20%100

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

Security (OWASP MCP)30%15

⚠ prompt-injection / hidden-instruction markup in source
⚠ references sensitive file paths / env secrets
uses eval/exec/child_process (review for unsanitized input)
scanned 6 source files

Maintenance / popularity20%83

last published ~9mo ago
131 published versions

Tool hygiene15%40

no TypeScript types
13 runtime deps (heavy)

Transparency / provenance15%100

✓ public repository linked
✓ Proprietary license
2,765 weekly downloads

Findings

FAILMCP01 Prompt-injection / hidden-instruction markup found in package source.

WARNMCP08 References sensitive file paths / environment secrets.

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

Grade another server

We re-grade npm:flow-nexus 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:flow-nexus grade F

Share on X Open card image

https://wmcp.sh/mcp/grade/npm%3Aflow-nexus

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 F](https://wmcp.sh/mcp/grade/npm%3Aflow-nexus/badge.svg)](https://wmcp.sh/mcp/grade/npm%3Aflow-nexus)

HTML

<a href="https://wmcp.sh/mcp/grade/npm%3Aflow-nexus"><img src="https://wmcp.sh/mcp/grade/npm%3Aflow-nexus/badge.svg" alt="MCP Trust Grade F · 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.