Tarmac MCP
OfficialRelated Servers
Alternatives to Tarmac MCP
No user-submitted related servers found.
Related Servers
AlicenseAqualityBmaintenanceEnables 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.9MIT- AlicenseNot gradedqualityCmaintenanceEnables MCP clients and AI agents to privately swap and send assets on Robinhood Chain, with quotes, swap creation, deposit payment from an optional local wallet, status checks, handoff links, wallet balances, and rewards.MIT

noctennaofficial
AlicenseNot gradedqualityBmaintenanceEnables 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 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables 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

hoodr MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to trade tokenized stocks (e.g., NVDA, TSLA) on Robinhood Chain via MCP, with non-custodial keys and spending caps.21 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables 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
Scored across 8 tools
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.
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.
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.
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.