01
Agent discovers
The client lists purpose-built tools and free reference resources through MCP.
Public remote MCP server
Market context for agents that decide.
Signed, machine-readable financial intelligence for autonomous research, risk and trading workflows. Discover narrowly scoped tools, pay per successful call with x402, and verify every RCQ payload independently.
Stateless MCP
Streamable HTTP · protocol 2026-07-28
x402 v2
Exact USDC settlement on Base
Prepared snapshots
Fast reads from the existing oracle pipeline
Independent verification
Canonicalized SHA-256 + Ed25519
System boundary
Thin transport. Clear authority.
The MCP layer helps agents discover and invoke RCQ products. The storefront remains the sole authority for pricing, x402 validation, settlement, product availability and signing.
02
RCQ challenges
A paid call returns validated x402 terms: resource, amount, network and asset.
03
Wallet authorizes
The client creates payment authorization and retries through a supported transport.
04
Oracle signs
The storefront settles, returns the prepared snapshot and signs the original payload.
MCP v1 tool surface
Small calls. Explicit purpose.
Each product is a separate tool so agents can select the narrowest useful context, understand the price before authorization and preserve a clean audit trail.
btc_intel
BTC Intel
Directional BTC context with conviction, regime, technical levels and 72-hour large-transfer activity.
- Use when
- An agent needs a compact decision-context snapshot before research, risk review or trade planning.
- Methodology
- Packages the current RCQ bias and conviction outputs, regime label and score, technical levels, and observed large on-chain transfers over 72 hours. Large activity is reported using the product's published 100 BTC / $5M threshold.
- Output
- Bias, conviction, regime, levels, transfer count, total and largest observed transfer, freshness and provenance.
Market intelligence only. Not individualized advice or an execution instruction.
btc_funding_surface
BTC Perpetual Funding Surface
Normalized cross-exchange derivatives intelligence across four independent BTC perpetual venues.
- Use when
- Screening crowding, funding dislocation, leverage regimes, venue divergence or potential arbitrage conditions.
- Methodology
- Normalizes the published funding observations from Bitnomial, OKX, Hyperliquid and dYdX into one canonical comparison surface, then reports venue rates, surface statistics, dispersion, z-scores and regime state.
- Evidence
- The data-product case passed. A preregistered contrarian directional hypothesis failed and is not marketed as predictive alpha.
Use as derivatives and crowding context—not as a validated directional BTC forecast.
btc_funding_regime
BTC Funding Regime
A low-cost branch-on-state call derived from the full funding surface.
- Use when
- An agent only needs the compact regime state before deciding whether the richer funding surface is warranted.
- Methodology
- Projects the normalized surface into a compact state object using the surface median, 30-day z-score, same-sign share, spread, dispersion, venue count and freshness controls.
- Output
- Regime state plus the minimum supporting statistics needed for an auditable branch decision.
Cheaper does not mean less controlled: the response retains signing, versions, freshness and provenance.
macro_event_risk
Macro Event Risk Surface
Cross-asset fragility plus scheduled BOJ, FOMC, CPI and NFP context.
- Use when
- Reviewing risk exposure, carry-unwind conditions or the context surrounding a major scheduled macro event.
- Methodology
- Frozen core: BTC Fragility 30%, JPY Carry Stress 30%, Cross-Asset Risk-Off 25% and Rates Stress 15%. Scores map to LOW, GUARDED, ELEVATED, HIGH or EXTREME.
- Event layer
- BOJ, FOMC, CPI and NFP proximity is descriptive context only. It never numerically changes the frozen core score.
Daily-series publication lag is explicit. USDJPY availability may be the binding freshness constraint. Not a directional BTC signal.
btc_dca_indicator
BTC DCA Indicator
Regime-aware accumulation intensity for systematic BTC purchasing workflows.
- Use when
- A recurring accumulator needs a standardized intensity input rather than a binary buy-or-sell call.
- Methodology
- Combines trend, momentum, mean reversion, moving-average structure, MACD stabilization and short-term price stabilization into a 0–9 score.
- Output
- Score, LIGHT / BASE / ACCELERATE / AGGRESSIVE state, intensity multiplier, data quality, freshness and provenance.
Historical testing was positive across four chronological blocks; forward validation remains active and statistically proven alpha is not claimed.
monthly_series
RCQ BTC Monthly Series
The complete currently published signed monthly performance series for audit and historical review.
- Use when
- Research, diligence or audit workflows require the full published monthly record rather than a teaser.
- Methodology
- Returns the prepared 18-month monthly series with the algorithm attribution, snapshot timestamp, record count and cryptographic provenance preserved.
- Access
- Public MCP access uses the current x402 price in the signed catalog. The separately arranged access-key subscription applies only to monthly_series and is not self-serve through MCP.
Historical performance is not a guarantee of future results. The licensed full trade log is outside MCP v1.
How to use
Connect once. Call deliberately.
MCP hosts vary, but the operating sequence is consistent. Add the remote endpoint, discover tools, select the narrowest useful call and let an x402-capable wallet handle authorization.
Generic remote MCP configuration
JSON
{
"mcpServers": {
"rcq-data-oracle": {
"url": "https://mcp.rcqsignals.com/mcp"
}
}
}
1
Discover before calling
List tools and free resources. Read descriptions, cadence, limitations and current catalog terms.
2
Receive validated payment terms
An unpaid tool call returns a structured x402 v2 challenge with the exact endpoint, amount, Base network and USDC asset.
3
Authorize outside model-visible arguments
Use an MCP-aware wallet bridge. RCQ supports the official x402 metadata convention and the MCP 2026 payment-header convention.
4
Verify the returned intelligence
Retain the original signed payload, settlement metadata, methodology version, freshness fields and provenance in your audit record.
x402 production flow
Authority remains upstream
agent → tools/call → payment_required
→ wallet authorization → tools/call retry
→ storefront verifies + settles
→ signed RCQ payload + settlement metadata
Free MCP resources
Context before cost.
Agents can inspect product availability, a signed sample, verification instructions and BTC Intel freshness proof before invoking a paid tool.
rcq://catalog
Product catalog
Signed product definitions, live availability, cadence, endpoints and prices.
rcq://sample
Signed sample
Free audit-summary teaser and representative monthly sample.
rcq://verification
Verification
Current public key, canonicalization method and signature-verification steps.
rcq://teaser/btc-intel
Freshness proof
Signed BTC Intel liveness, freshness and paid-field preview without a directional call.
Verification and controls
Trust is inspectable.
RCQ responses are designed for reproducibility and downstream audit—not blind acceptance.
Issuer, algorithm attribution, SHA-256 digest, Ed25519 signature and public key travel with the payload.
Normalization, scoring or regime-rule versions remain inside the signed result where the product defines them.
Product-specific timestamps, observation lag, staleness and data-quality fields remain explicit.
The adapter rejects pricing drift, invalid signatures, stale or unavailable upstream results according to the product contract.
Verification outline
Ed25519
1. Read provenance and retain the original response. 2. Canonicalize the unsigned body using sorted keys, compact separators and UTF-8. 3. Confirm the canonical SHA-256 digest. 4. Verify the Ed25519 signature with the published key. 5. Reject on any mismatch.
Institutional integration
One live workflow. Measurable evidence.
RCQ is preparing a controlled design-partner program for hedge funds, family offices, quant teams, AI research groups and trading-agent builders.
- MCP and REST/x402 access
- Historical samples and methodology cards
- Signed-response verification support
- Use-case playbooks and integration guidance
- Freshness, data-quality and limitation definitions
Public MCP v1 is pay-per-call through x402. Authenticated
institutional entitlements and included-usage allowances are
part of the approved next-stage architecture and are not yet
self-serve. Subscribers will not be charged twice for included
usage.