Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Central Command

REMOTE · RTCELWJNRBMFMRYWACKY.SUPABASE.CO

Crypto perps market data, backtests and BloFin trading agents. Free with a key or x402 per call.

+2 this week 78 Trust /100

Last scanned (18 hours ago)

Scores higher than 71% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Recent critical change

Authorization (14 Nov 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability72
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 9987 tokens (~322/item across 31 items; 27 tools + 4 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 27 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 29 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 16 Nov 26 +2
    • Stability: fail → pass ▲ security
  • 14 Nov 26 +10
    • Authorization: unverified → fail ▼ critical
    • Transport: fail → pass ▲ security
  • 13 Nov 26 −9
    • Authorization: fail → unverified ▼ security
    • Transport: pass → fail ▼ security
  • 12 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 5 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 17 Oct 26 0
    • A breaking change shipped without a version bump: still 1.2.0 ▼ security
    • Tool “cc.coinglass_footprint” was removed ▼ security
    • Tool “cc.hyperliquid_data” was removed ▼ security
    • Tool “cc.liquidation_heatmap” was removed ▼ security
    • Tool “cc.liquidation_max_pain” was removed ▼ security
    • Tool “cc.long_short_account_ratio” was removed ▼ security
    • Tool “cc.auto_fetch_market_data” rewrote its description, which is the text the model reads security
    • Tool “cc.cme_gap” rewrote its description, which is the text the model reads security
    • Tool “cc.coinglass_data” rewrote its description, which is the text the model reads security
    • Tool “cc.funding_rates” rewrote its description, which is the text the model reads security
    • Tool “cc.ma_fetch” rewrote its description, which is the text the model reads security
    • Tool “cc.open_interest” rewrote its description, which is the text the model reads security
    • Tool “cc.traditional_markets” rewrote its description, which is the text the model reads security
    • Schema quality: 11444 → 9932 ▲ functional
  • 14 Oct 26 0
    • Stability: pass → fail ▼ security
    • A breaking change shipped without a version bump: still 1.2.0 ▼ security
    • Tool “cc.squirrel_chat_v2” was removed ▼ security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://rtcelwjnrbmfmrywacky.supabase.co/functions/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=supabase.co CN=WE1,O=Google Trust Services,C=US 24 Oct 2026 22 Jan 2027 ECDSA 256 ECDSA-SHA256 d2b50611cd88e9c50e4e2231f4d3f059
SANs: supabase.co, *.supabase.co
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of rtcelwjnrbmfmrywacky.supabase.co. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
co. DS published 7786 8 Verified
supabase.co. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://rtcelwjnrbmfmrywacky.supabase.co/functions/v1/mcp Verified 200
http (plaintext) http://rtcelwjnrbmfmrywacky.supabase.co/functions/v1/mcp HTTPS enforced 301 https://rtcelwjnrbmfmrywacky.supabase.co/functions/v1/mcp
MCP tools · 27 exposed · ~9,692 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
cc.agent_strategy ~519

Run the Central Command agent console (strategy lifecycle + account actions). Purpose: guide/whoami, create/update strategies, backtest, deploy STOPPED, paper execute, and (explicitly) live orders. Behavior: READ + WRITE. Deploy without execute does NOT move money. Live place_order/close_position/cancel_order require confirm_live=true. Default force_paper=true. Auth: X-Api-Key (linked Connect keys preferred — free). Do not spoof X-Linked-User-Id. Cost: linked Connect keys free; otherwise prepaid / x402 per catalog price for agent-strategy. Rate limit: plan default. Returns: JSON envelope { ok, endpoint, status, data: { ok, guide|whoami|created|deployed|... } }. Guidelines: Start with action=guide then whoami. Prefer paper. Never invent outbound-proxy failures — report real HTTP status/body.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same as X-PAYMENT header) when retrying after 402. Optional.
actionstringyesRequired intent. Safe/read: guide, whoami, strategies, get_strategy, portfolio, positions, orders, balance, results, logs, get_backtest. Write (no live money): create_strategy, update_strategy, deplo…
bodyobject–Full JSON body merge/override for advanced fields. Optional.
confirm_liveboolean–Must be true to place/cancel LIVE exchange orders. Never set unless the human explicitly confirmed. Optional.
force_paperboolean–When true (recommended default), execute paths stay on paper. Optional.
goalstring–Natural-language strategy goal / rules. Optional.
idstring–Strategy id for get/update/deploy/execute/backtest. Optional.
settingsobject–For update_strategy: { strategy_config: {max_leverage, max_risk_per_trade_pct, max_concurrent_positions, asset_universe, ...}, capital_config, check_interval_minutes, trading_permissions }. Hot-edita…
task_typestring–Task classification for create_strategy. Prefer "paper". Optional.
titlestring–Strategy title when creating/updating. Optional.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

cc.asset_scanner ~338

Call cc.asset_scanner — Scans 36 major crypto assets across BTC, ETH, SOL, alts, and memes for multi-timeframe technical signals including RSI, MACD, Bollinger Bands, ATR, and composite scores. Purpose: Scans 36 major crypto assets across BTC, ETH, SOL, alts, and memes for multi-timeframe technical signals including RSI, MACD, Bollinger Bands, ATR, and composite scores. Behavior: READ-ONLY. Does not place orders, move funds, or mutate your exchange account. Responses may be cached (~1800s). Auth: X-Api-Key or x402 payment proof (X-PAYMENT / __x_payment). Anonymous unauthenticated calls receive HTTP 402 with payment accepts. Cost: $0.002 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 60/min (per API key). Tier: standard. Returns: Array of per-symbol objects with indicator values, directional scores, and signal strength ratings. Cached 30 minutes. Guidelines: Use for research / signal context. Pair with cc.agent_strategy (paper) before any live order. Do not invent fills from this data alone. Tags: crypto, technical-analysis, scanner, multi-asset, signals.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

cc.auto_fetch_market_data ~345

Call cc.auto_fetch_market_data — All-in-one market context for agents: BloFin OHLCV candles, indicators computed by Central Command, BloFin open interest and news. Purpose: All-in-one market context for agents: BloFin OHLCV candles, indicators computed by Central Command, BloFin open interest and news. Behavior: READ-ONLY. Does not place orders, move funds, or mutate your exchange account. Responses may be cached (~300s). Auth: X-Api-Key or x402 payment proof (X-PAYMENT / __x_payment). Anonymous unauthenticated calls receive HTTP 402 with payment accepts. Cost: $0.008 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 15/min (per API key). Tier: premium. Returns: Multi-section response: technical indicators, OHLCV data, market microstructure (OI/funding), and relevant news summaries. Guidelines: Compute / parse / backtest only — no live orders. Feed outputs into cc.agent_strategy with force_paper=true to paper-trade. Tags: comprehensive, market-data, indicators, news, context, all-in-one.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.
symbolstringyesParameter `symbol` (string). Required.
timeframestring–default: 1h Optional.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

cc.blofin_public ~348

Call cc.blofin_public — Proxy to BloFin public API (tickers, instruments, orderbook, trades, candles) bypassing CORS restrictions. Purpose: Proxy to BloFin public API (tickers, instruments, orderbook, trades, candles) bypassing CORS restrictions. Behavior: READ-ONLY. Does not place orders, move funds, or mutate your exchange account. Responses may be cached (~60s). Auth: X-Api-Key or x402 payment proof (X-PAYMENT / __x_payment). Anonymous unauthenticated calls receive HTTP 402 with payment accepts. Cost: $0.0005 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 120/min (per API key). Tier: standard. Returns: Raw BloFin public API response for any public endpoint: real-time tickers, full orderbook depth, recent trades, OHLCV candles. Guidelines: Pass required parameters exactly; omit unknown fields. On 402, settle payment then retry with X-PAYMENT. Tags: blofin, orderbook, tickers, candles, exchange-data.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.
paramsobject–Parameter `params` (object). Optional.
pathstringyesBloFin API path e.g. /api/v1/market/tickers Required.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

cc.central_signal ~352

Call cc.central_signal — Unified signal ingestion endpoint that normalizes symbols from any exchange format (Binance, Bybit, TradingView) to executable format and routes to execution. Purpose: Unified signal ingestion endpoint that normalizes symbols from any exchange format (Binance, Bybit, TradingView) to executable format and routes to execution. Behavior: DESTRUCTIVE. Normalizes the signal and routes toward trade execution for the authenticated account. Can open/close positions. Auth: X-Api-Key required (and linked exchange credentials for execution actions). Cost: $0.01 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 30/min (per API key). Tier: premium. Returns: Signal confirmation with execution status, order ID, fill price, and routing metadata. Guidelines: Use for research / signal context. Pair with cc.agent_strategy (paper) before any live order. Do not invent fills from this data alone. Tags: signals, execution, routing, tradingview, webhook, automation.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.
leveragenumber–Parameter `leverage` (number). Optional.
sidestringyesbuy or sell Required.
sizenumberyesParameter `size` (number). Required.
symbolstringyesAny format: BTCUSDT, BTC/USDT, BTC-USDT Required.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

cc.cme_gap ~309

Call cc.cme_gap — CME Bitcoin futures weekend gaps (Friday close vs Monday open) and their fill status, computed by Central Command from BloFin candles. Purpose: CME Bitcoin futures weekend gaps (Friday close vs Monday open) and their fill status, computed by Central Command from BloFin candles. Behavior: READ-ONLY. Does not place orders, move funds, or mutate your exchange account. Responses may be cached (~1800s). Auth: X-Api-Key or x402 payment proof (X-PAYMENT / __x_payment). Anonymous unauthenticated calls receive HTTP 402 with payment accepts. Cost: $0.002 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 30/min (per API key). Tier: premium. Returns: Array of detected gaps: direction, size, fill status, and dates. Gaps act as price magnets. Guidelines: Use for research / signal context. Pair with cc.agent_strategy (paper) before any live order. Do not invent fills from this data alone. Tags: cme, gaps, futures, price-magnets, institutional.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

cc.coinglass_data ~346

Call cc.coinglass_data — BloFin derivatives data: BloFin open interest and funding, and a bulk scan of BloFin tickers and funding. Paid calls carry BloFin and public-domain (CFTC) data only. Purpose: BloFin derivatives data: BloFin open interest and funding, and a bulk scan of BloFin tickers and funding. Paid calls carry BloFin and public-domain (CFTC) data only. Behavior: READ-ONLY. Does not place orders, move funds, or mutate your exchange account. Responses may be cached (~2700s). Auth: X-Api-Key or x402 payment proof (X-PAYMENT / __x_payment). Anonymous unauthenticated calls receive HTTP 402 with payment accepts. Cost: $0.003 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 30/min (per API key). Tier: standard. Returns: Normalized market microstructure data across top crypto perpetual futures. Guidelines: Use for research / signal context. Pair with cc.agent_strategy (paper) before any live order. Do not invent fills from this data alone. Tags: derivatives, open-interest, liquidations, funding, coinglass.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.
symbolstring–Specific symbol to query (default: top 20) Optional.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

cc.data_tools ~685

Call cc.data_tools — Comprehensive TA computation engine: 25+ indicators (SMA, EMA, RSI, MACD, ATR, Bollinger, Stochastic, ADX, CCI, Ichimoku, VWAP, Volume Profile, Fibonacci, Pivots, etc.) on any OHLCV data, plus the terminal's Smart Overlays (action smart_overlays: supply/demand zones, No-Trade Zone, EMA ribbon 8/13/21/34/55/89, FVG, liquidity sweeps) computed from the same code the chart draws. Purpose: Comprehensive TA computation engine: 25+ indicators (SMA, EMA, RSI, MACD, ATR, Bollinger, Stochastic, ADX, CCI, Ichimoku, VWAP, Volume Profile, Fibonacci, Pivots, etc.) on any OHLCV data, plus the terminal's Smart Overlays (action smart_overlays: supply/demand zones, No-Trade Zone, EMA ribbon 8/13/21/34/55/89, FVG, liquidity sweeps) computed from the same code the chart draws. Behavior: READ-ONLY. Does not place orders, move funds, or mutate your exchange account. Live / near-real-time data. Auth: X-Api-Key or x402 payment proof (X-PAYMENT / __x_payment). Anonymous unauthenticated calls receive HTTP 402 with payment accepts. Cost: $0.005 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 30/min (per API key). Tier: standard. Returns: Full indicator suite output for all requested tools: computed values, signals, divergences, and crossovers at every data point. Guidelines: Compute / parse / backtest only — no live orders. Feed outputs into cc.agent_strategy with force_paper=true to paper-trade. Tags: indicators, technical-analysis, computation, rsi, macd, bollinger, ichimoku, fibonacci.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.
actionstring–calculate_indicators (default) | compute_all_indicators | detect_patterns | analyze_regime | multi_timeframe_regime | find_support_resistance | cross_tf_analysis | evaluate_expressions | full_analysi…
barsnumber–Candles to analyse (default 100; use 300 for smart_overlays so the zone lookback matches the chart) Optional.
candlesarray–Provide your own OHLCV data instead of fetching Optional.
indicatorsarray–For calculate_indicators: list of indicators to compute, TYPE:PERIOD Optional.
overlaysarray–For smart_overlays: supply_demand | no_trade_zone | ema_ribbon (default all three) | fvg | liquidity_sweeps | rainbow Optional.
symbolstringyesParameter `symbol` (string). Required.
timeframestringyesParameter `timeframe` (string). Required.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

cc.economic_calendar ~314

Call cc.economic_calendar — Upcoming high-impact macroeconomic events (CPI, FOMC, NFP, etc.) with forecast vs previous values. 60-min cache. Purpose: Upcoming high-impact macroeconomic events (CPI, FOMC, NFP, etc.) with forecast vs previous values. 60-min cache. Behavior: READ-ONLY. Does not place orders, move funds, or mutate your exchange account. Responses may be cached (~3600s). Auth: X-Api-Key or x402 payment proof (X-PAYMENT / __x_payment). Anonymous unauthenticated calls receive HTTP 402 with payment accepts. Cost: $0.001 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 60/min (per API key). Tier: standard. Returns: Array of events with dates, countries, impact level, forecast/actual/previous values. Guidelines: Use for research / signal context. Pair with cc.agent_strategy (paper) before any live order. Do not invent fills from this data alone. Tags: macro, calendar, fomc, cpi, nfp, economic.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

cc.etf_flows ~319

Call cc.etf_flows — Real-time Bitcoin/crypto ETF inflow and outflow data tracking institutional positioning (GBTC, IBIT, FBTC, etc). 60-min cache. Purpose: Real-time Bitcoin/crypto ETF inflow and outflow data tracking institutional positioning (GBTC, IBIT, FBTC, etc). 60-min cache. Behavior: READ-ONLY. Does not place orders, move funds, or mutate your exchange account. Responses may be cached (~3600s). Auth: X-Api-Key or x402 payment proof (X-PAYMENT / __x_payment). Anonymous unauthenticated calls receive HTTP 402 with payment accepts. Cost: $0.002 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 30/min (per API key). Tier: standard. Returns: Per-ETF daily flow in USD with cumulative totals, showing institutional demand/supply dynamics. Guidelines: Use for research / signal context. Pair with cc.agent_strategy (paper) before any live order. Do not invent fills from this data alone. Tags: etf, institutional, flows, bitcoin, blackrock, grayscale.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

cc.external_signal ~321

Call cc.external_signal — Public-facing webhook endpoint for TradingView alerts, custom bots, and third-party signal providers. Normalizes and forwards to execution. Purpose: Public-facing webhook endpoint for TradingView alerts, custom bots, and third-party signal providers. Normalizes and forwards to execution. Behavior: DESTRUCTIVE. Normalizes the signal and routes toward trade execution for the authenticated account. Can open/close positions. Auth: X-Api-Key required (and linked exchange credentials for execution actions). Cost: $0.005 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 60/min (per API key). Tier: standard. Returns: Proxied execution response: signal received, validated, normalized, and forwarded to trade engine. Guidelines: Use for research / signal context. Pair with cc.agent_strategy (paper) before any live order. Do not invent fills from this data alone. Tags: webhook, tradingview, alerts, automation, signals.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.
actionstringyesbuy, sell, close Required.
sizenumber–Parameter `size` (number). Optional.
symbolstringyesParameter `symbol` (string). Required.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

cc.fear_greed ~313

Call cc.fear_greed — Crypto market Fear & Greed composite index (0-100) with historical values and trend direction. 30-min cache. Purpose: Crypto market Fear & Greed composite index (0-100) with historical values and trend direction. 30-min cache. Behavior: READ-ONLY. Does not place orders, move funds, or mutate your exchange account. Responses may be cached (~1800s). Auth: X-Api-Key or x402 payment proof (X-PAYMENT / __x_payment). Anonymous unauthenticated calls receive HTTP 402 with payment accepts. Cost: $0.0005 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 120/min (per API key). Tier: standard. Returns: Current index value (0=extreme fear, 100=extreme greed) plus 7/30/90 day history. Guidelines: Use for research / signal context. Pair with cc.agent_strategy (paper) before any live order. Do not invent fills from this data alone. Tags: sentiment, fear-greed, market-cycle, contrarian.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

cc.funding_rates ~323

Call cc.funding_rates — BloFin perpetual funding rate for a coin (percent per 8h), current and 90-period history. Paid calls carry BloFin data only. Purpose: BloFin perpetual funding rate for a coin (percent per 8h), current and 90-period history. Paid calls carry BloFin data only. Behavior: READ-ONLY. Does not place orders, move funds, or mutate your exchange account. Responses may be cached (~1800s). Auth: X-Api-Key or x402 payment proof (X-PAYMENT / __x_payment). Anonymous unauthenticated calls receive HTTP 402 with payment accepts. Cost: $0.001 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 60/min (per API key). Tier: standard. Returns: Per-symbol funding rate data with exchange-level breakdowns and predicted next funding. Guidelines: Use for research / signal context. Pair with cc.agent_strategy (paper) before any live order. Do not invent fills from this data alone. Tags: funding, perpetuals, carry-trade, sentiment.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.
symbolstring–Specific symbol (default: all major) Optional.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

cc.indicator_generator ~530

Call cc.indicator_generator — AI-powered indicator workshop. Actions: generate (prompt→code), list_library (user saved indicators), get_indicator (by id), delete_indicator, get_draft (poll generation status), save (persist to library). Returns full indicator code, params, and metadata. Purpose: AI-powered indicator workshop. Actions: generate (prompt→code), list_library (user saved indicators), get_indicator (by id), delete_indicator, get_draft (poll generation status), save (persist to library). Returns full indicator code, params, and metadata. Behavior: READ-ONLY. Does not place orders, move funds, or mutate your exchange account. Live / near-real-time data. Auth: X-Api-Key or x402 payment proof (X-PAYMENT / __x_payment). Anonymous unauthenticated calls receive HTTP 402 with payment accepts. Cost: $0.02 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 10/min (per API key). Tier: premium. Returns: For generation: {success, processing, generation_id}. For list_library: {indicators:[{id, name, description, code, color, is_overlay, params}]}. For get_draft: {draft, status, generation_id}. Guidelines: Pass required parameters exactly; omit unknown fields. On 402, settle payment then retry with X-PAYMENT. Tags: indicator, code-generation, ai, custom, technical-analysis, charting.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.
actionstring–list_library | get_indicator | delete_indicator | get_draft | save. Omit for generation. Optional.
historyarray–Conversation history for refinement Optional.
indicator_dataobject–Full indicator object to save: {name, description, code, color, is_overlay, params} Optional.
indicator_idstring–UUID of indicator (for get/delete actions) Optional.
promptstring–Natural language description of indicator to generate (required for generation) Optional.
saveboolean–Set true with indicator_data to persist to library Optional.
timeframestring–Chart timeframe context (e.g. 4H, 1D) Optional.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

cc.list_catalog ~144

List Central Command x402 catalog endpoints (names, prices, parameters, tiers). Purpose: discover which cc.* tools exist and what they cost before calling them. Behavior: READ-ONLY. Does not place orders or charge per-endpoint fees by itself (catalog fetch). Auth: optional X-Api-Key (same catalog is public); payment not required for listing. Cost: free to list. Individual endpoint calls are billed separately when invoked. Rate limit: gateway default. Returns: JSON envelope { ok, endpoint, status, data: { endpoints: [...] } }. Guidelines: Call this first. Then invoke cc.<slug> with required params. Admin-only tools are omitted.

Input schema present but exposes no named parameters.

NameTypeReqDescription
dataobjectyesFull catalog payload from /x402-gateway/catalog.
endpointstringyesAlways list_catalog.
errorstring––
okbooleanyesTrue when catalog fetch succeeded.
statusnumberyesHTTP status of catalog fetch.

No examples provided.

cc.ma_fetch ~319

Call cc.ma_fetch — Multi-period moving averages (SMA/EMA at several lengths) computed by Central Command from BloFin perpetual candles. Purpose: Multi-period moving averages (SMA/EMA at several lengths) computed by Central Command from BloFin perpetual candles. Behavior: READ-ONLY. Does not place orders, move funds, or mutate your exchange account. Responses may be cached (~1800s). Auth: X-Api-Key or x402 payment proof (X-PAYMENT / __x_payment). Anonymous unauthenticated calls receive HTTP 402 with payment accepts. Cost: $0.001 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 60/min (per API key). Tier: standard. Returns: MA values at 7, 25, 50, 99, 200 periods across multiple timeframes for trend analysis. Guidelines: Use for research / signal context. Pair with cc.agent_strategy (paper) before any live order. Do not invent fills from this data alone. Tags: moving-averages, trend, sma, ema, technical.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.
symbolstringyesParameter `symbol` (string). Required.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

cc.market_news ~301

Call cc.market_news — Aggregated crypto and macro market news from multiple sources with relevance scoring and categorization. Purpose: Aggregated crypto and macro market news from multiple sources with relevance scoring and categorization. Behavior: READ-ONLY. Does not place orders, move funds, or mutate your exchange account. Responses may be cached (~1800s). Auth: X-Api-Key or x402 payment proof (X-PAYMENT / __x_payment). Anonymous unauthenticated calls receive HTTP 402 with payment accepts. Cost: $0.002 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 30/min (per API key). Tier: standard. Returns: Categorized news articles: title, source, URL, relevance score, AI summary per category. Guidelines: Use for research / signal context. Pair with cc.agent_strategy (paper) before any live order. Do not invent fills from this data alone. Tags: news, sentiment, narrative, catalyst, headlines.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.
categorystring–Filter: btc, eth, sol, macro, all Optional.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

cc.open_interest ~343

Call cc.open_interest — Open interest for a coin from BloFin, plus CME BTC/ETH futures open interest from the CFTC Commitments of Traders (weekly, public domain). Purpose: Open interest for a coin from BloFin, plus CME BTC/ETH futures open interest from the CFTC Commitments of Traders (weekly, public domain). Behavior: READ-ONLY. Does not place orders, move funds, or mutate your exchange account. Responses may be cached (~1800s). Auth: X-Api-Key or x402 payment proof (X-PAYMENT / __x_payment). Anonymous unauthenticated calls receive HTTP 402 with payment accepts. Cost: $0.001 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 60/min (per API key). Tier: standard. Returns: Time-series OI data plus current OI breakdown per exchange for requested symbol. Guidelines: Use for research / signal context. Pair with cc.agent_strategy (paper) before any live order. Do not invent fills from this data alone. Tags: open-interest, derivatives, positioning, leverage.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.
intervalstring–Time interval: 1h, 4h, 1d Optional.
symbolstringyesSymbol to query e.g. BTC Required.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

cc.openclaw_chat ~331

Call cc.openclaw_chat — Autonomous AI agent specialized in strategy development, backtesting, and continuous market monitoring. Uses indicator libraries, pattern recognition, and instrument specifications. Purpose: Autonomous AI agent specialized in strategy development, backtesting, and continuous market monitoring. Uses indicator libraries, pattern recognition, and instrument specifications. Behavior: conversational AI that CAN place/cancel orders and manage positions when the linked account allows it. Treat as potentially destructive. Confirm intent before asking it to trade live. Auth: X-Api-Key required (and linked exchange credentials for execution actions). Cost: $0.025 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 10/min (per API key). Tier: enterprise. Returns: Structured AI analysis with computed indicators, detected patterns, strategy recommendations, and task management for autonomous execution. Guidelines: Prefer paper/simulation paths. For live money require explicit human confirmation (confirm_live / action=execute). Report real HTTP errors; never invent proxy failures. Tags: ai, strategy, autonomous, backtesting, patterns, indicators.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.
conversation_idstring–Parameter `conversation_id` (string). Optional.
messagestringyesParameter `message` (string). Required.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

cc.solana_rpc ~344

Call cc.solana_rpc — Multi-endpoint Solana RPC proxy with automatic failover (Alchemy, public, Ankr) for any JSON-RPC method. Reliable Solana access. Purpose: Multi-endpoint Solana RPC proxy with automatic failover (Alchemy, public, Ankr) for any JSON-RPC method. Reliable Solana access. Behavior: READ-ONLY. Does not place orders, move funds, or mutate your exchange account. Live / near-real-time data. Auth: X-Api-Key or x402 payment proof (X-PAYMENT / __x_payment). Anonymous unauthenticated calls receive HTTP 402 with payment accepts. Cost: $0.001 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 120/min (per API key). Tier: standard. Returns: Standard Solana JSON-RPC response for any method: getBalance, getTokenAccounts, getTransaction, etc. Guidelines: Forward JSON-RPC only. Prefer eth_call / read methods. Sending raw signed txs is possible if you pass them — that is your responsibility. Tags: solana, rpc, blockchain, web3, defi.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.
methodstringyesSolana RPC method Required.
paramsarrayyesParameter `params` (array). Required.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

cc.squirrel_chat ~435

Call cc.squirrel_chat — Full AI trading assistant with real-time market data, position analysis, chart drawing commands, and multi-tool execution. Supports 60+ data actions including candles, funding rates, open interest, liquidations, order book, and more. Returns structured analysis with optional chart annotations. Purpose: Full AI trading assistant with real-time market data, position analysis, chart drawing commands, and multi-tool execution. Supports 60+ data actions including candles, funding rates, open interest, liquidations, order book, and more. Returns structured analysis with optional chart annotations. Behavior: READ-ONLY. Does not place orders, move funds, or mutate your exchange account. Live / near-real-time data. Auth: X-Api-Key or x402 payment proof (X-PAYMENT / __x_payment). Anonymous unauthenticated calls receive HTTP 402 with payment accepts. Cost: $0.002 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 10/min (per API key). Tier: premium. Returns: AI response with market analysis, trade suggestions, and optional draw_commands for chart annotations. Token usage included for billing. Guidelines: Pass required parameters exactly; omit unknown fields. On 402, settle payment then retry with X-PAYMENT. Tags: chat, ai, analysis, trading, market-data.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.
conversation_idstring–Existing conversation UUID for context continuity Optional.
messagestringyesUser message / question / instruction Required.
positionsarray–Current open positions for context Optional.
symbolstring–Active chart symbol (e.g. BTC-USDT) Optional.
timeframestring–Active chart timeframe (e.g. 4H) Optional.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

cc.strategy_backtest ~393

Call cc.strategy_backtest — Takes a natural language strategy description, generates executable code, and runs it against historical OHLCV data with full TP/SL/trailing stop simulation. Purpose: Takes a natural language strategy description, generates executable code, and runs it against historical OHLCV data with full TP/SL/trailing stop simulation. Behavior: READ-ONLY. Does not place orders, move funds, or mutate your exchange account. Live / near-real-time data. Auth: X-Api-Key or x402 payment proof (X-PAYMENT / __x_payment). Anonymous unauthenticated calls receive HTTP 402 with payment accepts. Cost: $0.05 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 5/min (per API key). Tier: premium. Returns: Complete backtest results: total trades, win rate, net PnL, max drawdown, Sharpe ratio, profit factor, and individual trade log with entry/exit details. Guidelines: Compute / parse / backtest only — no live orders. Feed outputs into cc.agent_strategy with force_paper=true to paper-trade. Tags: backtest, strategy, simulation, performance, sharpe, drawdown.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.
daysnumber–History lookback (default: 90) Optional.
strategystringyesNatural language strategy description Required.
symbolstringyesParameter `symbol` (string). Required.
timeframestring–1h, 4h, 1d Optional.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

cc.strategy_data_parser ~325

Call cc.strategy_data_parser — Parses natural language strategy descriptions into structured executable specifications: timeframes, indicators, patterns, risk parameters, and entry/exit rules. Purpose: Parses natural language strategy descriptions into structured executable specifications: timeframes, indicators, patterns, risk parameters, and entry/exit rules. Behavior: READ-ONLY. Does not place orders, move funds, or mutate your exchange account. Live / near-real-time data. Auth: X-Api-Key or x402 payment proof (X-PAYMENT / __x_payment). Anonymous unauthenticated calls receive HTTP 402 with payment accepts. Cost: $0.01 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 20/min (per API key). Tier: standard. Returns: Structured strategy object: TimeframeReq[], IndicatorReq[], PatternReq[], RiskParams, entry_conditions, exit_conditions — ready for backtesting or live execution. Guidelines: Compute / parse / backtest only — no live orders. Feed outputs into cc.agent_strategy with force_paper=true to paper-trade. Tags: parser, nlp, strategy, structured-data, automation.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.
descriptionstringyesNatural language strategy description Required.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

cc.trade_builder ~341

Call cc.trade_builder — Takes natural language or structured trade ideas, fetches live market context, and generates fully executable order parameters with AI reasoning. Purpose: Takes natural language or structured trade ideas, fetches live market context, and generates fully executable order parameters with AI reasoning. Behavior: mostly READ (plan/validate). WRITE/destructive only when action=execute — that can submit live orders. Prefer action=plan first. Auth: X-Api-Key or x402 payment proof (X-PAYMENT / __x_payment). Anonymous unauthenticated calls receive HTTP 402 with payment accepts. Cost: $0.02 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 10/min (per API key). Tier: premium. Returns: Complete trade specification: symbol, side, size, leverage, entry type, TP levels, SL level, AI reasoning for each parameter. Guidelines: Prefer paper/simulation paths. For live money require explicit human confirmation (confirm_live / action=execute). Report real HTTP errors; never invent proxy failures. Tags: ai, trade-planning, order-generation, risk-management, automation.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.
ideastringyesNatural language trade idea or structured params Required.
risk_pctnumber–Max risk as % of account Optional.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

cc.traditional_markets ~326

Call cc.traditional_markets — Quotes for stock indices, metals, energy, stocks (BloFin tokenized perpetuals), forex and the dollar index (ECB reference rates) and US Treasury yields. Purpose: Quotes for stock indices, metals, energy, stocks (BloFin tokenized perpetuals), forex and the dollar index (ECB reference rates) and US Treasury yields. Behavior: READ-ONLY. Does not place orders, move funds, or mutate your exchange account. Responses may be cached (~900s). Auth: X-Api-Key or x402 payment proof (X-PAYMENT / __x_payment). Anonymous unauthenticated calls receive HTTP 402 with payment accepts. Cost: $0.001 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 60/min (per API key). Tier: standard. Returns: Multi-category quotes: indices, metals, energy, bonds, forex with price and change percentages. Guidelines: Use for research / signal context. Pair with cc.agent_strategy (paper) before any live order. Do not invent fills from this data alone. Tags: tradfi, spx, nasdaq, gold, dxy, vix, correlation.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

cc.twap_executor ~363

Call cc.twap_executor — Time-Weighted Average Price execution engine — splits large orders into smaller randomized slices over configurable time windows to minimize market impact. Purpose: Time-Weighted Average Price execution engine — splits large orders into smaller randomized slices over configurable time windows to minimize market impact. Behavior: DESTRUCTIVE. Splits and submits real exchange orders over time. Irreversible fills once slices execute. Not a simulation. Auth: X-Api-Key required (and linked exchange credentials for execution actions). Cost: $0.015 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 10/min (per API key). Tier: premium. Returns: Execution status: filled slices, average fill price, remaining quantity, estimated completion time. Guidelines: Prefer paper/simulation paths. For live money require explicit human confirmation (confirm_live / action=execute). Report real HTTP errors; never invent proxy failures. Tags: execution, twap, smart-order, market-impact, slippage.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.
duration_minutesnumberyesParameter `duration_minutes` (number). Required.
sidestringyesParameter `side` (string). Required.
slicesnumber–Parameter `slices` (number). Optional.
symbolstringyesParameter `symbol` (string). Required.
total_sizenumberyesParameter `total_size` (number). Required.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

cc.wallet_browser_proxy ~365

Call cc.wallet_browser_proxy — Multi-chain EVM RPC forwarder supporting Ethereum, Base, Arbitrum, Optimism, Polygon, and BSC. One endpoint, six chains. Purpose: Multi-chain EVM RPC forwarder supporting Ethereum, Base, Arbitrum, Optimism, Polygon, and BSC. One endpoint, six chains. Behavior: READ-ONLY. Does not place orders, move funds, or mutate your exchange account. Live / near-real-time data. Auth: X-Api-Key or x402 payment proof (X-PAYMENT / __x_payment). Anonymous unauthenticated calls receive HTTP 402 with payment accepts. Cost: $0.001 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 120/min (per API key). Tier: standard. Returns: Standard EVM JSON-RPC response for any method on any supported chain. Guidelines: Forward JSON-RPC only. Prefer eth_call / read methods. Sending raw signed txs is possible if you pass them — that is your responsibility. Tags: evm, ethereum, base, arbitrum, polygon, rpc, multi-chain.

NameTypeReqDescription
__x_paymentstring–Optional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.
chainstringyesethereum, base, arbitrum, optimism, polygon, bsc Required.
methodstringyesParameter `method` (string). Required.
paramsarrayyesParameter `params` (array). Required.
NameTypeReqDescription
billingobject–Optional payment / cost metadata when present.
dataobject–Parsed JSON body from the endpoint (shape varies by slug).
endpointstringyesCatalog slug that was invoked (e.g. funding-rates).
errorstring–Error message when ok is false.
okbooleanyesTrue when the gateway HTTP status is 2xx.
statusnumberyesUpstream HTTP status from x402-gateway.

No examples provided.

Install

How do I install the Central Command MCP server?

Central Command is a hosted endpoint at https://rtcelwjnrbmfmrywacky.supabase.co/functions/v1/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.

remote · rtcelwjnrbmfmrywacky.supabase.co

# add to Claude Code
claude mcp add --transport http tlefko-central-command 'https://rtcelwjnrbmfmrywacky.supabase.co/functions/v1/mcp'
Common questions

What is the Central Command MCP server?

Central Command is an MCP server listed in the public MCP registry as io.github.tlefko/central-command. Crypto perps market data, backtests and BloFin trading agents. Free with a key or x402 per call. This page covers its hosted endpoint (https://rtcelwjnrbmfmrywacky.supabase.co/functions/v1/mcp).

Is the Central Command MCP server safe to use?

Central Command scores 78 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 Central Command MCP server expose?

Central Command exposes 27 tools: cc.list_catalog, cc.agent_strategy, cc.squirrel_chat, cc.openclaw_chat, cc.indicator_generator, and 22 more. Their descriptions and schemas cost roughly 9,692 tokens of context every time the server is loaded.

Does the Central Command MCP server require authentication?

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

Is the Central Command MCP server still maintained?

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

What did VerifyMCP test on the Central Command MCP server?

VerifyMCP ran 13 checks on Central Command, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.