screenverity-mcp
Related Servers
Alternatives to screenverity-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables agents to verify US businesses against official keyless state registries (NY/CO/CT) and screen names against the live OFAC SDN sanctions list, returning scored matches, Colorado UCC-lien profiles, provenance, and explainable no-match audits.4MIT
- AlicenseAqualityAmaintenanceEnables 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.3MIT
- FlicenseNot gradedqualityCmaintenanceEnables 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.-
- AlicenseNot gradedqualityDmaintenanceRoutes 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
- AlicenseAqualityDmaintenanceEnables AI agents to screen business partners against EU/US/HADDEX sanctions and PEP lists, and maintain the easycompliance daily monitoring list.613 npmMIT

Verifex MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to screen a person or company against sanctions lists via Verifex, read back a past screening, and fetch its Evidence Capsule audit record. Sends only name, type, country and date of birth, and reports each result's status and which lists were actually checked.100 npm1MIT
TDQS
Scored across 3 tools
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.
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.
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.
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.