Nofax
NPM · NOFAX · SCANNED SEP 21
Human-in-the-loop approvals and notifications for AI coding agents through a local stdio MCP server.
Available components
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. How we score → Why this is hard to score →
Supply Chain Security63
- No malware found by supply-chain analysis.Pass
- Known CVEs could not be checked: the version this server declares is not published in its registry.Unverified
- No install/post-install scripts declared.Pass
- Dependency health could not be checked: the version this server declares is not published in its registry.Unverified
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to AKzar1el/nofax). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 580 tokens (~82/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
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.
npm · nofax
claude mcp add akzar1el-nofax -- npx -y nofax
{
"mcpServers": {
"akzar1el-nofax": {
"command": "npx",
"args": [
"-y",
"nofax"
]
}
}
} {
"servers": {
"akzar1el-nofax": {
"command": "npx",
"args": [
"-y",
"nofax"
]
}
}
} codex mcp add akzar1el-nofax -- npx -y nofax
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"akzar1el-nofax": {
"type": "local",
"command": [
"npx",
"-y",
"nofax"
],
"enabled": true
}
}
} openclaw mcp add akzar1el-nofax --command npx --arg -y --arg nofax
mcp_servers:
akzar1el-nofax:
command: "npx"
args: ["-y", "nofax"] {
"McpServers": {
"akzar1el-nofax": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"nofax"
]
}
}
} assistant mcp add akzar1el-nofax -t stdio -c npx -a -y nofax
{
"mcpServers": {
"akzar1el-nofax": {
"command": "npx",
"args": [
"-y",
"nofax"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 68
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed npm/nofax@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | AKzar1el/nofax |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/AKzar1el/nofax/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 2904928857 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b1ca32604ea59929e5e1de2f73cf238e4e817df1cb7b318b842ae5fa51f7f73337841f8cac67b998356b00e78cae905b1444c7668e750230b94dc0575 |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
nofax_get_request Get Nofax request ~39
Recover safe metadata and terminal state for a durable Nofax request. Secret response topics are never returned.
| Name | Type | Req | Description |
|---|---|---|---|
| requestId | string | yes | – |
No output schema declared.
No examples provided.
nofax_list_pending List pending Nofax requests ~43
List a bounded set of unresolved Nofax request handles for recovery after client or conversation interruption. Secret response topics are never returned.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
nofax_notify Send Nofax notification ~43
Send a one-way phone notification. This tool is informational and does not create a human-response wait.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
| title | string | – | – |
No output schema declared.
No examples provided.
nofax_request_approval Request human approval ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| allowRefine | boolean | – | – |
| message | string | yes | – |
| title | string | – | – |
No output schema declared.
No examples provided.
nofax_request_choice Request human choice ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
| options | array | yes | – |
| title | string | – | – |
No output schema declared.
No examples provided.
nofax_request_refinement Request human refinement ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
| title | string | – | – |
No output schema declared.
No examples provided.
nofax_wait_for_response Wait for Nofax human response ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| requestId | string | yes | – |
| waitSeconds | integer | – | – |
No output schema declared.
No examples provided.
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.