# RealtimeAPI.ai (remote · mcp.realtimeapi.ai)

Live data for AI agents: crypto, Hyperliquid, stocks, news, macro, predictions. Free key or x402.

- Trust score: 64/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.realtimeapi.ai`: 64/100 (this document), [markdown](https://verifymcp.io/servers/ai-realtimeapi-mcp/mcp.md), [page](https://verifymcp.io/servers/ai-realtimeapi-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.realtimeapi.ai/mcp`
- 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**: 46/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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 70/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 808 tokens (~134/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 94% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the RealtimeAPI.ai MCP server?

RealtimeAPI.ai is a hosted endpoint at https://mcp.realtimeapi.ai/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.

### Claude

```bash
claude mcp add --transport http ai-realtimeapi-mcp 'https://mcp.realtimeapi.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-realtimeapi-mcp": {
      "url": "https://mcp.realtimeapi.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-realtimeapi-mcp": {
      "type": "http",
      "url": "https://mcp.realtimeapi.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-realtimeapi-mcp]
url = "https://mcp.realtimeapi.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-realtimeapi-mcp": {
      "type": "remote",
      "url": "https://mcp.realtimeapi.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-realtimeapi-mcp --url 'https://mcp.realtimeapi.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-realtimeapi-mcp:
    url: "https://mcp.realtimeapi.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-realtimeapi-mcp": {
      "Transport": "http",
      "Url": "https://mcp.realtimeapi.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-realtimeapi-mcp -t streamable-http -u 'https://mcp.realtimeapi.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-realtimeapi-mcp": {
      "type": "http",
      "url": "https://mcp.realtimeapi.ai/mcp"
    }
  }
}
```

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 64, +1)

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

### 2026-11-17 (score 63, +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.

### 2026-11-15 (score 62, +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.

### 2026-11-13 (score 61, +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.

### 2026-11-11 (score 60, +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-10 (score 59, 0)

- [security] Tool “discover” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03

### 2026-11-09 (score 59)

First indexed and scored.

## MCP tools (6)

### `discover` (~94 tokens)

Search all feeds for endpoints matching a need. Returns up to `limit` ranked endpoints with price, params and latency (`latency.by_region`: cache-miss ms per Cloudflare region).

Input parameters:

- `limit` (integer): Results, default and max 5
- `max_price` (number): Max USD per call, e.g. 0.01
- `query` (string, required): What data you need, in plain words

### `get_sample` (~94 tokens)

Free trimmed sample of an endpoint's real response from the probe's cached copy (no key, no payment): see the data shape before paying. Works for results discover marks sample: true.

Input parameters:

- `tool` (string): Tool name from discover, e.g. "cryptodata_market-health"
- `url` (string): Gateway URL, e.g. https://api.realtimeapi.ai/v1/cryptodata/market-health

### `list_feeds` (~29 tokens)

List all live feeds with endpoint counts, per-call price range, plans and their paid MCP URL.

### `get_quote` (~118 tokens)

Price an endpoint without calling it: x402 `accepts` for one call plus time-pass plans. Nothing is charged.

Input parameters:

- `method` (string): HTTP method for url (default GET)
- `params` (object): Endpoint params by name (path params fill the URL, the rest become query params)
- `tool` (string): Tool name from discover, e.g. "cryptodata_market-health"
- `url` (string): Gateway URL, e.g. https://api.realtimeapi.ai/v1/cryptodata/market-health

### `call_feed` (~165 tokens)

Call a feed endpoint through the gateway with your API key (or an x402 payment). Without either it returns the 402 payment options.

Input parameters:

- `api_key` (string): rta_live_ key; defaults to this server's X-API-Key header
- `method` (string): HTTP method for url (default GET)
- `params` (object): Endpoint params by name (path params fill the URL, the rest become query params)
- `payment` (string): base64 x402 PAYMENT-SIGNATURE answering a previous 402
- `tool` (string): Tool name from discover, e.g. "cryptodata_market-health"
- `url` (string): Gateway URL, e.g. https://api.realtimeapi.ai/v1/cryptodata/market-health

### `create_free_key` (~58 tokens)

Create a free API key (1,000 calls/month, all feeds) for the user's real email. Works at once; signing in at realtimeapi.ai with that email later re-issues the secret once.

Input parameters:

- `email` (string, required)

## Diagnostics

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

## Score history

- 2026-11-21: 64
- 2026-11-20: 64
- 2026-11-19: 63
- 2026-11-18: 63
- 2026-11-17: 63
- 2026-11-16: 62
- 2026-11-15: 62
- 2026-11-14: 61
- 2026-11-13: 61
- 2026-11-12: 60
- 2026-11-11: 60
- 2026-11-10: 59
- 2026-11-09: 59

## Common questions

### What is the RealtimeAPI.ai MCP server?

RealtimeAPI.ai is an MCP server listed in the public MCP registry as ai.realtimeapi/mcp. Live data for AI agents: crypto, Hyperliquid, stocks, news, macro, predictions. Free key or x402. This page covers its hosted endpoint (https://mcp.realtimeapi.ai/mcp).

### Is the RealtimeAPI.ai MCP server safe to use?

RealtimeAPI.ai scores 64 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 RealtimeAPI.ai MCP server expose?

RealtimeAPI.ai exposes 6 tools: discover, get_sample, list_feeds, get_quote, call_feed, create_free_key. Their descriptions and schemas cost roughly 558 tokens of context every time the server is loaded.

### Does the RealtimeAPI.ai MCP server require authentication?

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

### Is the RealtimeAPI.ai MCP server still maintained?

RealtimeAPI.ai 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 RealtimeAPI.ai MCP server?

VerifyMCP ran 11 checks on RealtimeAPI.ai, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about RealtimeAPI.ai: Authorization and HTTPS. 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://mcp.realtimeapi.ai/mcp
- Website: https://realtimeapi.ai/docs#mcp
- Changelog RSS feed: https://verifymcp.io/servers/ai-realtimeapi-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-realtimeapi-mcp/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-realtimeapi-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-realtimeapi-mcp/mcp
