Skip to main content
Glama
Sign In
bitroad-mcp

bitroad-mcp

by bitroadai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to bitroad-mcp

No user-submitted related servers found.

    Related Servers

    • OrcaRail MCP

      OrcaRail MCPofficial

      OrcaRail
      A
      license
      B
      quality
      B
      maintenance
      Official MCP server for accepting crypto payments through OrcaRail. It enables AI agents to create payment intents, manage subscriptions, handle product catalogs, and get exchange rates via natural language.
      26
      77 npm
      MIT

    • craftpilot-mcp

      laur221
      A
      license
      B
      quality
      B
      maintenance
      This MCP server exposes a running Minecraft client's local HTTP API as tools over stdio, enabling AI assistants to inspect and control the game through screenshots, GUI interaction, input, chat, commands, movement, inventory, and world management.
      23
      MIT

    • roastify-mcp

      lonniev
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for the Roastify Developer API, letting AI agents browse the coffee catalog and generate packaging artwork, with paid tools settled in Bitcoin Lightning.
      Apache 2.0

    • mcp-mc-agent

      blueziii
      A
      license
      A
      quality
      C
      maintenance
      Gives any MCP client (Claude Desktop, Cursor, and others) a Minecraft character it can actually play, exposing 34 mc_* tools for joining servers, pathfinding, mining, crafting, smelting, chest access, combat, building, chat, first-person screen viewing, and session memory. Runs over stdio or Streamable HTTP with one character per server process.
      34
      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.8/5.0

    Scored across 65 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, with clear separation between buyer, seller, and service workflows. Despite the large number, there is no overlap or ambiguity.

    Naming Consistency4/5

    Tools follow a consistent domain_verb_noun pattern (e.g., seller_create_listing, disputes_withdraw), with a few minor deviations like auth_whoami and seller_onboarding_status that don't break the overall convention.

    Tool Count1/5

    65 tools is far beyond any reasonable scope for a single MCP server, vastly exceeding the typical 3-15 range and even the 50+ threshold for extreme mismatch.

    Completeness4/5

    The tool surface covers the marketplace lifecycle comprehensively—catalog, orders, returns, disputes, services, and auth—but has minor gaps such as no direct order cancellation for buyers or payout management for sellers.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Resources