Skip to content

RCQ Data Oracle MCP server

com.rcqsignals/data-oraclercqsignals.comstreamable-httpv0.1.0Scanned

Signed BTC and macro market intelligence for autonomous research, risk, and trading agents.

7 tools: 6 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 6 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

6 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the RCQ Data Oracle MCP server can do

The RCQ Data Oracle MCP server is published by rcqsignals.com, a domain the MCP Registry verified. It has 7 tools. It can create or change data (6 tools: btc_intel, btc_funding_surface, btc_funding_regime, macro_event_risk and 2 more), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 14, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 6Claude Code: ask
  • btc_dca_indicatorPaid regime-aware BTC accumulation-intensity indicator.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • btc_funding_regimePaid compact BTC perpetual-funding regime read across Bitnomial, OKX, Hyperliquid and dYdX.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • btc_funding_surfacePaid normalized BTC perpetual-funding surface across Bitnomial, OKX, Hyperliquid and dYdX.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • btc_intelPaid BTC decision-context snapshot.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • macro_event_riskPaid cross-asset macro-fragility and scheduled-event context.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • monthly_seriesPaid signed RCQ BTC monthly performance series.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 1Show 1 read-only tool
  • rcq_statusFree operational check for RCQ Data Oracle.No findings

    Why it is in this group

    • The name "rcq_status" says "status": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:45 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.rcqsignals.com/mcp: tools/list returned 7 tools to an anonymous client, including btc_intel (write), btc_funding_surface (write), btc_funding_regime (write), macro_event_risk (write), btc_dca_indicator (write) and 1 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http data-oracle https://mcp.rcqsignals.com/mcp
claude mcp add --transport http data-oracle https://mcp.rcqsignals.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__data-oracle__rcq_status"
    ],
    "ask": [
      "mcp__data-oracle__btc_intel",
      "mcp__data-oracle__btc_funding_surface",
      "mcp__data-oracle__btc_funding_regime",
      "mcp__data-oracle__macro_event_risk",
      "mcp__data-oracle__btc_dca_indicator",
      "mcp__data-oracle__monthly_series"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as data-oracle. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.rcqsignals/data-oracle/verify?hash=9a13aa69ca55e143a8b1fff1ad7cda1474e7a1cd0e6ccfda7a502866daf282dc" | jq -e '.changed == false'

Pinned hash 9a13aa69ca55, from Nov 14, 2026, 04:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.rcqsignals/data-oracle/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.rcqsignals/data-oracle
[![Anlyon Radar](https://radar.anlyon.com/badge/com.rcqsignals/data-oracle.svg)](https://radar.anlyon.com/servers/com.rcqsignals/data-oracle)

Source: MCP Registry. Synced Oct 21, 2026, 18:01 UTC.

RCQ Data Oracle MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the RCQ Data Oracle MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the RCQ Data Oracle MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the RCQ Data Oracle MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the RCQ Data Oracle MCP server have?

7 tools: 6 write, 1 read. btc_intel, btc_funding_surface, btc_funding_regime, macro_event_risk, btc_dca_indicator, monthly_series and rcq_status.

Does the RCQ Data Oracle MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the RCQ Data Oracle MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the RCQ Data Oracle MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.