# Verfy (pypi · verfy)

Ask before acting: would a command run, is an MCP config risky, what do the receipts say

- Trust score: 69/100 (medium)
- Change this week: −12
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- pypi · `verfy`: 69/100 (this document), [markdown](https://verifymcp.io/servers/verfy-dev-verfy/verfy.md), [page](https://verifymcp.io/servers/verfy-dev-verfy/verfy)

## Channel facts

- Registry: `pypi`
- Package: `verfy`
- Version: `0.26.3`
- 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-21.

- **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.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to verfy-dev/verfy).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 402 tokens (~67/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - 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 Verfy MCP server?

Verfy runs locally as a PyPI package, launched with uvx verfy 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 verfy-dev-verfy -- uvx verfy mcp
```

### Cursor

```json
{
  "mcpServers": {
    "verfy-dev-verfy": {
      "command": "uvx",
      "args": [
        "verfy",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "verfy-dev-verfy": {
      "command": "uvx",
      "args": [
        "verfy",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add verfy-dev-verfy -- uvx verfy mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "verfy-dev-verfy": {
      "type": "local",
      "command": [
        "uvx",
        "verfy",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add verfy-dev-verfy --command uvx --arg verfy --arg mcp
```

### Hermes

```yaml
mcp_servers:
  verfy-dev-verfy:
    command: "uvx"
    args: ["verfy", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "verfy-dev-verfy": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "verfy",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add verfy-dev-verfy -t stdio -c uvx -a verfy mcp
```

### Other

```json
{
  "mcpServers": {
    "verfy-dev-verfy": {
      "command": "uvx",
      "args": [
        "verfy",
        "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-11-20 (score 69, +3)

- [functional improvement] Stability: unverified → 0.23
- [functional] Package version: 0.23.1 → 0.26.3
- [functional] Package version: 0.23.1 → 0.26.2
- [functional] Package version: 0.23.1 → 0.26.1

### 2026-11-18 (score 66, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-17 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-15 (score 66, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-14 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-13 (score 66)

First indexed and scored.

## MCP tools (6)

### `check_line` (~54 tokens)

Check a shell command

Say what Verfy's rules decide for a terminal line before an agent uses it: allow, ask or deny, and which rule decides. The line is only read.

Input parameters:

- `line` (string, required): The line, as written

### `check_tool_call` (~75 tokens)

Check a tool call

Say whether Verfy's rules would allow, ask about or deny a call to a tool with these arguments. Nothing is called.

Input parameters:

- `arguments` (object): The arguments of the call
- `server` (string): The MCP server the tool belongs to, if any
- `tool` (string, required): The tool's name

### `scan_mcp_config` (~89 tokens)

Check an MCP config

Check how the MCP servers in a config are started: packages without a version, a download piped into a shell, plain http, a key written into the file, a privileged container. Give the config's JSON text, or leave it out to check the configs found on this computer. No server is started.

Input parameters:

- `config` (string): The JSON text of an MCP config (optional)

### `scan_tools` (~62 tokens)

Scan tool definitions

Scan MCP tool definitions (a tools/list result) for warning signs such as hidden instructions and odd parameters. Returns a grade and the findings per tool.

Input parameters:

- `server` (string): A name for the server (optional)
- `tools` (array, required): The tool definitions

### `agent_settings` (~36 tokens)

Risky agent settings

List the settings of the coding agents on this computer that weaken them or switch Verfy off, with the fix for each. Reads only.

### `recent_receipts` (~50 tokens)

Latest receipts

Show the latest signed receipts of checked calls (time, verdict, tool and rules; arguments are not stored) and whether the chain verifies.

Input parameters:

- `count` (integer): How many (default 20)

## Diagnostics

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

## Score history

- 2026-11-21: 69
- 2026-11-20: 69
- 2026-11-19: 66
- 2026-11-18: 66
- 2026-11-17: 81
- 2026-11-16: 66
- 2026-11-15: 66
- 2026-11-14: 81
- 2026-11-13: 66

## Common questions

### What is the Verfy MCP server?

Verfy is an MCP server listed in the public MCP registry as io.github.verfy-dev/verfy. Ask before acting: would a command run, is an MCP config risky, what do the receipts say. This page covers its PyPI package (verfy).

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

Verfy scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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.

### What tools does the Verfy MCP server expose?

Verfy exposes 6 tools: check_line, check_tool_call, scan_mcp_config, scan_tools, agent_settings, recent_receipts. Their descriptions and schemas cost roughly 366 tokens of context every time the server is loaded.

### Is the Verfy MCP server still maintained?

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

Verfy declares the MIT 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 Verfy MCP server?

VerifyMCP ran 15 checks on Verfy, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about Verfy: Malware scan. 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/verfy/
- Socket report: https://socket.dev/pypi/package/verfy
- Repository: https://github.com/verfy-dev/verfy
- Website: https://verfy.dev/
- Changelog RSS feed: https://verifymcp.io/servers/verfy-dev-verfy/verfy.xml
- Changelog JSON feed: https://verifymcp.io/servers/verfy-dev-verfy/verfy/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/verfy-dev-verfy/verfy.json
- HTML version of this page: https://verifymcp.io/servers/verfy-dev-verfy/verfy
