CryptoWatch for AI agents

Ask your AI about Bitcoin.

It answers with CryptoWatch’s dated read: the posture, the evidence and what would change it. Read-only, free, Bitcoin only.

https://cryptowatch.id/mcp Connect

01Ask your agent

Short answerEach question has one tool. Your agent starts with the morning brief, then calls the tool for the question you ask.

02Connect

Short answerSign in to a CryptoWatch account, add https://cryptowatch.id/mcp to your AI client and approve the mcp:read request. Then ask it to call cw.morning_brief.

This page explains the setup; it cannot install a connector into a personal ChatGPT or Claude account. A registered CryptoWatch user approves every connection and can revoke it in Account.

ClaudeCustom connector
  1. Open Customize → Connectors, then + → Add custom connector.
  2. Enter https://cryptowatch.id/mcp and select Add.
  3. Approve access with your CryptoWatch account.

No custom connectors on your plan? Use Claude Code (CLI tab).

ChatGPTCustom MCP server
  1. Open Plugins, then + → Add custom MCP server.
  2. Name it CryptoWatch, enter https://cryptowatch.id/mcp, choose OAuth.
  3. Approve access, then pick it with @ in a conversation.

There is no public ChatGPT directory listing yet. Workspace settings can block custom servers. After a tool update, refresh the plugin and start a new conversation.

CodexSettings → MCP servers
  1. Add a Streamable HTTP server with https://cryptowatch.id/mcp.
  2. Save, then select Authenticate and approve access.
CLICodex CLI · Claude Code 
codex mcp add cryptowatch --url https://cryptowatch.id/mcp
codex mcp login cryptowatch --scopes mcp:read

claude mcp add --transport http --scope user cryptowatch https://cryptowatch.id/mcp
# then run /mcp in Claude Code and finish OAuth
API keyOnly when OAuth is not supported

Create a key in Account; it is shown once and belongs to your account. X-API-Key is CryptoWatch’s HTTP header name, not an X (social platform) API credential. Send OAuth or a key, never both, and keep keys out of chat.

{ "mcpServers": { "cw": { "type": "http",
  "url": "https://cryptowatch.id/mcp",
  "headers": { "X-API-Key": "cw_YOUR_KEY" } } } }
If setup stops
401 bearer token required
Finish OAuth for your account, or send an Account key.
No OAuth option
Use the API key tab.
Connected, no answer
Ask for cw.morning_brief first.
Remove access
Revoke the connection or key in Account.

03Every answer includes

Short answerThe same five things, so your agent can say how current the answer is and which posture it sits under.

status
ok, partial or unavailable. Partial names what is missing.
as_of
The day the evidence describes. generated_at is when it was computed.
freshness
One row per source. Unknown stays unknown.
authority
Today’s posture from Bitcoin State. No other tool can override it; if State is unusable it reads WAIT.
schema
A versioned name such as cw.cycle/1, published as each tool’s output schema.

04Tools

Short answerEleven tools, one per question. This table is built from the server’s own tool list.

11 read-only tools · 16 older names still answer until they are retired.

ToolQuestionSizePast daysREST
cw.morning_briefWhat should I know today?≤ 50 KBCurrent only/api/public/v1/morning-brief
cw.bitcoin_stateWhat is the posture and today's plan?≤ 15 KBYes/api/public/v1/bitcoin-state?view=compact
cw.cycleWhere are we in the cycle? Has the bottom happened?≤ 12 KBYes/api/public/v1/sections/cycle
cw.moneyWho is buying or selling? Where are the coins?≤ 12 KBYes/api/public/v1/sections/money
cw.macroIs the backdrop helping or hurting?≤ 12 KBYes/api/public/v1/sections/macro
cw.actionHow far could it fall, where would I add, is timing aligned?≤ 12 KBYes/api/public/v1/sections/action
cw.scoresHow is the score built and how far can I trust it?≤ 12 KBYes/api/public/v1/sections/scores
cw.historyWhat did CryptoWatch say on a date, and how did it score?≤ 10 KBYes/api/public/v1/composite/dates · bitcoin-state?as_of= · calibration
cw.snapshotGive me the raw evidence for an audit.full by defaultYes/api/public/v1/snapshot?sections=
cw.mstr_mnavIs MSTR cheap or expensive to its bitcoin?≤ 10 KBCurrent only/api/public/v1/mstr/mnav (compatibility)
cw.dca_backtestHow would steady buying have done?≤ 10 KBCurrent only/api/public/v1/dca/backtest (compatibility)
Older tool names

They still answer, unchanged, with a deprecation note. They will stop once nobody calls them.

cw.daily_verdict
Use cw.bitcoin_state
cw.thesis_receipt
Use cw.bitcoin_state
cw.action_plan
Use cw.action
cw.calibration_report
Use cw.history(view="calibration")
cw.regime_state
Use cw.cycle
cw.market_compass
Use cw.macro
cw.cw_risk_suite
Use cw.scores
cw.tail_risk_register
Use cw.macro(include_structural=true)
cw.daily_read
Use cw.morning_brief
cw.holder_divergence
Use cw.money
cw.capital_rotation
Use cw.money
cw.macro_beta_mode
Use cw.macro
cw.retail_capitulation
Use cw.cycle
cw.three_layer_alignment
Use cw.cycle
cw.bottoming_process
Use cw.cycle
cw.bear_market_clocks
Use cw.cycle

Full tool list with schemas (JSON) · Usage contract

05Limits

Short answerResearch, not orders. Free within rate limits.

Research only
No trades, custody or transfers. Levels and plan legs are context, not orders.
Fails closed
Missing evidence stays unavailable; nothing is filled in from another day.
Bitcoin only
Older ETH, SOL and HYPE calls return unavailable.
Free
No paid lane. 120 requests a minute per account.

06REST and webhooks

Every tool has a REST twin with the same answer, listed in the table. The OpenAPI 1.3.0 file is the stable contract. Webhooks (/api/public/v1/webhooks) need a key with webhooks:manage; see the docs.

07What changed