RealtimeAPI.ai
REMOTE · MCP.REALTIMEAPI.AI
Live data for AI agents: crypto, Hyperliquid, stocks, news, macro, predictions. Free key or x402.
Available components
Last scanned (15 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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 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. 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 Usability70
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (11)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation 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 in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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 Nov 26 +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.
- 17 Nov 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.
- 15 Nov 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.
- 13 Nov 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.
- 11 Nov 26 +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.
- 10 Nov 26 0
- Tool “discover” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 9 Nov 26 59
First indexed and scored.
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 21 Nov 2026 · Probed https://mcp.realtimeapi.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=realtimeapi.ai | CN=WE1,O=Google Trust Services,C=US | 8 Oct 2026 | 7 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | aabddedf9eaf73cc13bd06fee32864c5 |
| SANs: realtimeapi.ai, mcp.realtimeapi.ai, *.mcp.realtimeapi.ai | ||||||
| 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.realtimeapi.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| realtimeapi.ai. | No DS | 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.realtimeapi.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.realtimeapi.ai/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 →
call_feed ~165
Call a feed endpoint through the gateway with your API key (or an x402 payment). Without either it returns the 402 payment options.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
create_free_key ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – |
No output schema declared.
No examples provided.
discover ~94
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).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results, default and max 5 |
| max_price | number | – | Max USD per call, e.g. 0.01 |
| query | string | yes | What data you need, in plain words |
No output schema declared.
No examples provided.
get_quote ~118
Price an endpoint without calling it: x402 `accepts` for one call plus time-pass plans. Nothing is charged.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
get_sample ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
list_feeds ~29
List all live feeds with endpoint counts, per-call price range, plans and their paid MCP URL.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
remote · mcp.realtimeapi.ai
claude mcp add --transport http ai-realtimeapi-mcp 'https://mcp.realtimeapi.ai/mcp'
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.