Mooncatcher Wire

Kostenlose Krypto-Nachrichten für KI-Agenten: Top-Storys nach Markteinfluss sortiert, Suche, Themen und ein KI-Marktüberblick. Remote-Server, kein API-Schlüssel oder Konto erforderlich.

Gehosteter MCP-Server

npx add-mcp 'https://mooncatcherwire.com/mcp'

Installiert in Claude Code, Codex, Cursor und mehr

Dokumentation

Moon Catcher Wire

FOR AGENTS · MCP SERVER

Crypto news for your agent. Free, no account needed.

Moon Catcher Wire runs a Model Context Protocol server with twelve read-only tools. Six read the same board as this site: every wire story of the last cycle, deduplicated and scored by market impact, the AI market digest, search and topics. Six read the Bitcoin snapshot behind Signals, in beta. Add one URL to your MCP client. There is nothing to sign up for and no key to paste.

https://mooncatcherwire.com/mcp

Streamable HTTP, JSON-RPC 2.0, protocol versions 2025-06-18 and 2025-03-26. Send no Authorization header.

Limits

30requests a minute, per IP

1,000requests a day, per IP

initialize, ping, tools/list and tools/call count; notifications and malformed requests do not. The day resets at 00:00 UTC. Over a limit, the call answers with a JSON-RPC error that names the limit and how many seconds to wait, plus a Retry-After header. The minute window is a calendar minute.

Many clients share one address. If your agent runs on a hosted platform, all of that platform's users can share the same allowance, and a busy minute can refuse you through no fault of your own. Wait and retry, or connect with an account (below).

Use it in Claude

Moon Catcher Wire is a remote MCP server, so Claude can read the wire directly in a conversation. It needs no account, no API key and no sign-in step.

Add it

On a Free, Pro or Max plan, open Customize → Connectors in Claude, click Add custom connector, and enter:

https://www.mooncatcherwire.com/mcp

For Authentication, choose No sign-in — this server serves its twelve tools to anyone who has the URL. Then click Add. On a Team or Enterprise plan an Owner adds it once for everyone, under Organization settings → Connectors → Add → Custom, and it then appears for members under Customize → Connectors with a Custom label.

To use it in a chat, click +, choose Connectors, and turn Moon Catcher Wire on. Every tool here is read-only, so Claude can call them without asking you to confirm each one.

Try it

  • “What’s moving crypto today?” — mcw-get-board
  • “Any Ethereum news in the last six hours?” — mcw-list-stories
  • “Search the wire for ETF outflows and summarise what you find.” — mcw-search
  • “Give me today’s market digest and the bull/bear split.” — mcw-get-digest
  • “How old is the Bitcoin signals snapshot, and what does it say about the 4H trend?” — mcw-signals-meta, then mcw-signals-overview

The twelve tools

ToolTitle
mcw-get-boardGet the Moon Catcher Wire board
mcw-list-storiesList stories
mcw-get-storyGet one story
mcw-searchSearch the wire
mcw-list-topicsList topics
mcw-get-digestGet the market digest
mcw-signals-overviewBitcoin signals: overview
mcw-signals-market-dataBitcoin signals: market data
mcw-signals-chartsBitcoin signals: chart
mcw-signals-metaBitcoin signals: freshness and sources
mcw-signals-thesisBitcoin signals: thesis
mcw-signals-sentimentBitcoin signals: sentiment

What each one returns is described in The tools below.

What it will not do

  • It only reads. Every tool is read-only: nothing can be created, changed or deleted through this server, and it takes no action on your behalf.
  • The news is the last cycle’s. The board is checked for updates every minute; it is a news board, not a real-time price feed.
  • Signals is Bitcoin only, and in beta. It publishes direction and confidence with the time each value was observed. No entry, target, stop, take-profit or risk/reward is published, and none of it is investment advice.
  • Editors may withhold stories. A story removed by a Moon Catcher Wire editor is not served here, and each answer reports how many were withheld, so you can see it happened rather than wonder why something is missing.
  • There are rate limits. See Limits above. They are per IP address, and a hosted client can share one with other people.

Privacy, terms and support

What this server records when Claude calls it, and for how long, is in the Privacy policy — see the section “AI assistants, the MCP server and the API”. The Terms cover use of the service. No part of your Claude conversation, memory or files is collected, and the arguments you send are never kept; what is counted is listed under What is kept below.

Questions, problems or a report of something wrong on the wire: admin@mooncatcherwire.com. Our staff answer it; how mail to that address is handled, including the AI that reads it, is under “When you contact us” in the Privacy policy.

Add it to your client

Claude (claude.ai and Claude Desktop): Customize → Connectors → Add custom connector, and give it https://www.mooncatcherwire.com/mcp. No sign-in step. Full instructions and example prompts.

Claude Code:

claude mcp add --transport http mooncatcherwire https://mooncatcherwire.com/mcp

Cursor, Windsurf and other clients with an mcpServers file:

{
  "mcpServers": {
    "mooncatcherwire": { "url": "https://mooncatcherwire.com/mcp" }
  }
}

VS Code (.vscode/mcp.json):

{
  "servers": {
    "mooncatcherwire": { "type": "http", "url": "https://mooncatcherwire.com/mcp" }
  }
}

By hand:

curl -s https://mooncatcherwire.com/mcp \
  -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"mcw-get-board","arguments":{"limit":5}}}'

The tools

ToolFor
mcw-get-boardThe current board: mood, counts, top stories by market impact. Start here.
mcw-list-storiesStories filtered by ticker, topic, age, or breaking only.
mcw-get-storyOne story in full, by id.
mcw-searchCase-insensitive search over headlines and summaries. A ticker (BTC) also finds the stories tagged with it.
mcw-list-topicsThe topics and the rules behind them. Topics are ours; the upstream feed tags only tickers.
mcw-get-digestThe AI market digest for the current board.

The board is checked for updates every minute and carries up to 25 stories per section. Stories an editor has removed are not served, and each answer reports how many were withheld. Nothing can be written through this server, and it gives no investment advice.

Bitcoin signals (beta)

ToolFor
mcw-signals-metaHow old the snapshot and its newest value are, whether it is degraded and why, and every source with its own time. Read this first when age matters. Also, for each BTC price feed, the upstream's own fresh or stale verdict beside this server's.
mcw-signals-overviewSpot, the trend, direction and confidence on thirteen timeframes, each timeframe's direction recomputed every minute (live, with its own age, stale past five minutes: the analysis itself is re-run about every ten minutes, and each row's cadence_check calls it stale past half an hour), the bull, base and bear cases with their probabilities, and support and resistance by how often they recur.
mcw-signals-thesisThe bull, base and bear cases for three horizons: the upstream analysis's own most probable case (and whether the probabilities tie), its dominant case (the highest-probability case with price levels, or none; the levels are not published), the aggregate confidence, each case's probability, each input judged against its own cadence, and the timeframe analyses each horizon is built from.
mcw-signals-market-dataFunding, open interest, liquidations, long/short, taker volume, ETF flows, max pain, two fear and greed indexes from two publishers (each 0 to 100, never averaged), the range over the upstream's latest hourly bars, and all accounts against top traders by position. The latest reading of every metric, plus the newest 3 points of each series; history: true returns the full stored series.
mcw-signals-sentimentThe upstream's sentiment readings: its hourly rollup, one upstream-wide series, not scoped to one org (mean, spread and number of readings per hour, thin under 5), its 24-hour EMA, its own daily news index with its article count, and its blend over its own window. Each with its own time; none combined with another. The newest 3 points of each series by default; history: true returns them all.
mcw-signals-chartsOne timeframe's candles (timeframe, bars — newest 50 by default, up to 200) with the support, resistance and FBB levels its analysis lists.

Bitcoin only. Direction and confidence: no price target or trade plan is published, and none of it is investment advice. They read the snapshot the five-minute job stores, the one the Signals page shows, and never call upstream per request. Every answer opens with a freshness block (when the snapshot was made, the newest value's age, whether it is stale or degraded), and every value keeps the time it was observed; a value kept from an earlier run is marked carried, and null means no data, never zero. Answers are kept small by default — the latest reading of each metric with a short series behind it, and 50 chart bars — and the market-data and sentiment answers say how many points they left out (history.points_omitted), so a short history is never mistaken for a short dataset; a chart answer gives bars_returned. Ask for more with history or bars. The Signals page offers the same six tools over WebMCP to an agent running in the reader's browser.

Agent-to-agent (A2A)

The same news, for agents that speak A2A rather than MCP. The Agent Card describes it; the endpoint answers JSON-RPC SendMessage with one completed message: a text part (headline, source and link per story) and a data part with the same JSON the MCP tools return, plus each story's page here (and the board's mood, with the top stories and the digest). Say top (or nothing) for the top stories, digest for the market digest, or any other word, name or ticker to search the board. No streaming, no tasks to poll. Free, no account needed, under the same limits as the MCP server, shared with it.

https://mooncatcherwire.com/a2a

curl -s https://mooncatcherwire.com/a2a \
  -H 'content-type: application/json' -H 'A2A-Version: 1.0' \
  -d '{"jsonrpc":"2.0","id":1,"method":"SendMessage","params":{"message":
       {"messageId":"m1","role":"ROLE_USER","parts":[{"text":"top"}]}}}'

Card: /.well-known/agent-card.json.

What is kept

A daily count of calls per tool and per client name (as the client reports it at initialize), a coarse client family from the User-Agent, and, for the rate limit, a salted hash of your IP address that changes every day. A call made without an account writes no IP address and no User-Agent string to this service's database. The rate-limit rows are deleted after 35 days and the daily counts after 90. Cloudflare, which hosts the service, keeps its own request logs for us. Registering an OAuth app (no account needed) stores the IP address it registered from, and approving it stores the approving IP address, with the sign-in's IP address and browser details. The IP addresses stored with the app and with the approval are removed after 90 days. All of this is described in the Privacy policy.

Register your agent (optional)

You never need to: everything above works with no header. But an agent can register itself, with no account and no person present, and get its own read-only credential: POST /agent/identity with {"type":"anonymous"}, then exchange the signed assertion it gets back at /oauth/token. Its calls are then counted per registration instead of per IP, which helps when a hosted client shares an address. A person with an account can later claim the registration by opening the link the agent gives them, signing in and typing its six-digit code, and can revoke it from the portal. The steps are in auth.md.

With an account (optional)

OAuth 2.1 is still there for people who have a Moon Catcher Wire account and want their agent's calls tied to it; signed-in calls are not subject to the limits above and, on the MCP server, read the live board (the A2A endpoint answers every caller from the stored board). Most clients only offer to sign in when a server refuses them with 401, which this server no longer does to a request without a token, so signing in needs a client that starts OAuth on its own. A client that sends a token must send a valid one: an invalid or expired token is refused with 401, never served as anonymous. The flow (dynamic client registration, PKCE, scope news:read) is in auth.md.

For machines

The board · Archive · Blog