Skip to main content
Glama

Related Servers

Alternatives to @arcnautical/mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables vessel screening by IMO number for sanctions matches, ownership opacity, and A–E vetting grades, along with batch screening and retrieval of stored records. Also resolves port names or countries to UN/LOCODEs and scores voyage risk between two ports.
      65 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables real-time vessel tracking, port data, maritime weather, and maritime intelligence through 25 tools, allowing AI clients to query live vessel positions, registry, port info, area searches, weather, and more.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP-compatible AI agents to screen counterparties against government sanctions lists and fraud-cluster registries, check regulatory tradability across 235 jurisdictions, and run pre-deal compliance checks via OilFlow APIs, with three tools usable without an API key.
      13
      9 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      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

    TDQS

    A3.9/5.0

    Scored across 7 tools

    Disambiguation4/5

    check_vessel, screen_vessel and screen_vessels all screen vessels and could be confused, but the descriptions explicitly differentiate them (free summary vs. authenticated full record vs. batch) and even point callers from check_vessel to screen_vessel. find_port, get_screening, get_usage and score_voyage are clearly distinct.

    Naming Consistency4/5

    Names consistently use snake_case verb_noun (get_screening, find_port, screen_vessel, score_voyage). The only deviation is the mixed verb choice 'check' vs 'screen' for the same core action and the singular/plural screen_vessel vs screen_vessels pair, which is a minor blemish.

    Tool Count5/5

    Seven tools is well-scoped for a maritime sanctions-screening server, with each tool earning its place (single screening, batch screening, record retrieval, port resolution, voyage scoring, usage). No redundant or filler tools.

    Completeness4/5

    Covers the core lifecycle: resolve ports, screen vessels individually and in batch, retrieve retained records, score voyage risk and check usage. Minor gaps exist — get_usage references monitor capacity but no tool manages monitors, and there is no tool to list or export past screenings.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data