Skip to main content
Glama
rafaemush

@oilflow/mcp-server

by rafaemush

Related Servers

Alternatives to @oilflow/mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Real-time OFAC and global sanctions screening for AI agents: screen crypto addresses, emails, websites, government IDs, and countries against OFAC SDN and 10+ sanctions/crime/risk lists, plus PEP screening, VPN detection, and IP geolocation. Hosted remote streamable-HTTP server at https://api.compliapi.com/mcp (anonymous tools/list; free API key or x402 pay-per-call).
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Provides AI agents with compliance screening (OFAC sanctions, risk scoring, Know-Your-Agent) plus disposable email and SMS verification for OTPs, accessible via MCP tools, HTTP API, and CLI.
      10
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      53 regulatory compliance evidence tools across 3 MCP servers for AI agents. MiCA authorization status, DORA evidence packs, stablecoin risk scoring (105+ tokens), macro intelligence (86 FRED series). Every response ECDSA-signed (ES256K), blockchain-anchored, audit-ready. Free tier, OAuth 2.0.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to perform identity verification, KYC/KYB, PEP & sanctions screening, bank statement analysis, and workflow automation via the Model Context Protocol.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to investigate corporate ownership, trace ultimate beneficial owners, screen sanctions, detect offshore exposure, and access fully cited dossiers from 130M+ entities across 31 global registries.
      21
      96 npm
      1
      MIT

    TDQS

    A4.3/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools map cleanly to a distinct resource or workflow: pre-deal, KYC, regulatory matrix, cluster feed, LC, UBO, receipts, and keys. The only real ambiguity is predeal_preview vs predeal_check, which are the same core function split by API-key requirement, and cluster_check vs clusters_list, though names and descriptions differentiate lookup from browsing. Overall an agent can reliably select the right tool.

    Naming Consistency4/5

    The dominant pattern is domain_operation: predeal_preview, regulatory_check, cluster_check, kyc_screen, lc_validate, ubo_screen. A few tools break the pattern with verb-first names like verify_receipt and request_sandbox_key, and noun-only names like regulatory_countries, regulatory_products, clusters_list, and ubo_graph. It is not perfectly uniform, but the naming is still predictable and readable.

    Tool Count5/5

    13 tools is well within the ideal range for a compliance-focused API and each tool corresponds to a distinct endpoint or workflow. The set covers multiple compliance subdomains without feeling bloated, and the free/keyed pre-deal pair is intentional rather than redundant.

    Completeness4/5

    The major workflows are covered: pre-deal checks, receipt verification, regulatory matrix lookups, cluster intelligence, LC validation, and UBO screening with polling. A minor gap is that kyc_screen can return queued results with a poll_url but there is no dedicated MCP tool to poll KYC results, though agents can work around this via the URL.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues