Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Aperiodic — Market Data for Tokenized Assets & Crypto

REMOTE · APERIODIC.IO

Stock, gold, oil, FX & crypto perps: microstructure, liquidity, order flow and raw data, live.

Available components

+3 this week 75 Trust /100

Last scanned (14 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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
Schema Quality & AI Usability58
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1691 tokens (~211/item across 8 items; 8 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 Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 82% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

Changelog

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.

  • 21 Nov 26 +1

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

  • 20 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “find_symbols” rewrote its description, which is the text the model reads security
    • Schema quality: 191 → 211 ▼ functional
    • “find_symbols” added an optional parameter “asset_class” cosmetic
    • “find_symbols” reworded the description of “query” cosmetic
  • 18 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 14 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.

  • 12 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.

  • 11 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 10 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.

Diagnostics

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://aperiodic.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=aperiodic.io CN=WE1,O=Google Trust Services,C=US 2 Nov 2026 31 Jan 2027 ECDSA 256 ECDSA-SHA256 2800cff241e25eed0e5081b090bc79aa
SANs: aperiodic.io, dataroom-factors.aperiodic.io, *.dataroom-factors.aperiodic.io
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 aperiodic.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
aperiodic.io. 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://aperiodic.io/mcp Verified 200
http (plaintext) http://aperiodic.io/mcp HTTPS enforced 301 https://aperiodic.io/mcp
MCP tools · 8 exposed · ~1,269 tokens

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 →

Tool Tokens
describe_dataset ~58

Field definitions, intervals, exchanges with their start dates, the plan needed and the free preview window for one dataset.

NameTypeReqDescription
datasetstringyesA dataset id from list_datasets, e.g. "flow" or "raw:trades".

No output schema declared.

No examples provided.

fetch ~41

The full text of one search result: a dataset with all its fields, a category, or the plans guide.

NameTypeReqDescription
idstringyesAn id from search.

No output schema declared.

No examples provided.

find_symbols ~324

Symbol ids on one exchange matching every word of the query, at most 50: crypto and real-world asset (RWA) perpetuals alike. A word matches the id or the asset's name, so "TSLA", "Tesla", "gold", "S&P 500" and "crude oil" all work; exact tickers and names come first. Each result has its asset class (crypto, stock, etf, index, commodity, fx, pre-ipo, or rwa when the class is not known yet), the underlying's name where known, and a HIP-3 market's dex. Ids look like "perpetual-BTC-USDT:USDT", "perpetual-TSLA-USDT:USDT" for a tokenized stock on Binance, or "perpetual-XYZ:TSLA-USDC:USDC" for a Hyperliquid HIP-3 market (dex before the colon). The free preview symbol is perpetual-BTC-USDT:USDT on binance-futures.

NameTypeReqDescription
asset_classstring–Only symbols of this class: "crypto", one real-world class ("stock", "etf", "index", "commodity", "fx", "pre-ipo"), or "rwa" for every real-world asset.
exchangestringyes–
querystring–Words to match against the id and the asset's name, e.g. "BTC USDT", "Tesla", "gold" or "XYZ TSLA". Empty lists the first 50.

No output schema declared.

No examples provided.

get_data ~273

A handle to one slice of a dataset, not the data: signed Parquet URLs (valid one hour), schema, row counts, per-column min/max/nulls from the Parquet footers, 5 sample rows and a Polars snippet. Load the files in your own code; never paste them into the conversation. Without code, use summarize. Every argument but dataset defaults to the free preview, which needs no API key.

NameTypeReqDescription
datasetstringyesA dataset id from list_datasets: a metrics dataset such as "flow", or a raw one such as "raw:trades".
end_datestring–YYYY-MM-DD, inclusive. Default: the end of the free preview month.
exchangestring–Default binance-futures.
intervalstring–Metrics only: bar interval. Default 5m.
start_datestring–YYYY-MM-DD, inclusive. Default: the free preview, 2025-05-01 for metrics, 2025-06-01 for raw.
symbolstring–Symbol id from find_symbols. Default perpetual-BTC-USDT:USDT.
timestampstring–Metrics only: 'exchange' uses the exchange-reported timestamp (default), 'true' the arrival time at our servers.

No output schema declared.

No examples provided.

list_datasets ~53

Every Aperiodic dataset, metrics and raw: id, category, the plan that unlocks it, a one-line description, field count, and whether this caller gets full access or the free preview. Start here.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

live_feed ~142

How your own code connects to the real-time WebSocket feed of metrics datasets (raw data is not streamed): its URL, the subscribe frame for a dataset, exchange, interval and symbols, your plan's limits and a Python client. Never the stream itself, which your code consumes outside MCP. The stream authenticates with an API key in X-API-KEY, not an MCP OAuth sign-in. With no dataset, lists what streams and which plans include it.

NameTypeReqDescription
datasetstring––
exchangestring––
intervalstring––
symbolsarray–Symbol ids. Default perpetual-BTC-USDT:USDT.

No output schema declared.

No examples provided.

search ~42

Keyword search over every dataset, its fields, the categories and the plans guide. Returns ids, titles and URLs; read one with fetch.

NameTypeReqDescription
querystringyes–

No output schema declared.

No examples provided.

summarize ~336

Statistics worked out on our side, for when you can't run code: per-column count, mean, std, quantiles and range ("stats"), a correlation matrix ("correlation"), or the series resampled to at most 500 points ("resample"). Same slice arguments and plan rules as get_data. Decodes only the columns you name (up to 12, numeric; default the first 6).

NameTypeReqDescription
aggregatestring–resample only: how a bucket is reduced. Default "mean".
analysisstring–Default "stats".
columnsarray–Numeric field names from describe_dataset. Default: the first 6.
datasetstringyesA dataset id from list_datasets: a metrics dataset such as "flow", or a raw one such as "raw:trades".
end_datestring–YYYY-MM-DD, inclusive. Default: the end of the free preview month.
exchangestring–Default binance-futures.
intervalstring–Metrics only: bar interval. Default 5m.
pointsinteger–resample only: buckets across the range. Default 200.
start_datestring–YYYY-MM-DD, inclusive. Default: the free preview, 2025-05-01 for metrics, 2025-06-01 for raw.
symbolstring–Symbol id from find_symbols. Default perpetual-BTC-USDT:USDT.
timestampstring–Metrics only: 'exchange' uses the exchange-reported timestamp (default), 'true' the arrival time at our servers.

No output schema declared.

No examples provided.

Install

How do I install the Aperiodic — Market Data for Tokenized Assets & Crypto MCP server?

Aperiodic — Market Data for Tokenized Assets & Crypto is a hosted endpoint at https://aperiodic.io/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 · aperiodic.io

# add to Claude Code
claude mcp add --transport http io-aperiodic-market-data 'https://aperiodic.io/mcp'
Common questions

What is the Aperiodic — Market Data for Tokenized Assets & Crypto MCP server?

Aperiodic — Market Data for Tokenized Assets & Crypto is an MCP server listed in the public MCP registry as io.aperiodic/market-data. Stock, gold, oil, FX & crypto perps: microstructure, liquidity, order flow and raw data, live. This page covers its hosted endpoint (https://aperiodic.io/mcp).

Is the Aperiodic — Market Data for Tokenized Assets & Crypto MCP server safe to use?

Aperiodic — Market Data for Tokenized Assets & Crypto scores 75 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 Aperiodic — Market Data for Tokenized Assets & Crypto MCP server expose?

Aperiodic — Market Data for Tokenized Assets & Crypto exposes 8 tools: list_datasets, describe_dataset, find_symbols, get_data, summarize, and 3 more. Their descriptions and schemas cost roughly 1,269 tokens of context every time the server is loaded.

Does the Aperiodic — Market Data for Tokenized Assets & Crypto MCP server require authentication?

No. We connected to Aperiodic — Market Data for Tokenized Assets & Crypto without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Aperiodic — Market Data for Tokenized Assets & Crypto MCP server still maintained?

Aperiodic — Market Data for Tokenized Assets & Crypto 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 Aperiodic — Market Data for Tokenized Assets & Crypto MCP server?

VerifyMCP ran 13 checks on Aperiodic — Market Data for Tokenized Assets & Crypto, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.