# RF Signals (remote · app.rewardsfuel.com)

Daily technical-analysis signals and levels for AAPL, NVDA, SPY, QQQ and more. Not financial advice.

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `app.rewardsfuel.com`: 61/100 (this document), [markdown](https://verifymcp.io/servers/com-rewardsfuel-signals/api-mcp-signals.md), [page](https://verifymcp.io/servers/com-rewardsfuel-signals/api-mcp-signals)

## Channel facts

- Endpoint: `https://app.rewardsfuel.com/api/mcp/signals`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 413 tokens (~206/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the RF Signals MCP server?

RF Signals is a hosted endpoint at https://app.rewardsfuel.com/api/mcp/signals, 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.

### Claude

```bash
claude mcp add --transport http com-rewardsfuel-signals 'https://app.rewardsfuel.com/api/mcp/signals'
```

### Cursor

```json
{
  "mcpServers": {
    "com-rewardsfuel-signals": {
      "url": "https://app.rewardsfuel.com/api/mcp/signals"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-rewardsfuel-signals": {
      "type": "http",
      "url": "https://app.rewardsfuel.com/api/mcp/signals"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-rewardsfuel-signals]
url = "https://app.rewardsfuel.com/api/mcp/signals"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-rewardsfuel-signals": {
      "type": "remote",
      "url": "https://app.rewardsfuel.com/api/mcp/signals",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-rewardsfuel-signals --url 'https://app.rewardsfuel.com/api/mcp/signals' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-rewardsfuel-signals:
    url: "https://app.rewardsfuel.com/api/mcp/signals"
```

### Netclaw

```json
{
  "McpServers": {
    "com-rewardsfuel-signals": {
      "Transport": "http",
      "Url": "https://app.rewardsfuel.com/api/mcp/signals"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-rewardsfuel-signals -t streamable-http -u 'https://app.rewardsfuel.com/api/mcp/signals'
```

### Other

```json
{
  "mcpServers": {
    "com-rewardsfuel-signals": {
      "type": "http",
      "url": "https://app.rewardsfuel.com/api/mcp/signals"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 60, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-18 (score 60)

First indexed and scored.

## MCP tools (2)

### `list_signal_tickers` (~67 tokens)

RF Signals: list the supported tickers (AAPL, AMZN, GOOGL, META, MSFT, NVDA, QQQ, SPY and TSLA) and the latest daily bar date for each. Free, no key. Educational only, not financial advice.

### `get_signal` (~134 tokens)

RF Signals daily technical read for one ticker: price, SMA50/200, RSI(14), MACD(12,26,9), trend, alignment and TD-style exhaustion counts (setup 9 / countdown 13). Free, no key: daily timeframe, delayed one trading day. Current data, levels, ratios, scans and weekly/monthly are on the paid server (https://app.rewardsfuel.com/api/mcp, rf_live_ key). Educational only, not financial advice.

Input parameters:

- `ticker` (string, required): Ticker symbol, e.g. NVDA. Call list_signal_tickers for the supported list.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-rewardsfuel-signals/api-mcp-signals#diagnostics

## Score history

- 2026-11-21: 61
- 2026-11-20: 61
- 2026-11-19: 60
- 2026-11-18: 60

## Common questions

### What is the RF Signals MCP server?

RF Signals is an MCP server listed in the public MCP registry as com.rewardsfuel/signals. Daily technical-analysis signals and levels for AAPL, NVDA, SPY, QQQ and more. Not financial advice. This page covers its hosted endpoint (https://app.rewardsfuel.com/api/mcp/signals).

### Is the RF Signals MCP server safe to use?

RF Signals scores 61 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 RF Signals MCP server expose?

RF Signals exposes 2 tools: list_signal_tickers, get_signal. Their descriptions and schemas cost roughly 201 tokens of context every time the server is loaded.

### Does the RF Signals MCP server require authentication?

No. We connected to RF Signals without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the RF Signals MCP server still maintained?

RF Signals is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the RF Signals MCP server?

VerifyMCP ran 12 checks on RF Signals, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about RF Signals: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://app.rewardsfuel.com/api/mcp/signals
- Website: https://signals.rewardsfuel.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-rewardsfuel-signals/api-mcp-signals.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-rewardsfuel-signals/api-mcp-signals/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-rewardsfuel-signals/api-mcp-signals.json
- HTML version of this page: https://verifymcp.io/servers/com-rewardsfuel-signals/api-mcp-signals
