Five-decision morning brief
Start with cw.morning_brief. It returns one current headline plus Now, Cycle, Money, Macro, and Action, with material changes, the operator action, and invalidation.
decisions: 5
output: brief + changes + invalidation
CryptoWatch for AI AgentsHosted MCP
CryptoWatch turns the five decisions humans inspect — Now, Cycle, Money, Macro, and Action — into one machine-readable brief. The human Macro has 10 visible owners; specialist tools are evidence behind those owners, not extra panels. Connect your agent through the hosted MCP server and approve read-only access with your CryptoWatch account.
What agents get
Most agent stacks can fetch prices. They still need a disciplined read on cycle phase, macro permission, invalidation, and what would change the thesis. CryptoWatch packages that into compact responses an agent can cite, cache, and turn into work.
Start with cw.morning_brief. It returns one current headline plus Now, Cycle, Money, Macro, and Action, with material changes, the operator action, and invalidation.
The daily verdict carries the source-dated Bitcoin State read, evidence receipts, and explicit fail-closed limits. It does not invent calibrated probabilities, time windows, or exact targets when the evidence cannot support them.
Go deeper
The complete hosted toolset is grouped by the decision it supports. Each response stays read-only, source-gated, and explicit about missing or uncalibrated evidence. Cite the 10 visible owners on Macro. Folded evidence is a closed sibling receipt — one click, not a receipt inside another receipt.
Cycle Position read: current regime, valuation-band stack, key levels, and confidence.
tool: cw.regime_state
Closed receipt on Macro Permission. Binding constraint plus forward and standalone lenses — not a standalone Macro panel.
tool: cw.market_compass
Closed receipt on Cycle Position. Bottom state, confirmation, invalidation, and accumulation ladder — not a standalone Cycle Bottom Radar panel.
tool: cw.bottoming_process
Cycle Position Cowen receipt: stage, elapsed-time clock, price checklist, and path.
tool: cw.bear_market_clocks
Closed receipt on Cycle Position. Whether structure, flow, and positioning agree.
tool: cw.three_layer_alignment
Entity Regime / Liquidity evidence: tourist-versus-OG holder behavior and conviction.
tool: cw.holder_divergence
Closed receipt on Macro Permission. Cross-asset rotation state and the assets driving it.
tool: cw.capital_rotation
Macro Permission scoring input — not a standalone panel. Whether BTC is trading as macro beta, idiosyncratically, inversely, or mixed.
tool: cw.macro_beta_mode
Cycle / Entity evidence: multi-leg stress confluence, observed hits, and limitations.
tool: cw.retail_capitulation
BTC Setup: bias, zones, risk state, and the next condition that changes the plan.
tool: cw.action_plan
Cycle supporting (starts closed): risk score, valuation bands, and separation evidence.
tool: cw.cw_risk_suite
Machine-only. mNAV, scenarios, funding health, and freshness limits — not a Macro panel.
tool: cw.mstr_mnav
Research history. The live DCA map is a closed receipt on BTC Setup.
tool: cw.dca_backtest
Closed receipt on Macro Permission. Quantitative risks and attributed expert opinions in separate evidence tiers.
tool: cw.tail_risk_register
Timestamp, confidence, invalidation, and review window for durable agent memory.
tool: cw.thesis_receipt
Calibration evidence, scoring receipts, and explicit sample limitations.
tool: cw.calibration_report
The earlier six-screen Verdict · Why · Move contract remains available for existing consumers. It is not the current Macro canvas (Now · Cycle · Money · Macro · Action plus Proof) and is not the recommended entry point.
tool: cw.daily_read
Every published snapshot block, including all syntheses, freshness, and availability fields. Start with the brief; use this only when your agent needs the full evidence payload.
tool: cw.snapshot
Connect
Create or sign in to your CryptoWatch account first. Then choose a client, add the hosted Streamable HTTP endpoint, and approve the mcp:read OAuth request. A developer API key is an account-owned fallback for clients that cannot complete OAuth.
Start here · 3 steps
The website explains the setup; it does not install a connector into a personal ChatGPT or Claude account. Every connection is approved by a registered CryptoWatch user and can be reviewed or revoked from Account.
Use the same CryptoWatch account that should own this connection. OAuth is the normal path; no key is needed.
Open Account →Pick Codex, Claude, a ChatGPT workspace app, or a terminal client below. Use the exact hosted endpoint shown in the panel.
After approval, ask the agent to call cw.morning_brief. A successful response contains the five current decisions and an invalidation.
https://cryptowatch.id/mcp.Sign in or create your CryptoWatch account when Codex opens the OAuth approval screen. If the OAuth window does not open, use the CLI steps or the Account-managed key fallback below.
https://cryptowatch.id/mcp.Sign in or create your CryptoWatch account when Claude opens the OAuth approval screen. If your Claude plan does not show custom connectors, use Claude Code or another compatible MCP client.
Public listing: There is no active public ChatGPT directory listing or one-click website installer for CryptoWatch. The button on this page opens instructions only; it cannot install a connector into a personal ChatGPT or Claude account.
Business / Enterprise / Edu: A workspace admin can add CryptoWatch as a custom MCP app. In ChatGPT, open Workspace settings → Permissions & Roles → Connected Data Developer mode / Create custom MCP connectors, create an app with https://cryptowatch.id/mcp, choose OAuth, scan the tools, and publish it for permitted members. Each member then signs in or creates their own CryptoWatch account in the approval window.
If the Developer Mode or custom-connector option is missing, the workspace plan or admin policy does not allow it yet. ChatGPT availability and labels can change as OpenAI rolls out MCP support.
Use Streamable HTTP at https://cryptowatch.id/mcp with OAuth scope mcp:read. Sign in or create your registered CryptoWatch account when your client opens the approval window, then start with cw.morning_brief.
# Codex CLI codex mcp add cryptowatch --url https://cryptowatch.id/mcp codex mcp login cryptowatch --scopes mcp:read codex mcp list # Start Codex and ask: call cw.morning_brief # Claude Code claude mcp add --transport http --scope user cryptowatch https://cryptowatch.id/mcp # Start Claude Code, run /mcp, then complete OAuth in the browser. # Verify with: claude mcp list
Use this only when OAuth is not supported. X-API-Key is CryptoWatch's HTTP header name; it is not an X (social platform) API credential.
{
"mcpServers": {
"cw": {
"type": "http",
"url": "https://cryptowatch.id/mcp",
"headers": {
"X-API-Key": "cw_YOUR_KEY"
}
}
}
}
Sign in to CryptoWatch, then create and manage your developer key from Account. Every developer key belongs to your account, and you or an administrator can revoke it. Never paste a key into chat or commit it to a repository.
# Use only when your client cannot complete OAuth # transport: streamable-HTTP # endpoint: https://cryptowatch.id/mcp # header: X-API-Key: cw_YOUR_KEY # (no key -> 401 Unauthorized)
X-API-Key.cw.morning_brief first, then inspect cw.snapshot only when full evidence is required.# Create a webhook subscription
curl -X POST https://cryptowatch.id/api/public/v1/webhooks \
-H "X-API-Key: $CRYPTOWATCH_API_KEY" \
-H 'Content-Type: application/json' \
-d '{"url":"https://example.com/cw","events":["composite.changed"]}'
# List subscriptions and delivery status
curl -H "X-API-Key: $CRYPTOWATCH_API_KEY" \
https://cryptowatch.id/api/public/v1/webhooks
# Human guide https://cryptowatch.id/docs#api # OpenAPI 3.1 https://cryptowatch.id/api/public/openapi.json
Access
The hosted MCP is free and rate-limited per connected credential for abuse control. There are no paid tiers, prepaid credits, payment challenges, or subscription upgrades.
The agent starts with cw.morning_brief, then calls a specialist tool only when one decision needs deeper evidence.
The call returns against a rate limit tied to the connected account or developer key. No charge and no payment challenge.
CryptoWatch returns the macro answer, receipt fields, confidence, invalidation, and next-check trigger in a compact JSON contract.
The agent stores the response as a dated market belief instead of blending it into vague chat history.
Agents never need a wallet, prepaid balance, subscription, or payment receipt to call a hosted tool.
Per-credential rate limits protect service quality without turning access into a paywall.
Dashboard artifacts
CryptoWatch is not selling a black-box label. The agent response points back to the same terminal evidence: cycle heat, scenario bands, accountability logs, and thesis changes.
Composite regime, BTC reference, risk posture, and the current action read in one scan.
Phase context with historical base rates and whether today's setup is early, mid, late, or overheated.
Realized-price allocation zones with explicit triggers, invalidation, and historical policy comparison.
Illustrative product snapshots — values shown in these images are not live.
Moat
CryptoWatch's advantage is the synthesis layer: cycle history, macro permission, market stress, on-chain behavior, and accountability in one operating model. The agent gets a call it can defend instead of a loose pile of charts.
Early access
CryptoWatch for agents is a free hosted MCP server protected by account-owned OAuth and rate limits. The dashboard remains the human control room; agent access is the machine lane.