Skip to content

quantdata MCP server

uk.quantdata/quantdataquantdata.ukstreamable-httpv1.1.0Scanned

Four market-statistics tools + a free qd_ key by email: 1 anonymous look, then 10 calls/UTC day.

3 tools: 3 change things.

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

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

3 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the quantdata MCP server can do

The quantdata MCP server is published by quantdata.uk, a domain the MCP Registry verified. It has 3 tools. It can create or change data (3 tools: quantdata_request_free_api_key, quantdata_brooks_events and quantdata_weis_wave), but cannot delete data. None of its tools only reads.

3 tools bring in text other people can write (quantdata_request_free_api_key, quantdata_brooks_events and quantdata_weis_wave).

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

Last scanned Oct 21, 2026, version 1.1.0.

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.

3 tools

Changes things 3Claude Code: ask
  • quantdata_brooks_eventsClassical Brooks price-action events detected in the current trading window — the day's first range breakout, breakout follow-through, closes in the top or bottom third of an estab…Reads text others write1 finding

    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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 3,099 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...tistics — not a recommendation. Check window_is_live before calling a read 'now'."

      What this check looks for
    Description, as the server wrote it
    Classical Brooks price-action events detected in the current trading window — the day's first range breakout, breakout follow-through, closes in the top or bottom third of an established range, long-lived-range breakouts, climactic spikes — each paired with the outcome rate measured for that exact definition in that exact window (pre-registered, ES 5-minute bars 2010-2026). Range breakouts also carry a calibrated per-event estimate of the probability the breakout closes back through its level within 10 bars (validated zero-shot on NQ 2023+: AUC 0.646, calibration error 5.1%, n=2,637). Answers 'what just happened structurally, and how did events like it resolve historically'. Works around the clock on 24-hour instruments, including the Asia-close-to-US-open gap window. Some measured rates contradict the classical claims; quote the measured numbers, not the folklore. Every read also carries two blocks that answer different questions and must not be mixed: `day_type` is the five-class day-type distribution, from the model trained for the current window. In the regular day session it is mode=day_session, with published accuracy: 66% top-1 over a complete session and 53.5% at the 90-minute mark, against a 37% majority-class baseline. In the Asian window it is mode=asia_session — trained natively on Asian windows, pre-registered, confirmed zero-shot on NQ — whose accuracy figures live in the response's own `accuracy` field and use their own label taxonomy: never quote the day-session figures for an asia read or vice versa. The gap window has no validated model and returns available=false there. `shape` is plain arithmetic over the bars already printed (where price closed inside its own range, how much of the travel was one-way, deepest pullback) — no model, no accuracy claim, available in every window including the gap. Report day_type as a distribution with its baseline; report shape as measurement, never as a forecast. **`day_type.analysis` is the block to lead with (day-session reads only; the asia_session read carries no analysis layer)** — it answers 'should today's read be trusted at all' before it answers 'what is today'. It carries: `confidence` (the model's own conviction crossed with how consistently the most similar past sessions resolved — both high has been right 95% of the time, both low only 41%, against a 66% baseline; say which bucket today falls in and stop treating a low-confidence read as a call); `live_now` (patterns mechanically confirmed on today's bars so far — e.g. 'broke yesterday's low then reclaimed it = bear trap confirmed' — this is what actually happened, trust it over any statistical checklist); `what_to_watch` (patterns over-represented on this day type, each with a status_today of yes/no/forming/unknown and a concrete way to verify it intraday; use the ordering, not the raw lift decimals); and `summary` / `summary_zh`, a one-line verdict written to be relayed verbatim — if you pass along only one sentence, pass that one. Descriptive statistics — not a recommendation. Check window_is_live before calling a read 'now'.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • quantdata_request_free_api_keyRequest an email verification link for the user's real inbox.Reads text others writeNo findings

    Why it is in this group

    • The name "quantdata_request_free_api_key" says "request": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Request an email verification link for the user's real inbox. No key or free API entitlement is returned by this tool. Ask the user for their own address; never invent one. The owner must open the email and press the confirmation button before receiving a key. After verification, they can configure X-API-Key in this client. All two market-data tools share 10 successful calls per UTC day. No account, card or payment is required.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • quantdata_weis_waveWeis Wave volume-price structure: price grouped into waves with volume summed per wave, plus which of five classical volume-price events have fired.Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Weis Wave volume-price structure: price grouped into waves with volume summed per wave, plus which of five classical volume-price events have fired. Each event carries the win rate measured for it on sixteen years of S&P 500 futures data, including the two that came out REVERSED against the tradition. Answers 'is there volume behind this move'. Quote the measured reference numbers rather than the folklore. Spot FX has no volume at all — use CME currency futures (6E=F) instead. GC=F carries exchange volume and is the gold instrument here. A spot-gold request (XAUUSD) answers with the XAUT-USD token reading plus a note — that is the Tether Gold token's order book, a different instrument. Use session='full' to match the published reference-rate window, or the default 'rth' for a regular-session-only read.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true

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 outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
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.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 19:20 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
525
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 525.

Posture changes

  1. Oct 29, 2026
    • HTTP status of an anonymous initialize: 200 to 525
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

1 info

History

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

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 525; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 3 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 525
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none

Install

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

claude mcp add --transport http quantdata https://api.quantdata.uk/mcp
claude mcp add --transport http quantdata https://api.quantdata.uk/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": [],
    "ask": [
      "mcp__quantdata__quantdata_request_free_api_key",
      "mcp__quantdata__quantdata_brooks_events",
      "mcp__quantdata__quantdata_weis_wave"
    ],
    "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 quantdata. Review it before you use it.

Capability tags behind 3 rules
  • mcp__quantdata__quantdata_request_free_api_key untrusted-input
  • mcp__quantdata__quantdata_brooks_events untrusted-input
  • mcp__quantdata__quantdata_weis_wave untrusted-input

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/uk.quantdata/quantdata/verify?hash=90969c2cb5fad777119c6b73988fe12d5f9be44e62ecf25591c9c75bd93f55ee" | jq -e '.changed == false'

Pinned hash 90969c2cb5fa, from Oct 21, 2026, 19:16 UTC.

Watch

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

https://radar.anlyon.com/servers/uk.quantdata/quantdata/changes.xml

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

Badge

Anlyon Radar badge for uk.quantdata/quantdata
[![Anlyon Radar](https://radar.anlyon.com/badge/uk.quantdata/quantdata.svg)](https://radar.anlyon.com/servers/uk.quantdata/quantdata)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:55 UTC.

quantdata MCP server: questions and answers

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

Is the quantdata MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 3 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 quantdata MCP server delete data?

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

Can the quantdata 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 quantdata MCP server have?

3 tools: 3 write. quantdata_request_free_api_key, quantdata_brooks_events and quantdata_weis_wave.

Does the quantdata MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the quantdata MCP server send data to outside services?

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

Has the quantdata MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.