RCQ Data Oracle
REMOTE · MCP.RCQSIGNALS.COM · SCANNED SEP 20
Signed BTC and macro market intelligence for autonomous research, risk, and trading agents.
Available components
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 715 tokens (~65/item across 11 items; 7 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the RCQ Data Oracle MCP server?
RCQ Data Oracle is a hosted endpoint at https://mcp.rcqsignals.com/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 · mcp.rcqsignals.com
claude mcp add --transport http com-rcqsignals-data-oracle 'https://mcp.rcqsignals.com/mcp'
{
"mcpServers": {
"com-rcqsignals-data-oracle": {
"url": "https://mcp.rcqsignals.com/mcp"
}
}
} {
"servers": {
"com-rcqsignals-data-oracle": {
"type": "http",
"url": "https://mcp.rcqsignals.com/mcp"
}
}
} [mcp_servers.com-rcqsignals-data-oracle] url = "https://mcp.rcqsignals.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-rcqsignals-data-oracle": {
"type": "remote",
"url": "https://mcp.rcqsignals.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-rcqsignals-data-oracle --url 'https://mcp.rcqsignals.com/mcp' --transport streamable-http
mcp_servers:
com-rcqsignals-data-oracle:
url: "https://mcp.rcqsignals.com/mcp" {
"McpServers": {
"com-rcqsignals-data-oracle": {
"Transport": "http",
"Url": "https://mcp.rcqsignals.com/mcp"
}
}
} assistant mcp add com-rcqsignals-data-oracle -t streamable-http -u 'https://mcp.rcqsignals.com/mcp'
{
"mcpServers": {
"com-rcqsignals-data-oracle": {
"type": "http",
"url": "https://mcp.rcqsignals.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Schema Quality & AI Usability fell 1.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Probed https://mcp.rcqsignals.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rcqsignals.com | CN=WE1,O=Google Trust Services,C=US | 31 Aug 2026 | 29 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 43a89d5ce777e4690eb2e40fd07fd74a |
| SANs: rcqsignals.com, mcp.rcqsignals.com, *.mcp.rcqsignals.com | ||||||
| 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 mcp.rcqsignals.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| rcqsignals.com. | absent | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.rcqsignals.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.rcqsignals.com/mcp | Inconclusive | 405 |
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 →
btc_dca_indicator BTC DCA Indicator ~101
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 market intelligence, not statistically proven alpha or individualized advice. Read rcq://catalog for current availability and price.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_signature | string | – | x402 payment authorization for MCP 2026 header-aware clients. |
No output schema declared.
No examples provided.
btc_funding_regime BTC Funding Regime ~109
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 coverage and freshness. This is derivatives and crowding intelligence, not validated directional alpha. Read rcq://catalog for current availability and price.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_signature | string | – | x402 payment authorization for MCP 2026 header-aware clients. |
No output schema declared.
No examples provided.
btc_funding_surface BTC Perpetual Funding Surface ~103
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 not use this tool as a validated directional signal. Read rcq://catalog for current availability and price.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_signature | string | – | x402 payment authorization for MCP 2026 header-aware clients. |
No output schema declared.
No examples provided.
btc_intel BTC Intel ~82
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 advice. Read rcq://catalog for current availability and price.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_signature | string | – | x402 payment authorization for MCP 2026 header-aware clients. |
No output schema declared.
No examples provided.
macro_event_risk Macro Event Risk Surface ~105
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. This is descriptive risk intelligence, not a directional BTC signal. Read rcq://catalog for current availability and price.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_signature | string | – | x402 payment authorization for MCP 2026 header-aware clients. |
No output schema declared.
No examples provided.
monthly_series RCQ BTC Monthly Series ~86
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 monthly_series and is not self-serve through MCP. Read rcq://catalog for current availability and price.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_signature | string | – | x402 payment authorization for MCP 2026 header-aware clients. |
No output schema declared.
No examples provided.
rcq_status RCQ Data Oracle Status ~45
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the RCQ Data Oracle MCP server?
RCQ Data Oracle is an MCP server listed in the public MCP registry as com.rcqsignals/data-oracle. Signed BTC and macro market intelligence for autonomous research, risk, and trading agents. This page covers its hosted endpoint (https://mcp.rcqsignals.com/mcp).
Is the RCQ Data Oracle MCP server safe to use?
RCQ Data Oracle scores 71 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 RCQ Data Oracle MCP server expose?
RCQ Data Oracle exposes 7 tools: btc_intel, btc_funding_surface, btc_funding_regime, macro_event_risk, btc_dca_indicator, and 2 more. Their descriptions and schemas cost roughly 631 tokens of context every time the server is loaded.
Does the RCQ Data Oracle MCP server require authentication?
No. We connected to RCQ Data Oracle without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RCQ Data Oracle MCP server still maintained?
RCQ Data Oracle is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.