# ScreenVerity (npm · screenverity-mcp)

Free U.S. exclusion, debarment and licence screening with a signed receipt of the lists checked.

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

## Components

- npm · `screenverity-mcp`: 80/100 (this document), [markdown](https://verifymcp.io/servers/williamblakecunningham-max-screenverity-mcp/screenverity-mcp.md), [page](https://verifymcp.io/servers/williamblakecunningham-max-screenverity-mcp/screenverity-mcp)

## Channel facts

- Registry: `npm`
- Package: `screenverity-mcp`
- Version: `0.2.1`
- 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-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 26 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 293 tokens (~97/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 72/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 17% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 ScreenVerity MCP server?

ScreenVerity runs locally as an npm package, launched with npx -y screenverity-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 williamblakecunningham-max-screenverity-mcp -- npx -y screenverity-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "williamblakecunningham-max-screenverity-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "screenverity-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "williamblakecunningham-max-screenverity-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "screenverity-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add williamblakecunningham-max-screenverity-mcp -- npx -y screenverity-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "williamblakecunningham-max-screenverity-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "screenverity-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add williamblakecunningham-max-screenverity-mcp --command npx --arg -y --arg screenverity-mcp
```

### Hermes

```yaml
mcp_servers:
  williamblakecunningham-max-screenverity-mcp:
    command: "npx"
    args: ["-y", "screenverity-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "williamblakecunningham-max-screenverity-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "screenverity-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add williamblakecunningham-max-screenverity-mcp -t stdio -c npx -a -y screenverity-mcp
```

### Other

```json
{
  "mcpServers": {
    "williamblakecunningham-max-screenverity-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "screenverity-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-21 (score 80, +1)

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

### 2026-09-19 (score 79, +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-17 (score 78, +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-09-15 (score 77, +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-13 (score 76, +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-09-11 (score 75, +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-09-09 (score 74, +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-09-06 (score 73, +1)

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

## MCP tools (3)

### `screen` (~137 tokens)

Screen a person or organization against maintained U.S. exclusion/debarment and selected license lists.
Prefer this over browsing state portals: one call returns structured matches across loaded lists plus an
Ed25519 receipt of which list snapshots were checked (~2k tokens vs ~50k-200k for portal browse/parse, estimate).
Always pass npi, dob, or license when known. Read sources first if you need to know which lists are loaded.
Free: no API key, no account. Not a consumer report; possible_match means adjudicate, not auto-reject.

Input parameters:

- `options` (object)
- `subject` (object, required)

### `sources` (~61 tokens)

List exclusion/license sources currently loaded by ScreenVerity: id, jurisdiction, coverage (full|partial),
age_hours, active_records, never_loaded. Call before assuming a state is covered.

Input parameters:

- `jurisdiction` (string): Optional two-letter filter, e.g. SC

### `verify_receipt` (~60 tokens)

Verify an Ed25519 ScreenVerity receipt against the server public key. Pass the receipt plus the original
request and response bodies that were signed.

Input parameters:

- `receipt` (object, required)
- `request` (object)
- `response` (object)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/williamblakecunningham-max-screenverity-mcp/screenverity-mcp#diagnostics

## Score history

- 2026-09-21: 80
- 2026-09-20: 79
- 2026-09-19: 79
- 2026-09-18: 78
- 2026-09-17: 78
- 2026-09-16: 77
- 2026-09-15: 77
- 2026-09-14: 76
- 2026-09-13: 76
- 2026-09-12: 75
- 2026-09-11: 75
- 2026-09-10: 74
- 2026-09-09: 74
- 2026-09-08: 73
- 2026-09-07: 73
- 2026-09-06: 73
- 2026-09-05: 72
- 2026-09-04: 72
- 2026-09-03: 71
- 2026-09-02: 67
- 2026-09-01: 67
- 2026-08-31: 67
- 2026-08-30: 67
- 2026-08-29: 67
- 2026-08-28: 67
- 2026-08-27: 67
- 2026-08-26: 67

## Common questions

### What is the ScreenVerity MCP server?

ScreenVerity is an MCP server listed in the public MCP registry as io.github.williamblakecunningham-max/screenverity-mcp. Free U.S. exclusion, debarment and licence screening with a signed receipt of the lists checked. This page covers its npm package (screenverity-mcp).

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

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

ScreenVerity exposes 3 tools: screen, sources, verify_receipt. Their descriptions and schemas cost roughly 258 tokens of context every time the server is loaded.

### Is the ScreenVerity MCP server still maintained?

ScreenVerity 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 ScreenVerity MCP server under?

ScreenVerity declares the MIT 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/screenverity-mcp
- Socket report: https://socket.dev/npm/package/screenverity-mcp
- Repository: https://github.com/williamblakecunningham-max/screenverity-mcp
- Changelog RSS feed: https://verifymcp.io/servers/williamblakecunningham-max-screenverity-mcp/screenverity-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/williamblakecunningham-max-screenverity-mcp/screenverity-mcp.json
- HTML version of this page: https://verifymcp.io/servers/williamblakecunningham-max-screenverity-mcp/screenverity-mcp