Skip to main content
Glama
williamblakecunningham-max

screenverity-mcp

by williamblakecunningham-max
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to screenverity-mcp

No user-submitted related servers found.

    Related Servers

    • fairquery-sanctions-screener by fairquery

      fairquery-sanctions-screenerofficial

      fairquery
      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
    • Pyxmark by pyxmark

      Pyxmarkofficial

      pyxmark
      F
      license
      Not graded
      quality
      D
      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.
      -

    • hive-mcp-agent-kyc

      srotzin
      A
      license
      Not graded
      quality
      C
      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

    • FLINT Agent Passport

      thefraudfather
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables verification of AI agent identity, authority, and integrity at transaction time, returning signed verdicts for allow, step-up, review, or block.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivityStale
    ResponsivenessNo issues

    Resources