Skip to main content
Glama
Kosmo-Protocol

Kosmo Protocol MCP server

Official

Related Servers

Alternatives to Kosmo Protocol MCP server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to propose policy-gated treasury payments and swaps, check pending human approvals, read transaction receipts, and locally verify their integrity through MCP tools.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Printr, a cross-chain token launchpad. Lets AI agents launch, stake, and graduate tokens across EVM chains and Solana without requiring an API key.
      4
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to create and verify tamper-evident cryptographic evidence, manage key-bound Agent Passports, and support verifiable handoffs, approvals, and audit trails through MCP, REST, and A2A.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to research, trade and move money across crypto spot and perpetuals, stocks, commodities, forex, prediction markets, onchain swaps and bridging, and memecoins through a single remote MCP connection with no installation or hosting required. It also supports wallet management, fiat on-ramps and token launches, with every write action asking the user for approval first.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to manage API keys and child keys with budgets and spending caps, set plans and model routing, handle wallet payments and top-ups, and verify signed receipts through MCP tools.
      265 npm
      2
      MIT

    TDQS

    B3.4/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools target distinctly separate steps (list/get reads, prepare_launch, metadata lifecycle, badge flow, agent room). The only mild collision is between prepare_metadata_message and prepare_badge_message, both 'prepare a signing message' tools, but the descriptions clearly delineate their respective flows.

    Naming Consistency4/5

    Names consistently use snake_case with a verb_noun structure (list_chains, prepare_launch, upload_logo, save_metadata, apply_badge). Minor deviation is the use of three different read verbs (list_chains, get_metadata, read_agent_room), which slightly breaks predictability.

    Tool Count5/5

    12 tools is well within a healthy range and each maps to a concrete capability across launch, metadata, badge, and agent/room domains. No obvious filler or redundant tools.

    Completeness4/5

    The surface covers the launch lifecycle (chains, quote assets, prepare_launch), full metadata lifecycle (prepare, upload logo, save, lock, get), badge issuance, agent listing, and room reads. Minor gaps: no way to inspect launched-token/factory state or launch status after preparation, but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues