Skip to main content
Glama
XCP

Counterparty MCP Server

by XCP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Counterparty MCP Server

No user-submitted related servers found.

    Related Servers

    • Bitcoin MCP

      tiero
      A
      license
      C
      quality
      D
      maintenance
      Enables AI applications to interact with the Bitcoin Network, manage wallets, check balances, convert prices, and send transactions.
      4
      22 npm
      6
      MIT

    • Cryptocurrency Daemon MCP

      raw391
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables secure interactions with cryptocurrency daemon RPC interfaces through AI assistants, supporting transaction management, wallet operations, and daemon monitoring for Bitcoin-derived cryptocurrencies.
      1
      -

    • Bitcoin SV MCP Server

      opldotdev
      A
      license
      B
      quality
      C
      maintenance
      A collection of Bitcoin SV tools for the Model Context Protocol that enables AI assistants to interact with the BSV blockchain through wallet operations, ordinals (NFTs), and various blockchain utilities.
      9
      118 npm
      22
      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

    B3.4/5.0

    Scored across 48 tools

    Disambiguation4/5

    Most tools are clearly distinct by resource and action, but there are many similar get_* tools that differ only by filter (by_asset, by_address, by_pair), which could cause confusion. The descriptions help, but the sheer number of similar patterns creates some ambiguity.

    Naming Consistency4/5

    Uses a consistent verb_noun snake_case pattern (get_ for reads, compose_ for transaction building). Some deviations like api_request, compose_mpma, compose_movetoutxo, and unpack_transaction vs decode_transaction slightly break the pattern, but it's mostly predictable.

    Tool Count2/5

    48 tools is far beyond the typical range. Even though the Counterparty protocol is complex, this many tools creates a heavy surface that agents must navigate. The api_request catch-all further suggests the count could have been trimmed.

    Completeness4/5

    The tool set covers most core Counterparty operations: assets, orders, dispensers, dividends, sends, issuance, and various compose actions. The api_request tool provides a fallback for missing endpoints. Minor gaps exist (e.g., no specific query for fairminters), but it's generally complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources