# knock (pypi · knock-mcp)

Code map and memory for AI coding agents: key functions, line ranges, callers, why code changed.

- Trust score: 35/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `knock-mcp`: 35/100 (this document), [markdown](https://verifymcp.io/servers/hasangilani-knock/knock-mcp.md), [page](https://verifymcp.io/servers/hasangilani-knock/knock-mcp)

## Channel facts

- Registry: `pypi`
- Package: `knock-mcp`
- Version: `0.2.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-11-05.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it.
  - 1 of 29 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to HasanGilani/knock).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 1 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.

**Unverified: 5 categories.** Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you.

## Install

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

knock runs locally as a PyPI package, launched with uvx knock-mcp serve --repo . --toolset map. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add hasangilani-knock -- uvx knock-mcp serve --repo . --toolset map
```

### Cursor

```json
{
  "mcpServers": {
    "hasangilani-knock": {
      "command": "uvx",
      "args": [
        "knock-mcp",
        "serve",
        "--repo",
        ".",
        "--toolset",
        "map"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "hasangilani-knock": {
      "command": "uvx",
      "args": [
        "knock-mcp",
        "serve",
        "--repo",
        ".",
        "--toolset",
        "map"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add hasangilani-knock -- uvx knock-mcp serve --repo . --toolset map
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hasangilani-knock": {
      "type": "local",
      "command": [
        "uvx",
        "knock-mcp",
        "serve",
        "--repo",
        ".",
        "--toolset",
        "map"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  hasangilani-knock:
    command: "uvx"
    args: ["knock-mcp", "serve", "--repo", ".", "--toolset", "map"]
```

### Netclaw

```json
{
  "McpServers": {
    "hasangilani-knock": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "knock-mcp",
        "serve",
        "--repo",
        ".",
        "--toolset",
        "map"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "hasangilani-knock": {
      "command": "uvx",
      "args": [
        "knock-mcp",
        "serve",
        "--repo",
        ".",
        "--toolset",
        "map"
      ]
    }
  }
}
```

## 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-11-05 (score 35, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-03 (score 50, +16)

- [security improvement] Malware scan: unverified → pass
- [functional improvement] Security disclosure: unverified → pass
- [functional] Package version: 0.1.1 → 0.2.0

### 2026-11-02 (score 34)

First indexed and scored.

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/hasangilani-knock/knock-mcp#diagnostics

## Score history

- 2026-11-05: 35
- 2026-11-04: 50
- 2026-11-03: 50
- 2026-11-02: 34

## Common questions

### What is the knock MCP server?

knock is an MCP server listed in the public MCP registry as io.github.HasanGilani/knock. Code map and memory for AI coding agents: key functions, line ranges, callers, why code changed. This page covers its PyPI package (knock-mcp).

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

knock scores 35 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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.

### Is the knock MCP server still maintained?

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

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.

### What did VerifyMCP test on the knock MCP server?

VerifyMCP ran 8 checks on knock, covering Known CVEs, Install scripts, Dependency health, Source repository and 4 more. 6 items could not be completed, a gap on our side rather than a finding about knock: Malware scan, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/knock-mcp/
- Socket report: https://socket.dev/pypi/package/knock-mcp
- Repository: https://github.com/HasanGilani/knock
- Changelog RSS feed: https://verifymcp.io/servers/hasangilani-knock/knock-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/hasangilani-knock/knock-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/hasangilani-knock/knock-mcp.json
- HTML version of this page: https://verifymcp.io/servers/hasangilani-knock/knock-mcp