Skip to content

Aperiodic — Market Data for Tokenized Assets & Crypto MCP server

io.aperiodic/market-dataaperiodic.iostreamable-httpv1.0.3Scanned

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

8 tools: 2 change things and 6 only read.

Tools: 0 delete, 0 irreversible, 2 write, 6 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Aperiodic — Market Data for Tokenized Assets & Crypto MCP server can do

The Aperiodic — Market Data for Tokenized Assets & Crypto MCP server is published by aperiodic.io, a domain the MCP Registry verified. It has 8 tools. It can create or change data (2 tools: get_data and live_feed), but cannot delete data. 6 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 16, 2026, version 1.0.3.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Changes things 2Claude Code: ask
  • get_dataA 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 P…1 finding

    Why it is in this group

    • The name "get_data" says "get": a word for reading.
    • The description's first verb is "handle": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "get_data" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_data" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get a data handle
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • live_feedHow 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 symbol…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Connect to the live feed
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 6Show 6 read-only tools
  • describe_datasetField definitions, intervals, exchanges with their start dates, the plan needed and the free preview window for one dataset.No findings

    Why it is in this group

    • The name "describe_dataset" says "describe": a word for reading.
    Description, as the server wrote it
    Field definitions, intervals, exchanges with their start dates, the plan needed and the free preview window for one dataset.

    Annotations the server declares

    • title: Describe a dataset
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • fetchThe full text of one search result: a dataset with all its fields, a category, or the plans guide.No findings

    Why it is in this group

    • The name "fetch" says "fetch": a word for reading.
    Description, as the server wrote it
    The full text of one search result: a dataset with all its fields, a category, or the plans guide.

    Annotations the server declares

    • title: Fetch a catalog document
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • find_symbolsSymbol ids on one exchange matching every word of the query, at most 50: crypto and RWA perpetuals alike.No findings

    Why it is in this group

    • The name "find_symbols" says "find": a word for reading.
    Description, as the server wrote it
    Symbol ids on one exchange matching every word of the query, at most 50: crypto and RWA perpetuals alike. 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). Matching is on the id, so search by ticker (e.g. "TSLA"), not by company name. The free preview symbol is perpetual-BTC-USDT:USDT on binance-futures.

    Annotations the server declares

    • title: Find symbols
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_datasetsEvery 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.No findings

    Why it is in this group

    • The name "list_datasets" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List datasets
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • summarizeStatistics 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 resa…No findings

    Why it is in this group

    • The name "summarize" says "summarize": a word for reading.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Summarize a slice
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:22 UTC, unchanged since Nov 7, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://aperiodic.io/.well-known/oauth-protected-resource/mcp
Authorization servers
https://aperiodic.io
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://aperiodic.io/mcp: tools/list returned 8 tools to an anonymous client, including get_data (write), live_feed (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "get_data" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_data" says "get": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff

Install

Pinned to version 1.0.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http market-data https://aperiodic.io/mcp
claude mcp add --transport http market-data https://aperiodic.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__market-data__list_datasets",
      "mcp__market-data__describe_dataset",
      "mcp__market-data__find_symbols",
      "mcp__market-data__summarize",
      "mcp__market-data__search",
      "mcp__market-data__fetch"
    ],
    "ask": [
      "mcp__market-data__get_data",
      "mcp__market-data__live_feed"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as market-data. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.aperiodic/market-data/verify?hash=f38d131fd74eb5ca74f365b6c00829011528c86b56ba479c0b5a94854f8adfd0" | jq -e '.changed == false'

Pinned hash f38d131fd74e, from Nov 16, 2026, 21:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.aperiodic/market-data/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.aperiodic/market-data
[![Anlyon Radar](https://radar.anlyon.com/badge/io.aperiodic/market-data.svg)](https://radar.anlyon.com/servers/io.aperiodic/market-data)

Source: MCP Registry. Synced Nov 16, 2026, 22:17 UTC.

Aperiodic — Market Data for Tokenized Assets & Crypto MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

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

No scan can promise that. What its definitions show: 8 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Aperiodic — Market Data for Tokenized Assets & Crypto MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Aperiodic — Market Data for Tokenized Assets & Crypto MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Aperiodic — Market Data for Tokenized Assets & Crypto MCP server have?

8 tools: 2 write, 6 read. get_data, live_feed, list_datasets, describe_dataset, find_symbols, summarize, search and fetch.

Does the Aperiodic — Market Data for Tokenized Assets & Crypto MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Aperiodic — Market Data for Tokenized Assets & Crypto MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Aperiodic — Market Data for Tokenized Assets & Crypto MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.