ScreenVerity
NPM · SCREENVERITY-MCP
Free U.S. exclusion, debarment and licence screening with a signed receipt of the lists checked.
Available components
Last scanned (9 hours ago)
Scores higher than 65% of npm servers
Category Security
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 72 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 293 tokens (~97/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage72
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 17% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 5 Nov 26 −2
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.83 functional
- 30 Oct 26 0
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.97 functional
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 0
- Stability: pass → 0.97 functional
- 19 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 18 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Analysed npm/screenverity-mcp@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
screen ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| options | object | – | – |
| subject | object | yes | – |
No output schema declared.
No examples provided.
sources ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction | string | – | Optional two-letter filter, e.g. SC |
No output schema declared.
No examples provided.
verify_receipt ~60
Verify an Ed25519 ScreenVerity receipt against the server public key. Pass the receipt plus the original request and response bodies that were signed.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt | object | yes | – |
| request | object | – | – |
| response | object | – | – |
No output schema declared.
No examples provided.
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.
npm · screenverity-mcp
claude mcp add williamblakecunningham-max-screenverity-mcp -- npx -y screenverity-mcp
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 6 November 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 6 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 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.
What did VerifyMCP test on the ScreenVerity MCP server?
VerifyMCP ran 16 checks on ScreenVerity, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.