screenverity-mcp
Related Servers
Alternatives to screenverity-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceRoutes 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
- AlicenseAqualityBmaintenanceEnables AI agents to screen business partners against EU/US/HADDEX sanctions and PEP lists, and maintain the easycompliance daily monitoring list.66 npmMIT
- AlicenseNot gradedqualityFmaintenanceEnables verification of AI agent identity, authority, and integrity at transaction time, returning signed verdicts for allow, step-up, review, or block.MIT
- AlicenseNot gradedqualityCmaintenanceScreens names against the US Consolidated Screening List including OFAC SDN and BIS Entity List, keyless.1 npmMIT
- AlicenseNot gradedqualityDmaintenanceScreens individuals and entities against the OIG LEIE exclusion list, returning candidate matches that require human verification.MIT
- AlicenseNot gradedqualityBmaintenanceEnables pay-per-call screening of individuals and entities against the HHS-OIG List of Excluded Individuals and Entities (LEIE), with x402 payment and an MCP interface for agents.MIT
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.