
ScreenVerity
io.github.williamblakecunningham-maxPublished by GitHub account williamblakecunningham-maxv0.2.1Updated Oct 24, 2026
Free U.S. exclusion, debarment and licence screening with a signed receipt of the lists checked.
Overview
ScreenVerity lets an assistant screen a name against U.S. exclusion, debarment and licence lists and get a signed receipt of the lists checked.
- What you can do
- Screen one subject across every loaded list, returning clear, possible_match or match with a signed receipt, and pass identifiers such as NPI, date of birth or licence when available to avoid name-only caps. List the loaded sources with their jurisdiction, freshness and full, partial or never_loaded coverage. Verify an Ed25519 receipt against its request and response.
- When to use it
- Useful when an assistant needs a quick, auditable check of a person or entity against public U.S. exclusion and debarment lists, or needs to confirm which lists were actually consulted before relying on a result.
- Requirements
- Runs locally over stdio, typically via npx screenverity-mcp or by running the single dependency-free server file with Node.js. No API key, account or wallet is needed. Network access to the public ScreenVerity endpoint is required, and that endpoint is rate limited.
Installation
In SourceWeft
- Open ScreenVerity in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
screenverity-mcp
MCP server for ScreenVerity — U.S. exclusion, debarment and licence screening for agents, with an Ed25519-signed receipt of exactly which list snapshots were checked.
Screening one name through a state or federal portal usually costs an agent ~50k–200k tokens
of browse-and-parse traffic and leaves no audit artefact. One POST /v1/screen is ~2k tokens
of structured JSON, and it leaves evidence.
Coverage is explicit and deliberately unexaggerated — call sources and read it. This is not a
"50 states" product.
Install
Or run the single file directly — it has no dependencies:
Claude Code
Any MCP client (stdio)
Tools
All three are free. No API key, no account, no wallet.
Call sources before assuming any particular list is covered.
Cost
Free. There is no payment, no key and no account.
The public endpoint is rate limited. If you are limited, screen returns
{"error": "rate_limited"} — it never fabricates a clear result. That property is
deliberate: a screening tool that guesses is worse than no screening tool.
0.1.0 charged $0.25 per call via x402. That is gone. If you pinned 0.1.0, upgrade — it points at an endpoint that no longer exists in that form.
Using the results
possible_matchmeans adjudicate, not auto-reject.- If
completeisfalse, a list was unavailable — it is not a full screen. - Always pass
npi,dob, orlicensewhen you have them. Common names without identifiers are capped atpossible_matchby design.
Not a consumer report
ScreenVerity is compliance-workflow tooling that retrieves and signs public exclusion-list data. It is not a consumer reporting agency and its output is not a consumer report. Do not use it to make eligibility decisions about employment, credit, insurance, or housing. Consult counsel about FCRA obligations for your use case.
More
- Skill description for agents:
SKILL.md - Integration guide:
INTEGRATION.md - API spec:
openapi.json· live at https://api.screenverity.com/openapi.json - Coverage, right now: https://api.screenverity.com/v1/sources
License
MIT
Source: README.md at commit 8f1139c
Tools
0Version history
1- v0.2.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts