# verifyfirst (pypi · verifyfirst-mcp)

Look up what your verification method cannot see: 48 failures that report success.

- Trust score: 80/100 (high trust)
- Change this week: +19
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- pypi · `verifyfirst-mcp`: 80/100 (this document), [markdown](https://verifymcp.io/servers/simulacra-verifyfirst/verifyfirst-mcp.md), [page](https://verifymcp.io/servers/simulacra-verifyfirst/verifyfirst-mcp)

## Channel facts

- Registry: `pypi`
- Package: `verifyfirst-mcp`
- Version: `1.8.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-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 27 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1206 tokens (~150/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

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

### Cursor

```json
{
  "mcpServers": {
    "simulacra-verifyfirst": {
      "command": "uvx",
      "args": [
        "verifyfirst-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "simulacra-verifyfirst": {
      "command": "uvx",
      "args": [
        "verifyfirst-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add simulacra-verifyfirst -- uvx verifyfirst-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add simulacra-verifyfirst --command uvx --arg verifyfirst-mcp
```

### Hermes

```yaml
mcp_servers:
  simulacra-verifyfirst:
    command: "uvx"
    args: ["verifyfirst-mcp"]
```

### Netclaw

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

### Vellum

```bash
assistant mcp add simulacra-verifyfirst -t stdio -c uvx -a verifyfirst-mcp
```

### Other

```json
{
  "mcpServers": {
    "simulacra-verifyfirst": {
      "command": "uvx",
      "args": [
        "verifyfirst-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-09-20 (score 80, +1)

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

### 2026-09-18 (score 79, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-16 (score 63, +1)

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

### 2026-09-15 (score 62, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-14 (score 77, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-12 (score 61, +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-09-09 (score 60, +1)

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

### 2026-09-07 (score 59, +1)

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

## MCP tools (8)

### `list_instruments` (~88 tokens)

List the six verification instruments an agent can observe a system through: screenshot, exit-code, http-response, file-on-disk, process-list, log-output. Each entry says what the instrument is used for so you can identify which one you are actually relying on right now. Start here when you are not sure how to name the instrument you just used, then call blind_spots on it.

### `blind_spots` (~238 tokens)

PRE-FLIGHT CHECK. Call this in the moment before you claim a task is done or a fix is verified. Give it the instrument you are trusting — a screenshot, an exit code, an HTTP status, a file you read, a process list, a log — and it returns the terse list of failure modes that instrument is structurally incapable of showing you. A screenshot cannot see time. An exit code cannot see semantics. A 200 cannot see staleness. A config file cannot see what the running process loaded. Reading this list takes seconds and is the difference between 'the command exited zero' and 'the change is live'. Accepts loose names: 'curl', 'ps', 'journalctl', 'I looked at the screenshot' all resolve. Use get_instrument afterwards for the worked examples.

Input parameters:

- `instrument` (string, required): The instrument you are verifying through. Canonical ids: screenshot, exit-code, http-response, file-on-disk, process-list, log-output. Common aliases also work (curl, 200, ps, pgrep, systemctl, journ…

### `get_instrument` (~131 tokens)

Full dossier on one instrument: what it genuinely captures, everything it is blind to, and every recorded real-world failure it missed — each with the false reading, the true state, and one concrete check that separates them. Use this after blind_spots when a listed blind spot might apply to what you are doing and you want the specific command or expression that would settle it. Every failure here was actually observed and diagnosed; none are hypothetical.

Input parameters:

- `id` (string, required): Instrument id: screenshot, exit-code, http-response, file-on-disk, process-list, or log-output. Aliases are accepted.

### `search` (~119 tokens)

Case-insensitive substring search across every recorded failure's title, false reading, true state, and failure class. Use it when you have a symptom rather than an instrument: 'blank page', 'cache', 'font', 'hang', 'oom', 'systemctl', 'opacity', 'no output'. Also useful for checking whether a surprising behaviour you just hit is a known instrument artifact before you spend rounds tuning against it.

Input parameters:

- `query` (string, required): Substring to look for, e.g. 'cache', 'blank', 'font', 'oom'.

### `get_entry` (~96 tokens)

Retrieve one recorded failure in full by its id, e.g. 'NS-001'. Returns the false reading, the true state, why the instrument could not separate them, the discriminating check, the cost of missing it, and what it generalises to. Use after search or get_instrument surfaces an id you want the complete account of.

Input parameters:

- `id` (string, required): Entry id such as NS-001 through NS-014.

### `from_symptom` (~183 tokens)

Start here when something is wrong but you do not yet know why. Describe what you are actually observing, in your own words — 'the page is blank', 'deploy ran but nothing changed', 'API returns 200 but the data is wrong', 'the service says active but is not serving', 'the command hangs and never returns' — and this returns the recorded failures that produce that exact appearance, each with the one check that tells them apart. This is the symptom-first door into the registry; blind_spots is the instrument-first one. Use this when you have a symptom, and blind_spots when you are about to verify something and want to know what your method cannot see.

Input parameters:

- `description` (string, required): What you are seeing, in plain words. A sentence works better than a keyword: 'screenshot shows a blank page in headless chrome'.

### `before_claiming` (~171 tokens)

Call this immediately before reporting a task complete — before writing 'done', 'fixed', 'deployed', 'working' or 'the tests pass'. Describe what you just did ('deployed a static site', 'restarted the service', 'changed a config file', 'ran the test suite', 'fetched a URL', 'published a package') and it returns an ordered preflight: the specific checks that would catch this task failing silently, each with the command to run and the recorded failure it guards against. Unlike from_symptom, nothing has to have gone wrong yet — this is for the moment when you believe the work succeeded.

Input parameters:

- `task` (string, required): What you just did, in plain words. 'I copied the built files to the web root' works as well as 'deploy'.

### `get_protocol` (~102 tokens)

The five-step verification checklist to run before reporting any work as complete: name the instrument, say what it cannot see, run one check that could actually come out either way, report the observation rather than the inference, and prefer resolved values over authored ones. Returns the checklist plus the underlying principles. Call it once at the start of a verification pass, or any time you are about to write the words 'done', 'fixed', 'working', or 'deployed'.

## Diagnostics

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

## Score history

- 2026-09-20: 80
- 2026-09-19: 79
- 2026-09-18: 79
- 2026-09-17: 63
- 2026-09-16: 63
- 2026-09-15: 62
- 2026-09-14: 77
- 2026-09-13: 61
- 2026-09-12: 61
- 2026-09-11: 60
- 2026-09-10: 60
- 2026-09-09: 60
- 2026-09-08: 59
- 2026-09-07: 59
- 2026-09-06: 58
- 2026-09-05: 58
- 2026-09-04: 57
- 2026-09-03: 57
- 2026-09-02: 56
- 2026-09-01: 56
- 2026-08-31: 55
- 2026-08-30: 55
- 2026-08-29: 54
- 2026-08-28: 54
- 2026-08-27: 53
- 2026-08-26: 53
- 2026-08-25: 51
- 2026-08-24: 50
- 2026-08-23: 65

## Common questions

### What is the verifyfirst MCP server?

verifyfirst is an MCP server listed in the public MCP registry as io.github.simulacra/verifyfirst. Look up what your verification method cannot see: 48 failures that report success. This page covers its PyPI package (verifyfirst-mcp).

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

verifyfirst scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 verifyfirst MCP server expose?

verifyfirst exposes 8 tools: list_instruments, blind_spots, get_instrument, search, get_entry, and 3 more. Their descriptions and schemas cost roughly 1,128 tokens of context every time the server is loaded.

### Is the verifyfirst MCP server still maintained?

verifyfirst is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- PyPI project: https://pypi.org/project/verifyfirst-mcp/
- Socket report: https://socket.dev/pypi/package/verifyfirst-mcp
- Repository: https://github.com/simulacra/verifyfirst
- Website: https://verifyfirst.dev/
- Changelog RSS feed: https://verifymcp.io/servers/simulacra-verifyfirst/verifyfirst-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/simulacra-verifyfirst/verifyfirst-mcp.json
- HTML version of this page: https://verifymcp.io/servers/simulacra-verifyfirst/verifyfirst-mcp