Skip to main content
Glama

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

npx screenverity-mcp

Or run the single file directly — it has no dependencies:

curl -O https://api.screenverity.com/mcp/server.js
node server.js

Claude Code

claude mcp add screenverity -- npx -y screenverity-mcp

Any MCP client (stdio)

{
  "mcpServers": {
    "screenverity": {
      "command": "npx",
      "args": ["-y", "screenverity-mcp"]
    }
  }
}

Related MCP server: mcp-easycompliance

Tools

Tool

What it does

screen

Screen one subject across every loaded list; returns clear / possible_match / match + a signed receipt

sources

Which lists are loaded, their jurisdiction, freshness, and full / partial / never_loaded coverage

verify_receipt

Check an Ed25519 receipt against its request/response

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_match means adjudicate, not auto-reject.

  • If complete is false, a list was unavailable — it is not a full screen.

  • Always pass npi, dob, or license when you have them. Common names without identifiers are capped at possible_match by 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

License

MIT

Available Tools

3 tools
screenA

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.

Inputs: subject (required), options.

sourcesA

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.

Inputs: jurisdiction.

verify_receiptA

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

Inputs: receipt (required), request, response.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a clear, separate purpose: 'screen' performs the core lookup, 'sources' provides metadata about loaded lists, and 'verify_receipt' handles cryptographic verification. There is no overlap in function or ambiguity in what each does.

    Naming Consistency5/5

    Tool names are simple, lowercase, and follow a consistent style. 'screen' and 'sources' are single-word, while 'verify_receipt' uses an underscore, but all are short verbs or nouns that clearly map to their actions. No mixed conventions or vague verbs.

    Tool Count5/5

    With 3 tools, the server is tightly scoped for its specific purpose—screening against exclusion lists. Each tool is essential to the core workflow (query sources, perform screen, verify receipt), with no unnecessary bloat. This is well within the ideal range.

    Completeness5/5

    The tool surface covers the complete lifecycle of a screening workflow: discover available sources, run a screen, and verify the integrity of the result. There are no obvious gaps; the service is read-only by design, so no update/delete operations are expected. All critical operations are present.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Routes blockchain address screening to third-party KYC/AML providers and checks public sanctions lists, serving as a clean-money gate primitive for MCP-compatible agents.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables agents to fuzzy-screen person and company names against the OFAC SDN/Consolidated, EU, UK and UN sanctions lists downloaded fresh from official sources, returning potential-match statuses, 0–100 scores and listing details via a billed screening tool, plus a free local tool that lists covered sources, score scale and disclaimer.
      3
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables screening companies or people against OFAC, UN, EU and UK sanctions lists, looking up SEC EDGAR records, checking domain age and email records, and compiling due-diligence reports with source links and a clear, review, or hold verdict.
      -