True Markets Market Data
REMOTE · MCP.TRUEMARKETS.CO
Real-time crypto market data
Available components
Last scanned (7 hours ago)
Scores higher than 83% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2968 tokens (~174/item across 17 items; 17 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 Management84
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 3 breaking changes, 0 auth/transport breaks, 7 additions. See how to fix → Fail
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% 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 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 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
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.
- 30 Oct 26 −5
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “get_surging_assets” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “get_surging_assets” changed the type of “limit”: string → number ▼ functional
- “get_trending_assets” changed the type of “limit”: string → number ▼ functional
- “list_market_caps” changed the type of “limit”: string → number ▼ functional
- Schema quality: excellent → good functional
- New tool “get_candles” functional
- New tool “get_market_cap_history” functional
- New tool “get_perp_market_history” functional
- New tool “get_price_at_time” functional
- New tool “get_price_indicators” functional
- New tool “get_price_range” functional
- New tool “get_volume_history” functional
- “get_price_history” added an optional parameter “asset_ids” cosmetic
- “get_market_cap” reworded the description of “symbol” cosmetic
- “get_price_history” reworded the description of “resolution” cosmetic
- “get_price_history” reworded the description of “symbols” cosmetic
- “get_price_history” reworded the description of “window” cosmetic
- “get_surging_assets” reworded the description of “limit” cosmetic
- “get_surging_assets” reworded the description of “sort” cosmetic
- “get_trending_assets” reworded the description of “limit” cosmetic
- “get_trending_assets” reworded the description of “sort” cosmetic
- “list_market_caps” reworded the description of “limit” cosmetic
- “get_price_history” made “symbols” optional cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 5 Nov 2026 · Probed https://mcp.truemarkets.co/marketdata/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=truemarkets.co | CN=WE1,O=Google Trust Services,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | e02d46679bf364c8137b9aeddb6d4b9b |
| SANs: truemarkets.co, *.truemarkets.co | ||||||
| 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.truemarkets.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| truemarkets.co. | absent | 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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.truemarkets.co/marketdata/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.truemarkets.co/marketdata/mcp | HTTPS enforced | 301 | https://mcp.truemarkets.co/marketdata/mcp |
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 →
get_asset ~44
Get details for a specific token by chain and contract address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Token contract address |
| chain | string | yes | Blockchain network (solana, base) |
No output schema declared.
No examples provided.
get_asset_summary ~43
Get a daily AI-generated summary for a specific asset including news analysis and sentiment.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Asset symbol (e.g., BTC, ETH, SOL) |
No output schema declared.
No examples provided.
get_asset_summary_history ~58
Get historical daily summaries for a specific asset.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | Number of historical summaries (default: 7, max: 30) |
| symbol | string | yes | Asset symbol (e.g., BTC, ETH, SOL) |
No output schema declared.
No examples provided.
get_candles ~323
Get OHLC candles for a symbol. Returns open/high/low/close buckets for an asset over a configurable lookback window, sampled at a configurable resolution. Use for candlestick charts and volatility measures that need the intra-bucket range rather than a single close. Only sources that store individual ticks can produce OHLC. Requesting candles for an asset priced from a derived or snapshot source returns `400`. See the [Time Window & Resolution](#section/Time-Window-and-Resolution) section for the format of `window` and `resolution`.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Ends the window at this instant instead of now, so a past period can be read. RFC3339, and not the zero time. A future instant bounds a window that is still filling. Absent reads live data. |
| asset_class | string | – | Asset class to resolve the symbol in. Defaults to `spot` (one of: spot, perp) |
| asset_id | string | – | Backend asset ID. Mutually exclusive with `symbol`: exactly one of the two is required, and naming both is a 400. |
| resolution | string | – | Candle size (e.g. `1m`, `5m`, `1h`). |
| symbol | string | – | Asset symbol to fetch candles for (e.g. `SOL`, `BTC`). |
| window | string | – | Lookback period (e.g. `1h`, `4h`, `1d`, `7d`, `1M`). |
No output schema declared.
No examples provided.
get_market_cap ~48
Get the market capitalization for a specific asset by symbol.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Asset symbol to fetch the market cap for (e.g. `BTC`, `ETH`, `SOL`). |
No output schema declared.
No examples provided.
get_market_cap_history ~238
Get reported market-cap history. Returns an asset's reported market capitalisation in USD over a configurable lookback window, sampled at a configurable resolution. Each point is the figure the data provider reported at that timestamp. The snapshot is written on the provider's ingest cadence, which is coarser than a minute, so a `resolution` of at least `1h` is what the series can actually fill. Buckets with no snapshot behind them are absent rather than zero. See the [Time Window & Resolution](#section/Time-Window-and-Resolution) section for the format of `window` and `resolution`.
| Name | Type | Req | Description |
|---|---|---|---|
| resolution | string | – | Bucket size (e.g. `5m`, `1h`, `1d`). Must be at least `1h` for windows over `1d`. |
| symbol | string | yes | Asset symbol to fetch market cap for (e.g. `SOL`, `BTC`). |
| window | string | – | Lookback period (e.g. `1h`, `4h`, `1d`, `7d`, `1M`). |
No output schema declared.
No examples provided.
get_market_summary ~36
Get a market digest with key bullets, trending assets, sentiment analysis, and sources. Returns an AI-generated summary of current market conditions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_perp_market_history ~293
Get perp funding rate and open interest history. Returns a perpetual future's funding rate and open interest over a configurable lookback window, sampled at a configurable resolution. Both series come from the same venue snapshot row, so a caller reading them together never compares values sampled at different times. `funding_rate` is the venue's hourly rate as a decimal fraction, so `0.0000125` is 0.00125% per hour. `open_interest` is a coin count of the base asset (`35984.2` for BTC), not a USD notional. See the [Time Window & Resolution](#section/Time-Window-and-Resolution) section for the format of `window` and `resolution`.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | – | Backend asset ID. Mutually exclusive with `symbol`: exactly one of the two is required, and naming both is a 400. |
| resolution | string | – | Bucket size (e.g. `5m`, `1h`, `1d`). Must be at least `1h` for windows over `1d`. |
| symbol | string | – | Perp symbol to fetch the snapshot series for (e.g. `BTC`). |
| window | string | – | Lookback period (e.g. `1h`, `4h`, `1d`, `7d`, `1M`). |
No output schema declared.
No examples provided.
get_price_at_time ~164
Get price at a point in time. Returns the last known price for an asset at or before the given timestamp. Use this to value a position, settle a trade, or anchor a calculation to a specific moment in time.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_class | string | – | Asset class to resolve the symbol in. Defaults to `spot` (one of: spot, perp) |
| asset_id | string | – | Backend asset ID. Mutually exclusive with `symbol`: exactly one of the two is required, and naming both is a 400. |
| symbol | string | – | Asset symbol to look up (e.g. `SOL`, `BTC`). |
| timestamp | number | yes | Unix timestamp in seconds. The response returns the most recent price at or before this moment. |
No output schema declared.
No examples provided.
get_price_history ~159
Get historical price data for one or more tokens. Returns timestamped price points. No authentication required.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_ids | string | – | Comma-separated list of backend asset IDs. Mutually exclusive with `symbols`: exactly one of the two is required, and naming both is a 400. |
| resolution | string | – | Gap between consecutive data points (e.g. `5s`, `1m`, `5m`, `1h`). |
| symbols | string | – | Comma-separated list of asset symbols (e.g. `SOL,BTC,ETH`). |
| window | string | – | Lookback period (e.g. `1h`, `4h`, `1d`, `7d`, `1M`). |
No output schema declared.
No examples provided.
get_price_indicators ~666
Get a technical indicator series. Returns one or more technical indicator lines computed from the asset's close prices. The requested `window` is widened internally by the indicator's warm-up depth and trimmed back before responding, so the first returned point is already converged rather than carrying seed bias. The window is measured back from the most recent available point, so a feed lagging behind the current time still returns a full window. `lines` is keyed by line name. Single-line indicators (`sma`, `ema`, `rsi`, `atr`) return one entry named after the indicator. `macd` returns `macd`, `signal` and `histogram`; `bollinger` returns `upper`, `middle`, `lower` and `percent_b`. `atr` reads OHLC candles rather than closes, so it is only available for assets whose price source stores individual ticks; anything else returns `400`. It is Wilder-smoothed and defaults to a period of 14. The momentum measures cover fixed spans rather than a caller-supplied `period`, which is rejected for them. `surging_1h`, `surging_4h` and `surging_24h` are the percent price change over that span, so the `resolution` must be coarse enough for the span to fit in 400 buckets — the same bound a supplied `period` carries. `trending_ratio` is average reported 24h volume over the last 6 hours divided by its 30-day average, so it needs a CoinGecko-mapped asset and a `resolution` of at least `1h`. VWAP is not offered: it needs per-bucket traded volume, which no price series carries.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_class | string | – | – |
| asset_id | string | – | Backend asset ID. Mutually exclusive with `symbol`: exactly one of the two is required, and naming both is a 400. |
| fast_period | number | – | MACD fast EMA length. Defaults to 12. |
| indicator | string | yes | (one of: sma, ema, rsi, macd, bollinger, atr, surging_1h, surging_4h, surging_24h, trending_ratio) |
| period | number | – | Lookback in candles. Required for sma, ema and rsi; defaults to 20 for bollinger and 14 for atr, and is not used by macd. Rejected for the momentum measures, which cover a fixed span. |
| resolution | string | – | Candle size the period counts in (e.g. 1m, 1h, 1d) |
| signal_period | number | – | MACD signal EMA length. Defaults to 9. |
| slow_period | number | – | MACD slow EMA length. Defaults to 26; must exceed fast_period. |
| std_dev | number | – | Bollinger band width in standard deviations. Defaults to 2. |
| symbol | string | – | Asset symbol (e.g. SOL, BTC) |
| window | string | – | Time window for the series (e.g. 1d, 7d, 1M) |
No output schema declared.
No examples provided.
get_price_range ~212
Get min/max price over a window. Returns the minimum and maximum price observed for an asset within a configurable lookback window, along with the timestamps at which each extreme occurred. Useful for surfacing 24h highs/lows or computing period-over-period statistics. See the [Time Window & Resolution](#section/Time-Window-and-Resolution) section for the format of `window`.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_class | string | – | Asset class to resolve the symbol in. Defaults to `spot` (one of: spot, perp) |
| asset_id | string | – | Backend asset ID. Mutually exclusive with `symbol`: exactly one of the two is required, and naming both is a 400. |
| symbol | string | – | Asset symbol to fetch the range for (e.g. `SOL`, `BTC`). |
| window | string | – | Lookback period (e.g. `1h`, `4h`, `1d`, `7d`, `1M`). |
No output schema declared.
No examples provided.
get_surging_assets ~49
Get assets with unusual recent price or volume moves.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Assets to return. |
| sort | string | – | Rank ascending instead of descending (one of: asc, desc) |
No output schema declared.
No examples provided.
get_trending_assets ~46
Get assets trending by trading volume.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Assets to return. |
| sort | string | – | Rank ascending instead of descending (one of: asc, desc) |
No output schema declared.
No examples provided.
get_volume_history ~242
Get reported 24h volume history. Returns an asset's reported 24h volume in USD over a configurable lookback window, sampled at a configurable resolution. Each point is the rolling 24h figure the data provider reported at that timestamp, not the volume traded inside the bucket. Two adjacent points therefore overlap by almost a full day. See the [Time Window & Resolution](#section/Time-Window-and-Resolution) section for the format of `window` and `resolution`.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | – | Backend asset ID. Mutually exclusive with `symbol`: exactly one of the two is required, and naming both is a 400. |
| resolution | string | – | Bucket size (e.g. `5m`, `1h`, `1d`). Must be at least `1h` for windows over `1d`. |
| symbol | string | – | Asset symbol to fetch reported volume for (e.g. `SOL`, `BTC`). |
| window | string | – | Lookback period (e.g. `1h`, `4h`, `1d`, `7d`, `1M`). |
No output schema declared.
No examples provided.
list_assets ~45
List all available tradeable tokens. Returns symbol, name, chain, address, and decimals for each asset.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Filter by blockchain (solana, base) |
No output schema declared.
No examples provided.
list_market_caps ~43
List all assets ranked by market capitalization in descending order.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of assets to return. Defaults to `10`; maximum is `50`. |
No output schema declared.
No examples provided.
How do I install the True Markets Market Data MCP server?
True Markets Market Data is a hosted endpoint at https://mcp.truemarkets.co/marketdata/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.truemarkets.co
claude mcp add --transport http co-truemarkets-marketdata 'https://mcp.truemarkets.co/marketdata/mcp'
What is the True Markets Market Data MCP server?
True Markets Market Data is an MCP server listed in the public MCP registry as co.truemarkets/marketdata. Real-time crypto market data. This page covers its hosted endpoint (https://mcp.truemarkets.co/marketdata/mcp).
Is the True Markets Market Data MCP server safe to use?
True Markets Market Data scores 81 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 True Markets Market Data MCP server expose?
True Markets Market Data exposes 17 tools: get_asset, get_asset_summary, get_asset_summary_history, get_candles, get_market_cap, and 12 more. Their descriptions and schemas cost roughly 2,709 tokens of context every time the server is loaded.
Does the True Markets Market Data MCP server require authentication?
No. We connected to True Markets Market Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the True Markets Market Data MCP server still maintained?
True Markets Market Data is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.