# nofax

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

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.2.43
- **Author:** io.github.AKzar1el
- **License:** MIT
- **npm:** nofax
- **Source:** https://github.com/AKzar1el/nofax
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 14 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-21T10:39:31.609Z
- **Version scanned:** 0.2.1
- **CVEs:** none found by OSV at scan time

## Tools

7 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `nofax_notify` — Send a one-way phone notification. This tool is informational and does not create a human-response wait.
- `nofax_request_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 i
- `nofax_request_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 
- `nofax_request_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_res
- `nofax_wait_for_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 un
- `nofax_get_request` — Recover safe metadata and terminal state for a durable Nofax request. Secret response topics are never returned.
- `nofax_list_pending` — List a bounded set of unresolved Nofax request handles for recovery after client or conversation interruption. Secret response topics are never returned.

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"nofax\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"nofax\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 12, ceiling 30 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/nofax
- Install plan: https://forgeregistry.com/api/v1/packages/nofax/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/nofax
- HTML page: https://forgeregistry.com/registry/nofax
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.