mooncatcherwire

endpoint

https://mooncatcherwire.com/mcp also at https://www.mooncatcherwire.com/mcp

door code

280f25b891b83676

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is mooncatcherwire live?

Yes — it answered the hub's last check (checked 39m ago). It answered 99% of checks over the last 30 days.

Is mooncatcherwire free to use?

Yes — the hub reached it with no key and no payment.

What tools does mooncatcherwire have?

12 tools: mcw-signals-charts, mcw-signals-meta, mcw-signals-sentiment, mcw-search, mcw-signals-overview, mcw-signals-thesis, mcw-signals-market-data, mcw-get-story, ….

Is mooncatcherwire safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• mcw-get-digest reads open 15h ago

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

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• mcw-list-stories reads open 12h ago

  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.

  mcp-tool

  123456789101112131415161718192021222324252627

  {
    "type": "object",
    "properties": {
      "limit": {
        "type": "integer",
        "default": 20,
        "maximum": 60,
        "minimum": 1
      },
      "topic": {
        "type": "string",
        "description": "a topic slug, e.g. crypto or ai"
      },
      "ticker": {
        "type": "string",
        "description": "e.g. BTC"
      },
      "since_hours": {
        "type": "number",
        "maximum": 168,
        "minimum": 0.5
      },
      "breaking_only": {
        "type": "boolean"
      }
    }
  }

  arguments 27 lines copy
• mcw-get-board reads open 15h ago

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

  mcp-tool

  1234567891011

  {
    "type": "object",
    "properties": {
      "limit": {
        "type": "integer",
        "default": 20,
        "maximum": 60,
        "minimum": 1
      }
    }
  }

  arguments 11 lines copy
• mcw-list-topics reads open 15h ago

  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.

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• mcw-signals-charts unknown never probed

  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.

  mcp-tool

  12345678910111213141516171819202122232425262728293031

  {
    "type": "object",
    "properties": {
      "bars": {
        "type": "integer",
        "default": 50,
        "maximum": 200,
        "minimum": 1,
        "description": "How many of the newest bars to return."
      },
      "timeframe": {
        "enum": [
          "1m",
          "3m",
          "5m",
          "15m",
          "30m",
          "1H",
          "2H",
          "4H",
          "6H",
          "8H",
          "12H",
          "1D",
          "1W"
        ],
        "type": "string",
        "default": "4H"
      }
    }
  }

  arguments 31 lines copy
• mcw-signals-meta unknown never probed

  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.

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• mcw-signals-sentiment unknown never probed

  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.

  mcp-tool

  12345678910

  {
    "type": "object",
    "properties": {
      "history": {
        "type": "boolean",
        "default": false,
        "description": "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)."
      }
    }
  }

  arguments 10 lines copy
• mcw-search reads unknown 12h ago

  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.

  mcp-tool

  1234567891011121314151617

  {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "default": 20,
        "maximum": 60,
        "minimum": 1
      },
      "query": {
        "type": "string"
      }
    }
  }

  arguments 17 lines copy
• mcw-signals-overview unknown never probed

  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.

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• mcw-signals-thesis unknown never probed

  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.

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• mcw-signals-market-data unknown never probed

  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-signals-meta. Not investment advice.

  mcp-tool

  12345678910

  {
    "type": "object",
    "properties": {
      "history": {
        "type": "boolean",
        "default": false,
        "description": "True returns every stored point of each series instead of the newest 3. The answer is about twice as large."
      }
    }
  }

  arguments 10 lines copy
• mcw-get-story reads unknown 12h ago

  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.

  mcp-tool

  1234567891011

  {
    "type": "object",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string"
      }
    }
  }

  arguments 11 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

1 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.