RCQ Signals MCP server

• Registry namecom.rcqsignals/data-oracleverified in the MCP registry

The registry name sits under rcqsignals.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-21
• Tools7
• Server calls itselfrcq-data-oracle
• Server version0.1.0
• Protocol version2025-06-18

On 2026-10-21 the server answered initialize and tools/list without a sign-in. First answer in 215 ms.

• Its tools do none of the product's use cases we checked: check 4h regime and reward-to-risk on each signal; calculate position size and expected value for self-entered trades.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score68 of 100answers 100 · does the job 0 · definitions 83 · context 100 · connects 100
• What an agent can do with it0 of 2 use cases
• Answered100% of days14 of 14 daily checks
• Median first answer324 ms
• Space in an agent's context≈ 1,088 tokensthe definitions of all its tools (7), which an agent carries on every turn
• Tool definitionsB · 83 of 100
• Typed results0 of 7 toolsdeclared outputSchema: results come typed, read once

• Not saying whether it only reads or can destroy: 7 of 7

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• btc_intel

  Paid BTC decision-context snapshot. Use when an agent needs current directional bias, conviction, regime score, technical levels and 72-hour large on-chain transfer activity. This is market intelligence, not individualized investment…

• btc_funding_surface

  Paid normalized BTC perpetual-funding surface across Bitnomial, OKX, Hyperliquid and dYdX. Use for crowding, cross-venue dislocation, leverage-regime monitoring and arbitrage screening. The directional-alpha hypothesis was rejected; do…

• btc_funding_regime

  Paid compact BTC perpetual-funding regime read across Bitnomial, OKX, Hyperliquid and dYdX. Use as a low-cost branch-on-state check before requesting the full funding surface. Returns regime state, normalized surface statistics, venue…

• macro_event_risk

  Paid cross-asset macro-fragility and scheduled-event context. Use when evaluating risk exposure, carry-unwind conditions, or proximity to BOJ, FOMC, CPI and NFP events. Event proximity adds context and never changes the frozen core score…

• btc_dca_indicator

  Paid regime-aware BTC accumulation-intensity indicator. Use when a systematic accumulation workflow needs a 0-9 score, LIGHT, BASE, ACCELERATE or AGGRESSIVE state, and an intensity multiplier. Forward validation remains active; this is…

• monthly_series

  Paid signed RCQ BTC monthly performance series. Use for historical review, audit and research workflows that require the complete currently published monthly dataset. The separately arranged access-key subscription applies only to…

• rcq_status

  Free operational check for RCQ Data Oracle. Use before paid calls to confirm product availability and freshness. Returns a filtered operational summary only, not paid market intelligence or internal infrastructure details.