# Nofax (npm · nofax)

Human-in-the-loop approvals and notifications for AI coding agents through a local stdio MCP server.

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- npm · `nofax`: 68/100 (this document), [markdown](https://verifymcp.io/servers/akzar1el-nofax/nofax.md), [page](https://verifymcp.io/servers/akzar1el-nofax/nofax)

## Channel facts

- Registry: `npm`
- Package: `nofax`
- Version: `0.2.1`
- 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-09-21.

- **Supply Chain Security**: 63/100
  - No malware found by supply-chain analysis.
  - Known CVEs could not be checked: the version this server declares is not published in its registry.
  - No install/post-install scripts declared.
  - Dependency health could not be checked: the version this server declares is not published in its registry.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to AKzar1el/nofax).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 580 tokens (~82/item across 7 items; 7 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**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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.
  - All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (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 Nofax MCP server?

Nofax runs locally as an npm package, launched with npx -y nofax. 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 akzar1el-nofax -- npx -y nofax
```

### Cursor

```json
{
  "mcpServers": {
    "akzar1el-nofax": {
      "command": "npx",
      "args": [
        "-y",
        "nofax"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "akzar1el-nofax": {
      "command": "npx",
      "args": [
        "-y",
        "nofax"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add akzar1el-nofax -- npx -y nofax
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add akzar1el-nofax --command npx --arg -y --arg nofax
```

### Hermes

```yaml
mcp_servers:
  akzar1el-nofax:
    command: "npx"
    args: ["-y", "nofax"]
```

### Netclaw

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

### Vellum

```bash
assistant mcp add akzar1el-nofax -t stdio -c npx -a -y nofax
```

### Other

```json
{
  "mcpServers": {
    "akzar1el-nofax": {
      "command": "npx",
      "args": [
        "-y",
        "nofax"
      ]
    }
  }
}
```

## 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-21 (score 68)

First indexed and scored.

## MCP tools (7)

### `nofax_notify` (~43 tokens)

Send Nofax notification

Send a one-way phone notification. This tool is informational and does not create a human-response wait.

Input parameters:

- `message` (string, required)
- `title` (string)

### `nofax_request_approval` (~97 tokens)

Request human approval

Send Allow/Deny to the phone and return a durable pending requestId. IMPORTANT: after this tool returns pending, call nofax_wait_for_response and repeat while it remains pending. Never continue the guarded action without a terminal Allow response. Set allowRefine when the human should also be able to send refinement text.

Input parameters:

- `allowRefine` (boolean)
- `message` (string, required)
- `title` (string)

### `nofax_request_choice` (~70 tokens)

Request human choice

Send up to three explicit options to the phone and return a durable pending requestId. IMPORTANT: call nofax_wait_for_response and repeat while pending; do not choose on the human's behalf.

Input parameters:

- `message` (string, required)
- `options` (array, required)
- `title` (string)

### `nofax_request_refinement` (~64 tokens)

Request human refinement

Ask the human for free-text refinement through the configured Nofax Refine iOS Shortcut. Returns a durable pending requestId. IMPORTANT: call nofax_wait_for_response and repeat while pending.

Input parameters:

- `message` (string, required)
- `title` (string)

### `nofax_wait_for_response` (~89 tokens)

Wait for Nofax human response

Long-poll a durable Nofax request for up to 240 seconds. If the result is pending, you MUST call this tool again with the same requestId. Repeat indefinitely until a terminal response is returned or the user explicitly changes/cancels the goal. Do not continue the guarded action while pending.

Input parameters:

- `requestId` (string, required)
- `waitSeconds` (integer)

### `nofax_get_request` (~39 tokens)

Get Nofax request

Recover safe metadata and terminal state for a durable Nofax request. Secret response topics are never returned.

Input parameters:

- `requestId` (string, required)

### `nofax_list_pending` (~43 tokens)

List pending Nofax requests

List a bounded set of unresolved Nofax request handles for recovery after client or conversation interruption. Secret response topics are never returned.

Input parameters:

- `limit` (integer)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/akzar1el-nofax/nofax#diagnostics

## Score history

- 2026-09-21: 68

## Common questions

### What is the Nofax MCP server?

Nofax is an MCP server listed in the public MCP registry as io.github.AKzar1el/nofax. Human-in-the-loop approvals and notifications for AI coding agents through a local stdio MCP server. This page covers its npm package (nofax).

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

Nofax scores 68 out of 100 on VerifyMCP. 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 Nofax MCP server expose?

Nofax exposes 7 tools: nofax_notify, nofax_request_approval, nofax_request_choice, nofax_request_refinement, nofax_wait_for_response, and 2 more. Their descriptions and schemas cost roughly 445 tokens of context every time the server is loaded.

### Is the Nofax MCP server still maintained?

Nofax is still listed as active in the MCP registry. We last reached this channel on 21 September 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 Nofax MCP server under?

Nofax declares the MIT 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/nofax
- Socket report: https://socket.dev/npm/package/nofax
- Repository: https://github.com/AKzar1el/nofax
- Changelog RSS feed: https://verifymcp.io/servers/akzar1el-nofax/nofax.xml
- Changelog JSON feed: https://verifymcp.io/servers/akzar1el-nofax/nofax.json
- HTML version of this page: https://verifymcp.io/servers/akzar1el-nofax/nofax