Mooncatcher Wire MCP server
com.mooncatcherwire/wiremooncatcherwire.comstreamable-httpv1.0.0Scanned
Free crypto news for agents: top stories by market impact, search, topics, AI digest.
12 tools: 6 change things and 6 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
6 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Mooncatcher Wire MCP server can do
The Mooncatcher Wire MCP server is published by mooncatcherwire.com, a domain the MCP Registry verified. It has 12 tools. It can create or change data (6 tools: mcw-signals-overview, mcw-signals-market-data, mcw-signals-charts, mcw-signals-meta and 2 more), but cannot delete data. 6 tools only read.
1 tool brings in text other people can write (mcw-get-story).
The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 13, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
12 tools
Changes things 6Claude Code: ask
mcw-signals-chartsBitcoin only, beta.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Bitcoin signals: chart
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
mcw-signals-market-dataBitcoin only, beta.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The description is 2,031 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...t, and its verdict on each price feed in mcw-signals-meta. Not investment advice."
Description, as the server wrote it 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.
Annotations the server declares
- title: Bitcoin signals: market data
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
mcw-signals-metaBitcoin only, beta.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Bitcoin signals: freshness and sources
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
mcw-signals-overviewBitcoin only, beta.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Bitcoin signals: overview
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
mcw-signals-sentimentBitcoin only, beta.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Bitcoin signals: sentiment
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
mcw-signals-thesisBitcoin only, beta.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Bitcoin signals: thesis
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 6Show 6 read-only tools
mcw-get-boardThe current crypto news board: mood, counts, the top stories by market impact, and the AI digest.No findings
Why it is in this group
- The name "mcw-get-board" says "get": a word for reading.
Description, as the server wrote it The current crypto news board: mood, counts, the top stories by market impact, and the AI digest. This is what www.mooncatcherwire.com shows.
Annotations the server declares
- title: Get the Moon Catcher Wire board
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
mcw-get-digestThe AI-written market digest for the current board: overview, the bull/neutral/bear split, per-ticker takeaways and the clustered highlights.No findings
Why it is in this group
- The name "mcw-get-digest" says "get": a word for reading.
Description, as the server wrote it The AI-written market digest for the current board: overview, the bull/neutral/bear split, per-ticker takeaways and the clustered highlights.
Annotations the server declares
- title: Get the market digest
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
mcw-get-storyOne story in full by its id, including TSP's own review state and the Moon Catcher Wire editor state if one has been set.Reads text others writeNo findings
Why it is in this group
- The name "mcw-get-story" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get one story
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
mcw-list-storiesStories with filters.No findings
Why it is in this group
- The name "mcw-list-stories" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List stories
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
mcw-list-topicsThe Moon Catcher Wire topics and the rules behind them.No findings
Why it is in this group
- The name "mcw-list-topics" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List topics
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
mcw-searchCase-insensitive search over headlines and summaries of the current board.No findings
Why it is in this group
- The name "mcw-search" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Search the wire
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:42 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mooncatcherwire.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://mooncatcherwire.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mooncatcherwire.com/mcp: tools/list returned 12 tools to an anonymous client, including mcw-signals-overview (write), mcw-signals-market-data (write), mcw-signals-charts (write), mcw-signals-meta (write), mcw-signals-thesis (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
The description is 2,031 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...t, and its verdict on each price feed in mcw-signals-meta. Not investment advice."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools3 changed.~3 changedView diff
- Changed:mcw-signals-market-dataChanges thingsdescription
- Changed:mcw-signals-overviewChanges thingsdescription
- Changed:mcw-signals-thesisChanges thingsdescription
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http wire https://mooncatcherwire.com/mcpclaude mcp add --transport http wire https://mooncatcherwire.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__wire__mcw-get-board",
"mcp__wire__mcw-list-stories",
"mcp__wire__mcw-get-story",
"mcp__wire__mcw-search",
"mcp__wire__mcw-list-topics",
"mcp__wire__mcw-get-digest"
],
"ask": [
"mcp__wire__mcw-signals-overview",
"mcp__wire__mcw-signals-market-data",
"mcp__wire__mcw-signals-charts",
"mcp__wire__mcw-signals-meta",
"mcp__wire__mcw-signals-thesis",
"mcp__wire__mcw-signals-sentiment"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as wire. Review it before you use it.
Capability tags behind 1 rule
- mcp__wire__mcw-get-story untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.mooncatcherwire/wire/verify?hash=703ddf9d2365a6118b2207a624a6562672854a60d9df3fe5c68e884375a56c48" | jq -e '.changed == false'Pinned hash 703ddf9d2365, from Nov 13, 2026, 20:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.mooncatcherwire/wire/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.mooncatcherwire/wire)Source: MCP Registry. Synced Oct 21, 2026, 17:59 UTC.
Mooncatcher Wire MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Mooncatcher Wire MCP server safe?
- No scan can promise that. What its definitions show: 12 tools, 6 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Mooncatcher Wire MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Mooncatcher Wire MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Mooncatcher Wire MCP server have?
- 12 tools: 6 write, 6 read. mcw-signals-overview, mcw-signals-market-data, mcw-signals-charts, mcw-signals-meta, mcw-signals-thesis, mcw-signals-sentiment, mcw-get-board, mcw-list-stories and 4 more.
Does the Mooncatcher Wire MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Mooncatcher Wire MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Mooncatcher Wire MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Oct 31, 2026. Every change is on this page and in its Atom feed.