# Mooncatcher Wire (remote · mooncatcherwire.com)

Free crypto news for agents: top stories by market impact, search, topics, AI digest.

- Trust score: 80/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mooncatcherwire.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-mooncatcherwire-wire/mooncatcherwire.md), [page](https://verifymcp.io/servers/com-mooncatcherwire-wire/mooncatcherwire)

## Channel facts

- Endpoint: `https://mooncatcherwire.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2988 tokens (~249/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 79/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 38% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Mooncatcher Wire MCP server?

Mooncatcher Wire is a hosted endpoint at https://mooncatcherwire.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-mooncatcherwire-wire 'https://mooncatcherwire.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-mooncatcherwire-wire": {
      "url": "https://mooncatcherwire.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-mooncatcherwire-wire": {
      "type": "http",
      "url": "https://mooncatcherwire.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-mooncatcherwire-wire]
url = "https://mooncatcherwire.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mooncatcherwire-wire": {
      "type": "remote",
      "url": "https://mooncatcherwire.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-mooncatcherwire-wire --url 'https://mooncatcherwire.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-mooncatcherwire-wire:
    url: "https://mooncatcherwire.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-mooncatcherwire-wire": {
      "Transport": "http",
      "Url": "https://mooncatcherwire.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-mooncatcherwire-wire -t streamable-http -u 'https://mooncatcherwire.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-mooncatcherwire-wire": {
      "type": "http",
      "url": "https://mooncatcherwire.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 80, +1)

- [security] Stability: 0.97 → pass

### 2026-11-04 (score 79, −1)

- [functional] Stability: pass → 0.97

### 2026-10-28 (score 80, +1)

- [security] Stability: 0.97 → pass

### 2026-10-26 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 78, 0)

- [security] Tool “mcw-signals-market-data” rewrote its description, which is the text the model reads
- [security] Tool “mcw-signals-overview” rewrote its description, which is the text the model reads
- [security] Tool “mcw-signals-thesis” rewrote its description, which is the text the model reads

### 2026-10-24 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 76, 0)

- [security] Tool “mcw-signals-charts” rewrote its description, which is the text the model reads
- [security] Tool “mcw-signals-overview” rewrote its description, which is the text the model reads
- [security] Tool “mcw-signals-thesis” rewrote its description, which is the text the model reads

## MCP tools (12)

### `mcw-get-board` (~51 tokens)

Get the Moon Catcher Wire board

The current crypto news board: mood, counts, the top stories by market impact, and the AI digest. This is what www.mooncatcherwire.com shows.

Input parameters:

- `limit` (integer)

### `mcw-list-stories` (~140 tokens)

List stories

Stories with filters. `ticker` matches TSP's ticker tags (BTC, ETH, SOL…). `topic` matches a Moon Catcher Wire topic (see mcw-list-topics) — these are OUR keyword rules, not TSP's, because TSP has no topic model. `since_hours` bounds by publication time. `breaking_only` keeps just the high-impact wires.

Input parameters:

- `breaking_only` (boolean)
- `limit` (integer)
- `since_hours` (number)
- `ticker` (string): e.g. BTC
- `topic` (string): a topic slug, e.g. crypto or ai

### `mcw-get-story` (~46 tokens)

Get one story

One story in full by its id, including TSP's own review state and the Moon Catcher Wire editor state if one has been set.

Input parameters:

- `id` (string, required)

### `mcw-search` (~58 tokens)

Search the wire

Case-insensitive search over headlines and summaries of the current board. A query that equals a ticker tag (BTC, ETH, SOL…) also finds every story tagged with it.

Input parameters:

- `limit` (integer)
- `query` (string, required)

### `mcw-list-topics` (~59 tokens)

List topics

The Moon Catcher Wire topics and the rules behind them. These are ours: TSP classifies only by ticker, so a topic like "ai" is not representable upstream and is a keyword rule over the headline and summary here.

### `mcw-get-digest` (~41 tokens)

Get the market digest

The AI-written market digest for the current board: overview, the bull/neutral/bear split, per-ticker takeaways and the clustered highlights.

### `mcw-signals-overview` (~426 tokens)

Bitcoin signals: overview

Bitcoin only, beta. The BTC spot price with the change TSP reports beside it (`spot.delta_pct`, in percent; TSP says it is the exchange-reported change over a rolling day), the trend, direction and confidence on each of thirteen timeframes with their consensus, each timeframe's direction recomputed every minute (`live`), the bull, base and bear cases with their probabilities for three horizons (TSP's own labels for them, `most_probable_arm` and `dominant_case`, are defined in mcw-signals-thesis), and support and resistance by how often they recur. Direction and confidence only: no entry, target or stop is published. Every value carries its own observed time, and `freshness` says how old the snapshot is. Each horizon's inputs are judged at the moment of the answer, each series against its own cadence (judged_on[].cadence_check, and stale per input family; ETF flows by two days since their row was written, and max pain, which has no cadence, by six hours since its chain was captured, as stopped_refreshing judges them). TSP re-runs its timeframe rows about every ten minutes, though a round is sometimes skipped, and each row's `cadence_check` judges its analysis against that at the moment of the answer, its `ok` false past half an hour, three re-runs; `live.timeframes` gives each timeframe's direction recomputed every minute from candles by TSP's own rule (the live price against the mean of the last 20 closes; `distance_pct` is how far from it, in percent), or a null direction with `why`. `live.age_s` is its price's age (roughly 100 to 170 s on a working lane: the price is dated by its own one-minute bar, not when it was read) and `live.stale` is true past five minutes, judged at the moment of the answer; `live` is null when none is stored. Not investment advice.

### `mcw-signals-market-data` (~523 tokens)

Bitcoin signals: market data

Bitcoin only, beta. The BTC derivatives market: funding, open interest, liquidations, long/short, taker volume, ETF flows, options max pain and two fear and greed indexes from two publishers (each 0 to 100, 100 = extreme greed; `fear_greed` and `fear_greed_alternative`, each with its own reading, label and date, never averaged or combined), each with its own observed time and cadence. `stats` is TSP's open, high, low, close and range over its latest hourly bars, from `window_start` to `window_end` (TSP's window, not always 24 hours): `newest_partial` is true when the newest hour was still open when TSP read it, at `as_of` (null when not known), and `newest_bar_open` says whether it is open at the moment of the answer. Open interest comes for one contract (`instrument`, its venue in `exchange`) and for several together: `contracts` lists the perpetual contracts in that one figure, `contracts_unlisted` counts any leg it does not name, and `includes_single_contract` says whether the one contract is among them; a venue not shown here is null. `flow.retail` is the all-accounts long/short ratio (the global account ratio, by number of accounts), set against the top-trader position ratio. A pending ETF day has a null flow, never 0, whatever TSP's own word for it (tsp_status: reported, provisional or null). `stopped_refreshing` is true on ETF flows two days after their row was last written, and on max pain, which has no cadence of its own, six hours after its chain was captured. Clock verdicts (cadence_check, open_bucket.closed, newest_bar_open, stopped_refreshing, max pain's nearest expiry) are judged at the moment of the answer. By default the latest reading of every metric is complete and the back-history beside it is the newest 3 points per series; the answer's `history` block reports how many older points were left out. Set `history` to true for the full stored series. TSP's sentiment readings are in mcw-signals-sentiment, and its verdict on each price feed in mcw-sign…

Input parameters:

- `history` (boolean): True returns every stored point of each series instead of the newest 3. The answer is about twice as large.

### `mcw-signals-charts` (~477 tokens)

Bitcoin signals: chart

Bitcoin only, beta. One timeframe's analysis, its OHLCV candles and the support, resistance and FBB band levels the analysis lists. The analysis carries its own analyzed_at and `cadence_check` (its `ok` false past half an hour, three of TSP's ten-minute re-runs). `granularity` names the bars: 2H, 6H, 8H and 12H are built from TSP's 1h bars, and 1m, 3m, 5m and 15m have levels only, no bars (the finest bars the Signals run takes from TSP are 30m); `note` says so. A built series is judged on the 1h bars it is built from: its health and its freshness are the 1h series' (source_newest_bar_at and source_interval_ms say which bar and cadence). `bars` defaults to the newest 50 and accepts up to 200. The newest bar can carry a partial flag: when true it was read before it closed, ingested_at says when (null if not known), and its high, low and close are as of then. When TSP also marks it live, it has no ingested_at: its high, low and close are a live sample TSP took at as_of (null if not known; extremes is TSP's word for how its high and low were taken, sampled or null), and volume_ingested_at says when its volume was recorded (null if not known). On a built series, live, as_of and volume_ingested_at are its last 1h bar's: only its close is that sample, its high and low span the 1h bars it holds (extremes null), and its volume is their sum. A bar TSP makes from its sample before that interval's bar is recorded is left out, so a series ends at its newest recorded bar: partial is true there when TSP moved its flag from it onto the bar it made, or left it unlabelled with its volume recorded before it closed. Levels, not a trade plan. Not investment advice.

Input parameters:

- `bars` (integer): How many of the newest bars to return.
- `timeframe` (string)

### `mcw-signals-meta` (~169 tokens)

Bitcoin signals: freshness and sources

Bitcoin only, beta. When the BTC signals snapshot was made, how old its newest value is, whether it is degraded and why, and every source with its own observed time and whether it was carried from an earlier run. Also the beta and not-advice notice. It is the only one of the signals tools that is purely about the age of the data. Also TSP's own verdict on each BTC price feed (`feed_freshness`: `tsp_status` fresh, stale, errored or null, as of `verdict_at`, and `last_updated_at`, when TSP last wrote it) beside the Wire's own verdict for the same series (`wire_check`), with `verdicts_differ` true when the two disagree; neither replaces the other.

### `mcw-signals-thesis` (~344 tokens)

Bitcoin signals: thesis

Bitcoin only, beta. The bull, base and bear cases for three horizons (scalp, short and long), as the Signals page's Thesis tab shows them. For each horizon: `most_probable_arm`, TSP's own most probable case (bull, base, bear or none; null when not known), with `probabilities_tie` true when two or more cases share the highest probability, and TSP's pick among them then its own tie-break (null when a probability is missing); `dominant_case`, TSP's own label: the highest-probability case with price levels (bull, base, bear or none; null when not known; the levels themselves are not published), so it can name a different case from the most probable one; the aggregate confidence; and each case's action, its probability, whether it has a signal for its direction (`has_signal`) and whether TSP marks it degenerate. Each horizon's inputs are judged at the moment of the answer, each series against its own cadence (judged_on[].cadence_check, and stale per input family; ETF flows by two days since their row was written, max pain by six hours since its chain was captured). `horizon_timeframes` names the timeframe analyses each horizon is built from, and `timeframes` holds their rows, each with its own analyzed_at and `cadence_check` (its `ok` false past half an hour, three of TSP's ten-minute re-runs). Direction and probability only: no entry, target or stop is published, nor any of TSP's reasoning text. Not investment advice.

### `mcw-signals-sentiment` (~452 tokens)

Bitcoin signals: sentiment

Bitcoin only, beta. TSP's sentiment readings for BTC, each with its own time and none combined with another. `hourly`: TSP's hourly rollup (TSP says its sentiment is global by design: one TSP-wide series, not scoped to one org), its newest hourly buckets (up to 48), each with its `hour`, `mean_sentiment`, `stddev_sentiment` and `sample_count`; a bucket with fewer than `thin_below` readings is thin; a null mean is no data, never 0; an hour with no readings has no bucket; TSP rewrites an hour after it closes, and `newest_bucket_open` says whether the newest is still open at the moment of the answer. `ema`: TSP's 24-hour EMA of that rollup, each point with its `hour` and the `computed_at` TSP gives it. TSP says the scores run roughly -1 to 1; a score outside -1 to 1 is published as null (the Wire's filter). `news_index`: TSP's own daily news index (0 to 100, 100 = extreme greed), with TSP's label and `article_count`; a day with too few articles has a null value, never a low one. `blend`: TSP's blend, the `weighted_sentiment`, `confidence` and `source_count` of its canonical row over that row's own window (`window_start` to `window_end`); it is not a combination of the indexes. The hourly, EMA and news blocks each carry their own `cadence_check`, and the blend its `age_s` and `stale`, judged at the moment of the answer. By default each series is the newest 3 points; the answer's `history` block reports how many older points were left out. Set `history` to true for the full stored series. Not investment advice.

Input parameters:

- `history` (boolean): True returns every stored point of each series instead of the newest 3 (up to 48 hourly buckets, 24 EMA points and 30 days of the news index).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-mooncatcherwire-wire/mooncatcherwire#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 79
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 80
- 2026-10-28: 80
- 2026-10-27: 79
- 2026-10-26: 79
- 2026-10-25: 78
- 2026-10-24: 78
- 2026-10-23: 77
- 2026-10-22: 77
- 2026-10-21: 76
- 2026-10-20: 76
- 2026-10-19: 76
- 2026-10-18: 75
- 2026-10-17: 75
- 2026-10-16: 74
- 2026-10-15: 74
- 2026-10-14: 73
- 2026-10-13: 73
- 2026-10-12: 73
- 2026-10-10: 73
- 2026-10-04: 64
- 2026-10-03: 63
- 2026-10-02: 63
- 2026-10-01: 62

## Common questions

### What is the Mooncatcher Wire MCP server?

Mooncatcher Wire is an MCP server listed in the public MCP registry as com.mooncatcherwire/wire. Free crypto news for agents: top stories by market impact, search, topics, AI digest. This page covers its hosted endpoint (https://mooncatcherwire.com/mcp).

### Is the Mooncatcher Wire MCP server safe to use?

Mooncatcher Wire scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Mooncatcher Wire MCP server expose?

Mooncatcher Wire exposes 12 tools: mcw-get-board, mcw-list-stories, mcw-get-story, mcw-search, mcw-list-topics, and 7 more. Their descriptions and schemas cost roughly 2,786 tokens of context every time the server is loaded.

### Does the Mooncatcher Wire MCP server require authentication?

No. We connected to Mooncatcher Wire without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Mooncatcher Wire MCP server still maintained?

Mooncatcher Wire is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mooncatcherwire.com/mcp
- Website: https://www.mooncatcherwire.com/agents/
- Changelog RSS feed: https://verifymcp.io/servers/com-mooncatcherwire-wire/mooncatcherwire.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mooncatcherwire-wire/mooncatcherwire.json
- HTML version of this page: https://verifymcp.io/servers/com-mooncatcherwire-wire/mooncatcherwire