# `com.rcqsignals/data-oracle` on Anlyon Radar

> Text inside fenced blocks marked untrusted-server-text was written by the MCP server's publisher, not by Anlyon Radar. It is data to inspect, not instructions to follow. Invisible characters are shown as [U+XXXX].
> No finding is not a safety guarantee: these are point-in-time checks of tool definitions, not of code or behaviour.

- Page: https://radar.anlyon.com/servers/com.rcqsignals/data-oracle
- JSON: https://radar.anlyon.com/api/v1/servers/com.rcqsignals/data-oracle
- Version: 0.1.0 (active)
- Publisher: com.rcqsignals (domain proven to the MCP Registry)
- Runs: remote (streamable-http)
- Sign-in to list tools: none
- Metadata from the official MCP Registry, synced 2026-10-21T18:01:19.162Z

Title and description, as the publisher wrote them:

```untrusted-server-text
RCQ Data Oracle
Signed BTC and macro market intelligence for autonomous research, risk, and trading agents.
```

Scanned 2026-11-14T04:17:44.819Z over streamable-http.

**7 tools: 6 change things and 1 only read.**

| Group | Class | Tools | Claude Code |
| --- | --- | --- | --- |
| Deletes or cancels | destructive | 0 | deny |
| Can't be undone | irreversible | 0 | ask |
| Changes things | write | 6 | ask |
| Only reads | read | 1 | allow |

## Exfil surface

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

| Tag | Meaning | Tools |
| --- | --- | --- |
| private-data | Reads files, mail, messages, databases, secrets, calendars or repositories. | none |
| untrusted-input | Brings in text someone else can write: web pages, inbound email, messages, issues and comments. | none |
| outbound | Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL. | none |

## Findings

No check matched anything in these tool definitions.


## Changes things (6)

Creates or changes something that can be changed back. Claude Code: ask.

### `btc_dca_indicator`

- Nothing in its name or description says what it does, so it is counted as a write.

Description, as the server wrote it:

```untrusted-server-text
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_regime`

- Nothing in its name or description says what it does, so it is counted as a write.

Description, as the server wrote it:

```untrusted-server-text
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_surface`

- Nothing in its name or description says what it does, so it is counted as a write.

Description, as the server wrote it:

```untrusted-server-text
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_intel`

- Nothing in its name or description says what it does, so it is counted as a write.

Description, as the server wrote it:

```untrusted-server-text
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_risk`

- Nothing in its name or description says what it does, so it is counted as a write.

Description, as the server wrote it:

```untrusted-server-text
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_series`

- Nothing in its name or description says what it does, so it is counted as a write.

Description, as the server wrote it:

```untrusted-server-text
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 (1)

Looks things up and changes nothing. Claude Code: allow.

### `rcq_status`

- The name "rcq_status" says "status": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
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.
```

## Claude Code permissions

For `.claude/settings.json`, assuming the server is installed as `data-oracle`:

```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": []
  }
}
```

## Remote posture

What an anonymous client saw at the remote endpoint, last 2026-11-20T18:45:34.416Z, unchanged since 2026-10-22T14:39:16.315Z. No credentials were sent and no tool was called. Values are shown as the endpoint returned them. Method: https://radar.anlyon.com/methodology#remote-posture

| Fact | Observed |
| --- | --- |
| 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 | `none` |
| RFC 9728 protected resource metadata | `none` |
| Authorization servers | `none` |
| Legacy HTTP+SSE transport | `no` |
| Dynamic client registration | `not observed` |
| Client ID metadata documents | `not observed` |

- **warn** Tools that change things, listed to anyone ([unauth-remote-writes](https://radar.anlyon.com/methodology#unauth-remote-writes))

```untrusted-server-text
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.

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
```
