Skip to main content
Glama
CMSCardOS

CardOS MCP Server

Official
by CMSCardOS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to CardOS MCP Server

No user-submitted related servers found.

    Related Servers

    • Mono Banking MCP Server

      sin4ch
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to perform Nigerian banking operations including account management, payments, and identity verification through the Mono Open Banking API.
      59
      MIT
    • Shatale MCP Server by Shatale-SASU

      Shatale MCP Serverofficial

      Shatale-SASU
      A
      license
      A
      quality
      A
      maintenance
      AI-native payment infrastructure that enables AI agents to make purchases, issue virtual cards, and manage spending within delegated budgets and policy controls.
      7
      286 npm
      MIT

    • AgentCard MCP Server

      tiny-agent-company
      -
      license
      Not graded
      quality
      F
      maintenance
      Enables AI agents to manage and use prepaid virtual Visa cards with hard budget limits for secure online transactions. It provides tools for creating cards, checking balances, and retrieving payment credentials with human-in-the-loop approvals.
      1
      -

    • x402card

      RWA-ID
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to spend from ENS-addressed virtual cards without ever seeing card numbers or API keys, by issuing cards with spend policy published as ENS text records, checking card status, requesting funding, freezing a card, and listing transactions. Charges within policy clear automatically, while above-policy requests escalate to a human approver and anomalous activity triggers an automatic freeze.
      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

    A3.6/5.0

    Scored across 26 tools

    Disambiguation5/5

    Each tool targets a distinct operation on a specific resource (e.g., card, deposit, dispute, KYC, webhook). No two tools have overlapping purposes; descriptions clearly differentiate them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case. The naming convention is uniform across the entire set, making it predictable and easy to navigate.

    Tool Count4/5

    With 26 tools, the count is slightly above the typical 3-15 range, but the breadth of card operations (issuing, management, disputes, KYC, webhooks) justifies the number. It is still reasonable and not overly bloated.

    Completeness5/5

    The tool surface covers the full lifecycle of card management, deposits, disputes, KYC, webhooks, and analytics. Essential CRUD operations are present, and sandbox tools support testing. Missing operations are minor and non-critical.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources