# node9 (npm · node9-ai)

Access control for AI agents and MCP servers: allow, hold for approval, or block each tool call

- Trust score: 79/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-03

## Components

- npm · `node9-ai`: 79/100 (this document), [markdown](https://verifymcp.io/servers/node9-ai-node9/node9-ai.md), [page](https://verifymcp.io/servers/node9-ai-node9/node9-ai)

## Channel facts

- Registry: `npm`
- Package: `node9-ai`
- Version: `2.26.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-03.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 95 dependencies flagged as unhealthy (1 deprecated).
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to node9-ai/node9-proxy).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 3 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1707 tokens (~94/item across 18 items; 18 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the node9 MCP server?

node9 runs locally as an npm package, launched with npx -y node9-ai. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add node9-ai-node9 -- npx -y node9-ai
```

### Cursor

```json
{
  "mcpServers": {
    "node9-ai-node9": {
      "command": "npx",
      "args": [
        "-y",
        "node9-ai"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "node9-ai-node9": {
      "command": "npx",
      "args": [
        "-y",
        "node9-ai"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add node9-ai-node9 -- npx -y node9-ai
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "node9-ai-node9": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "node9-ai"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add node9-ai-node9 --command npx --arg -y --arg node9-ai
```

### Hermes

```yaml
mcp_servers:
  node9-ai-node9:
    command: "npx"
    args: ["-y", "node9-ai"]
```

### Netclaw

```json
{
  "McpServers": {
    "node9-ai-node9": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "node9-ai"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add node9-ai-node9 -t stdio -c npx -a -y node9-ai
```

### Other

```json
{
  "mcpServers": {
    "node9-ai-node9": {
      "command": "npx",
      "args": [
        "-y",
        "node9-ai"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-30 (score 79, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-29 (score 64)

First indexed and scored.

## MCP tools (18)

### `node9_status` (~48 tokens)

Show the current node9 protection status: mode, daemon state, pause state, active shields, and whether agent hooks are wired. Use this to understand what protection is active before doing risky work.

### `node9_config_get` (~54 tokens)

Read the current node9 configuration: security mode, approver channels, timeouts, DLP settings, and the number of active smart rules. Returns the merged config (env > cloud > project > global > defaults).

### `node9_shield_list` (~43 tokens)

List all available node9 shields and which ones are currently active. Shields are pre-packaged rule sets for specific services (postgres, aws, github, filesystem).

### `node9_shield_enable` (~75 tokens)

Enable a node9 shield for a specific service. Shields only add protection — they cannot be used to weaken or bypass node9. Use node9_shield_list to see available shield names.

Input parameters:

- `service` (string, required): Shield name to enable (e.g. "postgres", "aws", "github", "filesystem").

### `node9_shield_disable` (~82 tokens)

Disable a node9 shield. WEAKENING action — refused over MCP by default (a human must run "node9 shield disable <name>" from the CLI). Use node9_shield_list to see active shields.

Input parameters:

- `service` (string, required): Shield name to disable (e.g. "postgres", "aws", "github", "filesystem").

### `node9_approver_list` (~67 tokens)

List all node9 approver channels and their current enabled/disabled state. Approvers are the channels through which node9 asks a human to approve risky tool calls. Channels: native (OS popup), browser (web UI), cloud (team policy server), terminal (stdin).

### `node9_approver_set` (~126 tokens)

Enable or disable a specific node9 approver channel in the global config (~/.node9/config.json). Use this to turn individual channels on or off without touching other settings. Channels: native, browser, cloud, terminal. WEAKENING action — refused over MCP by default (a human must run it from the CLI). WARNING: disabling all approvers means node9 cannot prompt for human approval — use with care.

Input parameters:

- `channel` (string, required): Approver channel to configure.
- `enabled` (boolean, required): true to enable the channel, false to disable it.

### `node9_audit_get` (~188 tokens)

Read recent entries from the node9 audit log (~/.node9/audit.log). Each entry shows timestamp, outcome, tool name, the command, and the rule that fired. Outcomes use the same words as the dashboard: Auto-allowed, Approved, Ran, Blocked, Denied (a human refused), Timed out (nobody answered), Would block (shadow mode let it through), Finding, Info. Use this to review what AI actions were taken, especially refused ones.

Input parameters:

- `filter` (string): Filter by outcome. "deny" covers every refusal (rule block, human denial, timeout); "observe" is shadow-mode would-blocks; "block" is an alias for "deny". Omit or use "all" for every entry.
- `limit` (number): Number of recent entries to return (default: 20, max: 100).

### `node9_policy_get` (~54 tokens)

Show all active smart rules in detail — name, tool, verdict, conditions, and reason. Includes default rules, shield rules, and any custom project rules. Use this to understand exactly what is being blocked or reviewed.

### `node9_scan` (~84 tokens)

Scan all AI agent history (Claude + Gemini) and report what node9 would have blocked or flagged. Shows blocked operations, reviewed commands, credential leaks, and agent spend. Use this to audit past activity and find security gaps before they become incidents.

Input parameters:

- `drill_down` (boolean): Show full commands and session IDs for every finding (default: false for a clean summary).

### `node9_report` (~90 tokens)

Show an activity and security report: tool call counts, blocks, DLP findings, agent cost, and daily trends for a chosen period. Covers all AI agents (Claude, Gemini, etc.).

Input parameters:

- `no_tests` (boolean): Exclude test runner calls (npm test, vitest, pytest…) from stats.
- `period` (string): Time period for the report (default: 7d).

### `node9_session` (~70 tokens)

List recent AI agent sessions with per-session summaries: tool calls, cost, modified files, and any blocked operations. Pass a session_id to see the full tool trace for that session.

Input parameters:

- `detail` (string): Session ID to show the full tool trace for. Omit to list all recent sessions.

### `node9_posture` (~85 tokens)

Run the node9 security posture scorecard for the agent on this host — grades how exposed the machine is to a compromised agent across isolation, egress, secrets-on-disk, supply chain, and privilege, with the #1 risk and a concrete fix for each finding. Read-only.

Input parameters:

- `agent` (string): Optional label / policy scope for the agent being graded.

### `node9_explain` (~129 tokens)

Preview exactly how node9 would evaluate a tool call BEFORE running it — the full allow / review / block waterfall and step-by-step policy trace. Use this to self-check a command (e.g. "git push --force") and see whether it would be allowed, sent for human review, or blocked, and why. Read-only — nothing executes.

Input parameters:

- `args` (string): Tool arguments as JSON, or a plain shell command string (e.g. "git push --force").
- `tool` (string): Tool name to evaluate. Defaults to "bash" for plain shell commands.

### `node9_rule_add` (~200 tokens)

Add a new protective smart rule to the global node9 config (~/.node9/config.json). Rules can block or send dangerous commands for human review based on regex conditions. IMPORTANT: only "block" and "review" verdicts are permitted — "allow" rules are never accepted because they would weaken node9 security. Rules can only be added, never removed.

Input parameters:

- `field` (string, required): Field to inspect — "command" for bash, "sql" for database tools.
- `name` (string, required): Unique rule name (e.g. "block-drop-prod-db").
- `pattern` (string, required): Regex pattern to match against the field.
- `reason` (string, required): Human-readable explanation shown when the rule triggers.
- `tool` (string, required): Tool to match — "bash", "*", or a specific tool name.
- `verdict` (string, required): Action to take when the rule matches. Only "block" or "review" are allowed.

### `node9_egress_status` (~129 tokens)

Show egress (outbound network) control: whether it is enabled, the mode (off / review / block), and your allow + deny host lists. Common dev/LLM hosts (github, npm, pypi, anthropic, …) are always allowed by a built-in list. Also reports the SSRF floor: the addresses blocked before any policy is consulted (cloud metadata, link-local, multicast), the carriers it covers, whether the strict tier (loopback, private ranges, CGNAT) is on, and the exemptions in force. Read-only.

### `node9_egress_protect` (~105 tokens)

Turn on egress control (or strengthen it). mode="review" prompts on unknown hosts; mode="block" hard-blocks them. Monotonic — it only ever ADDS protection and never reduces it (a request for review will not downgrade an existing block). Only adds protection, so it is always allowed over MCP.

Input parameters:

- `mode` (string): Enforcement to apply. "review" = prompt, "block" = deny. Defaults to review.

### `node9_egress_deny` (~78 tokens)

Add a host to the egress deny list (deny always wins over allow). Only adds protection, so it is always allowed over MCP. Host is an FQDN or wildcard glob (e.g. evil.com or *.evil.com).

Input parameters:

- `host` (string, required): Host to deny (FQDN or *.glob).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/node9-ai-node9/node9-ai#diagnostics

## Score history

- 2026-10-03: 79
- 2026-10-02: 79
- 2026-10-01: 79
- 2026-09-30: 79
- 2026-09-29: 64

## Common questions

### What is the node9 MCP server?

node9 is an MCP server listed in the public MCP registry as io.github.node9-ai/node9. Access control for AI agents and MCP servers: allow, hold for approval, or block each tool call. This page covers its npm package (node9-ai).

### Is the node9 MCP server safe to use?

node9 scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 3 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the node9 MCP server expose?

node9 exposes 18 tools: node9_status, node9_config_get, node9_shield_list, node9_shield_enable, node9_shield_disable, and 13 more. Their descriptions and schemas cost roughly 1,707 tokens of context every time the server is loaded.

### Is the node9 MCP server still maintained?

node9 is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the node9 MCP server under?

node9 declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/node9-ai
- Socket report: https://socket.dev/npm/package/node9-ai
- Repository: https://github.com/node9-ai/node9-proxy
- Website: https://node9.ai/
- Changelog RSS feed: https://verifymcp.io/servers/node9-ai-node9/node9-ai.xml
- Changelog JSON feed: https://verifymcp.io/servers/node9-ai-node9/node9-ai.json
- HTML version of this page: https://verifymcp.io/servers/node9-ai-node9/node9-ai