Skip to main content
Glama
Tarmac MCP

Tarmac MCP

Official
by tarmacagent

Related Servers

Alternatives to Tarmac MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables Robinhood Chain trading agents to obtain quotes, policy-checked unsigned public-swap calldata, simulations, hook information, prices, and deployment discovery without holding keys or signing transactions.
      9
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP hosts to read and trade Robinhood Chain markets, including swaps, launch checks, bonding-curve launches, Arcus and Lighter perps and funding, weekend reopen watch, bridging, and local wallet operations with two-step confirmations.
      1,307 npm
      MIT
    • 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
      C
      maintenance
      Enables AI agents to trade tokenized stocks (e.g., NVDA, TSLA) on Robinhood Chain via MCP, with non-custodial keys and spending caps.
      21 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and MCP clients to manage a private balance on Robinhood Chain by checking balances and pools, reviewing policy and activity, and quoting or executing sends, swaps, withdrawals, and deposits through quote IDs.
      Apache 2.0

    TDQS

    A3.6/5.0

    Scored across 8 tools

    Disambiguation4/5

    The tools largely map to distinct steps in a run lifecycle: start/attach, context, balances, quote, swap request, finish, and run status. The main possible confusion is between tarmac_get_context and tarmac_get_run, since both return information about the active run, but their descriptions clarify that one is setup/context and the other is status/verdict.

    Naming Consistency4/5

    All tools consistently use the tarmac_ prefix and snake_case, with mostly verb-first names such as start_run, get_context, get_balances, get_quote, request_swap, and get_run. Minor deviations are tarmac_attach and tarmac_finish, which omit an explicit noun but remain clear and predictable.

    Tool Count5/5

    Eight tools is well scoped for a simulated-wallet test-run server. Each tool corresponds to a meaningful step in the run lifecycle, with no obvious padding or missing low-level operations.

    Completeness5/5

    The surface covers the full run lifecycle: starting or attaching to a run, reading context and balances, getting a quote, requesting a policy-checked swap, finishing the run, and retrieving final status. No obvious dead ends remain for the stated simulated trading workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues