# three.ws Knock (npm · @three-ws/knock-mcp)

Reach a real person: quote their door, browse who is reachable, knock, and read the reply.

- Trust score: 76/100 (medium)
- Change this week: −2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- npm · `@three-ws/knock-mcp`: 76/100 (this document), [markdown](https://verifymcp.io/servers/nirholas-knock-mcp/three-ws-knock-mcp.md), [page](https://verifymcp.io/servers/nirholas-knock-mcp/three-ws-knock-mcp)

## Channel facts

- Registry: `npm`
- Package: `@three-ws/knock-mcp`
- Version: `0.1.0`
- 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-25.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 43 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1112 tokens (~185/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the three.ws Knock MCP server?

three.ws Knock runs locally as an npm package, launched with npx -y @three-ws/knock-mcp. 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 nirholas-knock-mcp -- npx -y @three-ws/knock-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "nirholas-knock-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@three-ws/knock-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "nirholas-knock-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@three-ws/knock-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add nirholas-knock-mcp -- npx -y @three-ws/knock-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add nirholas-knock-mcp --command npx --arg -y --arg @three-ws/knock-mcp
```

### Hermes

```yaml
mcp_servers:
  nirholas-knock-mcp:
    command: "npx"
    args: ["-y", "@three-ws/knock-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "nirholas-knock-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@three-ws/knock-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add nirholas-knock-mcp -t stdio -c npx -a -y @three-ws/knock-mcp
```

### Other

```json
{
  "mcpServers": {
    "nirholas-knock-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@three-ws/knock-mcp"
      ]
    }
  }
}
```

## 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-10-24 (score 76, −4)

- [security regression] CVE-2023-54404 affects this package: high
- [security regression] Known CVEs: pass → fail

### 2026-10-22 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-18 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-16 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-13 (score 75, +6)

- [functional improvement] Stability: unverified → 0.43

### 2026-10-01 (score 69, +15)

- [security improvement] Malware scan: unverified → pass

## MCP tools (6)

### `knock_quote` (~124 tokens)

Quote a door

Read one person's public door on three.ws: the price of a single message to them, which chains they take it on, how long the message may be, what they say they want to hear about, and the exact endpoint to use. Costs nothing and needs no credential. ALWAYS call this before knock_send on a priced door: the owner can change their price at any time, and the quote you show a human before they approve a payment must be the live one. Read-only.

Input parameters:

- `handle` (string, required): The recipient's three.ws username, with or without the @.

### `knock_directory` (~81 tokens)

Browse open doors

List every open, listed door on three.ws, cheapest first: who is reachable, for how much, and what they say they want to be reached about. This is how an agent discovers which humans it can pay to talk to. Costs nothing and needs no credential. Read-only.

Input parameters:

- `limit` (integer): How many doors to return. Default 60.

### `knock_send` (~293 tokens)

Knock on a door

Send exactly one message to a person through their three.ws door. The message lands in their inbox AND their 3D companion walks on screen wherever they are on the site and delivers it out loud, naming you and what you paid. On a FREE door this sends immediately. On a PRICED door this tool does not pay and cannot pay: it returns `payment_required` together with the recipient, the amount, the token, the chain and the endpoint, so a human can approve the spend and pay from their own wallet (npx @three-ws/knock, or any x402 client). Pass `request_id` to make retries safe: the same id never knocks, or charges, twice. Refusals (shut door, daily cap, message too long) happen before any payment, so a rejected knock is never a paid one.

Input parameters:

- `from` (string, required): Who is knocking. Shown to them and spoken out loud.
- `message` (string, required): The message. Shown in full, never read aloud.
- `request_id` (string): Idempotency key. A retry returns the first knock instead of knocking twice.
- `subject` (string): One line their companion says out loud. Make it the reason you are knocking.
- `to` (string, required): Recipient username, with or without the @.
- `url` (string): An http(s) link about you.

### `knock_receipt` (~102 tokens)

Read a knock receipt

Read the state of a knock you sent, using the receipt_url it returned. Statuses: pending (not opened), read (opened, no answer written), replied (they wrote back, and the reply is included), dismissed (read and closed). The receipt carries its own proof, so this needs no account and reveals nothing about the recipient beyond the reply they chose to write. Read-only.

Input parameters:

- `receipt_url` (string, required): The receipt_url a knock returned.

### `knock_inbox` (~122 tokens)

Read your knocks

Read the knocks your own door has taken, newest first, each with what the sender paid for it. Use this to triage: the amount is the sender's own statement of how much reaching you was worth. Also returns totals (waiting, all time, earned). Requires THREE_WS_API_KEY for the account that owns the door; it can never read anyone else's. Read-only.

Input parameters:

- `before` (string): ISO timestamp cursor for paging.
- `limit` (integer): Page size. Default 30.
- `status` (string): Filter to one status.

### `knock_act` (~193 tokens)

Act on a knock

Act on one knock in your own inbox: mark it read, dismiss it, or reply to it. A reply is delivered back through the receipt link the sender already holds, so answering never hands out your email or any other address. Set block to stop hearing from that sender: they are matched on the wallet that paid when there was one, and they see the same answer a shut door gives, so they cannot tell it was them. Acting on a knock also settles its companion delivery, so your avatar will not walk on later to announce something you have already dealt with. Requires THREE_WS_API_KEY.

Input parameters:

- `block` (boolean): Never hear from this sender again.
- `knock_id` (string, required): The knock id from knock_inbox.
- `reply` (string): What to write back. The sender reads it through their receipt link.
- `status` (string): The new status. Use replied together with reply.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/nirholas-knock-mcp/three-ws-knock-mcp#diagnostics

## Score history

- 2026-10-25: 76
- 2026-10-24: 76
- 2026-10-23: 80
- 2026-10-22: 80
- 2026-10-21: 79
- 2026-10-20: 79
- 2026-10-19: 78
- 2026-10-18: 78
- 2026-10-17: 77
- 2026-10-16: 77
- 2026-10-15: 76
- 2026-10-14: 76
- 2026-10-13: 75
- 2026-10-12: 69
- 2026-10-11: 69
- 2026-10-05: 69
- 2026-10-04: 69
- 2026-10-03: 69
- 2026-10-02: 69
- 2026-10-01: 69
- 2026-09-30: 54

## Common questions

### What is the three.ws Knock MCP server?

three.ws Knock is an MCP server listed in the public MCP registry as io.github.nirholas/knock-mcp. Reach a real person: quote their door, browse who is reachable, knock, and read the reply. This page covers its npm package (@three-ws/knock-mcp).

### Is the three.ws Knock MCP server safe to use?

three.ws Knock scores 76 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 25 October 2026. It declares no install or post-install scripts. 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 three.ws Knock MCP server expose?

three.ws Knock exposes 6 tools: knock_quote, knock_directory, knock_send, knock_receipt, knock_inbox, knock_act. Their descriptions and schemas cost roughly 915 tokens of context every time the server is loaded.

### Is the three.ws Knock MCP server still maintained?

three.ws Knock is still listed as active in the MCP registry. We last reached this channel on 25 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 three.ws Knock MCP server under?

three.ws Knock 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/@three-ws/knock-mcp
- Socket report: https://socket.dev/npm/package/@three-ws/knock-mcp
- Repository: https://github.com/nirholas/three.ws
- Website: https://three.ws/knock
- Changelog RSS feed: https://verifymcp.io/servers/nirholas-knock-mcp/three-ws-knock-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/nirholas-knock-mcp/three-ws-knock-mcp.json
- HTML version of this page: https://verifymcp.io/servers/nirholas-knock-mcp/three-ws-knock-mcp