Skip to content
Launch Tape logo

Launch Tape MCP server

Which MCP servers are Launch Tape's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-30

← Back to Launch Tape

Whose server it is
  • Registry nameio.launchtape/launch-tapeverified in the MCP registry

The registry name sits under launchtape.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-30
  • Stateanswerschecked 2026-10-30
  • Tools10
  • Server calls itselflaunch-tape
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-30 the server answered initialize and tools/list without a sign-in. First answer in 185 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: compare price moves of coins after they graduate; check which new coins doubled in their first minutes; test entry and exit rules against recorded launch trades.
  • Checked on 3 of the 7 days it takes to judge reliability.

Once connected

  • For "check which new coins doubled in their first minutes", the likely first call is graduation_stats.
  • For "test entry and exit rules against recorded launch trades", the likely first call is test_rule.
  • Parameters are untyped or undescribed in 8 of 11 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 3, the first on 2026-10-30
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
  • What an agent can do with it3 of 3 use cases
  • Answeredmeasuring3 of the 7 daily checks it takes to print a share
  • Median first answer298 ms
  • Space in an agent's context≈ 1,812 tokensthe definitions of all its tools (11), which an agent carries on every turn
  • Tool definitionsB · 88 of 100
  • Typed results0 of 11 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 8 of 11

What an agent can do with it

  • can do · compare price moves of coins after they graduate
  • can do · check which new coins doubled in their first minutes
  • can do · test entry and exit rules against recorded launch trades

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers10 tools · read 2026-10-30
  • launch_tape_overview

    What Launch Tape records, dataset descriptions, US dollar plan prices and coverage limits. History starts October 3, 2026; coverage varies by dataset. Use days_available for the exported UTC day range.

  • graduation_stats

    One UTC day: graduate counts, down 90% at 30 minutes, positive/doubled 30-minute changes and median curve fill; followed, gap-free, full tapes only. History starts October 3, 2026; coverage varies by dataset. Use days_available for the…

  • lookup_coin

    Public graduate facts for an exact mint or symbol on one UTC day; at most 20 matches. History starts October 3, 2026; coverage varies by dataset. Use days_available for the exported UTC day range.

  • data_preview

    The same real rows as the public site preview, up to 20. Only graduates, gradtrades and pregrad have site previews. History starts October 3, 2026; coverage varies by dataset. Use days_available for the exported UTC day range.

  • days_available

    Exported UTC days and byte sizes for each dataset, from public manifests. History starts October 3, 2026; coverage varies by dataset. Use days_available for the exported UTC day range.

  • my_plan

    Your purchased scope, expiry and remaining calls. History starts October 3, 2026; coverage varies by dataset. Use days_available for the exported UTC day range.

  • coin_trades

    One graduate and at most 1500 compact trades in its first 30 minutes. History starts October 3, 2026; coverage varies by dataset. Use days_available for the exported UTC day range.

  • wallet_day

    Wallet and walletcoin daily observations, at most 100 rows. History starts October 3, 2026; coverage varies by dataset. Use days_available for the exported UTC day range.

  • top_wallets

    Top daily wallet observations, at most 50. History starts October 3, 2026; coverage varies by dataset. Use days_available for the exported UTC day range.

  • day_full_stats

    Graduation stats, 10-minute buyers, dev-share bands and touched outcome distributions. History starts October 3, 2026; coverage varies by dataset. Use days_available for the exported UTC day range.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "launch-tape": {
      "type": "http",
      "url": "https://launchtape.io/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http launchtape https://launchtape.io/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://launchtape.io/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.