Act for a person on websites: sandboxed browser, phone approvals, saved logins, scheduled plans.
Nothing to run from here
node9 is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
94/100
trust score
382
downloads a day
local
runs on your machine
10k
downloads in 30d
What it does
Access control for AI agents and MCP servers: allow, hold for approval, or block each tool call
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user node9-mcp '--' npx -y node9-ai mcp-server
# 2 — ask your agent for something these tools do
# node9_status, node9_config_get, node9_shield_list and 15 more
node9 costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
NAAll 1 server
node9-ai1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts node9 as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user node9-mcp '--' npx -y node9-ai mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
18 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Show the current node9 protection status: mode, daemon state, pause state,
No parameter schema on file.
Read the current node9 configuration: security mode, approver channels, timeouts,
No parameter schema on file.
List all available node9 shields and which ones are currently active.
No parameter schema on file.
Enable a node9 shield for a specific service. Shields only add protection — they cannot
No parameter schema on file.
Disable a node9 shield. WEAKENING action — refused over MCP by default (a human must run
No parameter schema on file.
List all node9 approver channels and their current enabled/disabled state.
No parameter schema on file.
Enable or disable a specific node9 approver channel in the global config (~/.node9/config.json).
No parameter schema on file.
Read recent entries from the node9 audit log (~/.node9/audit.log). Each entry shows
No parameter schema on file.
Show all active smart rules in detail — name, tool, verdict, conditions, and reason.
No parameter schema on file.
Scan all AI agent history (Claude + Gemini) and report what node9 would have blocked or
No parameter schema on file.
Show an activity and security report: tool call counts, blocks, DLP findings, agent cost,
No parameter schema on file.
List recent AI agent sessions with per-session summaries: tool calls, cost, modified files,
No parameter schema on file.
Run the node9 security posture scorecard for the agent on this host — grades how exposed
No parameter schema on file.
Preview exactly how node9 would evaluate a tool call BEFORE running it — the full
No parameter schema on file.
Add a new protective smart rule to the global node9 config (~/.node9/config.json).
No parameter schema on file.
Show egress (outbound network) control: whether it is enabled, the mode
No parameter schema on file.
Turn on egress control (or strengthen it). mode="review" prompts on unknown hosts;
No parameter schema on file.
Add a host to the egress deny list (deny always wins over allow). Only adds
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install node9 or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 94 / 100
Release 2.27.0 · scanned 6 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score94
Findings1 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digestdb27cad4b6132cecf24f8a3dae52e83b338ac4e51cb2d0df13111358e88e17a8
Score vectorthreat 100 → client 94
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can execute shell commands or code
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestdb27cad4b6132cec
Scanned2026-10-06
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 2.27.0. Pin a release below and the command asks for exactly that one.
2.27.0
4 Oct 2026
latestNo release note was published with this version.
2.26.2
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish node9 can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.