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.

zdte.ai SPX Market Structure

REMOTE · API.ZDTE.AI

SPX 0DTE dealer market structure: GEX, walls, gamma flip, regime, flow. Free preview; pay per read.

Available components

0 this week 91 Trust /100

Last scanned (21 hours ago)

Scores higher than 98% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

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 Security83
  • 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
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability86
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1492 tokens (~106/item across 14 items; 13 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 15 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.

  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 25 Oct 26 0
    • Tool “subscribe_event” rewrote its description, which is the text the model reads security
    • Schema quality: 91 → 104 ▼ functional
  • 24 Oct 26 0
    • Tool “get_field_guide” rewrote its description, which is the text the model reads security
  • 18 Oct 26 0
    • DNSSEC: fail → pass ▲ security
  • 10 Oct 26 0
    • Schema quality: 100 → 90 ▲ functional
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://api.zdte.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=zdte.ai CN=YE2,O=Let's Encrypt,C=US 21 Oct 2026 19 Jan 2027 ECDSA 256 ECDSA-SHA384 54b039555e863d2c345fce942ecfa6474c6
SANs: *.zdte.ai, zdte.ai
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of api.zdte.ai. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
zdte.ai. DS published 2371 13 Verified
api.zdte.ai. Verified address RRset verified with the apex keys
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
strict-transport-security max-age=15552000
content-security-policy default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data:; connect-src 'self' https://zdte.ai https://api.zdte.ai https://*.zdte.ai wss://api.zdte.ai wss://*.zdte.ai; frame-src 'none'; frame-ancestors 'none'; base-uri 'self'; form-action 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.zdte.ai/mcp Verified 200
http (plaintext) http://api.zdte.ai/mcp HTTPS enforced 301 https://api.zdte.ai/mcp
MCP tools · 13 exposed · ~1,099 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
create_credit_checkout ~83

Create a payment link that adds prepaid credits to the authenticated key; a person opens it to pay. Does not charge or fund anything until payment is authorized and confirmed.

NameTypeReqDescription
creditsintegeryesWhole number of credits to buy, within the published minimum and maximum purchase. Each credit costs the published credit_unit_price_cents; the checkout total is credits times that price.

No output schema declared.

No examples provided.

create_guest_key ~87

Creates a zero-credit API key, returned once and not shown again. When the response says connection_authenticated, this MCP session already uses the key; other connections authenticate with an HTTP Authorization: Bearer header. No arguments. For OAuth-capable clients, a Connect prompt appears automatically the first time an account or paid tool is called, with no website account needed, so no key is required.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_access_options ~25

Free: current prices and the accountless access steps; no website account required.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_credit_balance ~28

Free balance check for the API key in this connection's HTTP header; takes no key argument.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_day ~92

The full market-structure history of one past trading day, the larger replay: the intraday timeline (walls, gamma flip, net GEX, regime, spot) plus a day summary. One replay date (YYYY-MM-DD) per call. Data only -- not investment advice or a trade recommendation.

NameTypeReqDescription
datestringyesReplay date in YYYY-MM-DD, one of the dates in the replay date catalog.

No output schema declared.

No examples provided.

get_field_guide ~72

Static, versioned dictionary of every field this surface emits: unit, value set where the field has a fixed one, and a one-sentence meaning, plus the shared response conventions (tier, delay, timestamps, and how missing data is reported) and a changelog. No inputs; static per version.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_market_structure ~217

The full current SPX dealer market structure, the largest realtime read: walls, gamma flip, net GEX, regime and the strike-level detail below. Current computed SPX dealer market structure (walls, gamma flip, net GEX, regime), recomputed ~every 10s during market hours: scored pressure-point strike ladder, implied 50%/80% forecast-band ranges, strike activity (volume/OI), and VIX term-structure context. Also the 0DTE ATM-straddle expected move and its session fence, max pain, the running session open/high/low with the prior close and gap, order-flow measurements, a top-10 net-GEX strike profile, and chain vanna/charm totals with a top-10 strike ladder. The full realtime structure needs a funded zdte.ai API key (no website account needed); without a key this returns a delayed headline preview (regime, spot, walls, gamma flip, net GEX). Data only -- not investment advice or a trade recommendation.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_regime ~60

Only the current SPX dealer regime label and its confidence, a small read for checking whether conditions have changed; no walls, gamma flip, net GEX or strike detail. Realtime with an API key; without a key this serves a delayed preview.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_regime_segments ~84

Only how the dealer regime changed during one past trading day, the compact replay: a list of regime segments with their start and end times; no walls, gamma flip, net GEX or spot. One replay date (YYYY-MM-DD) per call.

NameTypeReqDescription
datestringyesReplay date in YYYY-MM-DD, one of the dates in the replay date catalog.

No output schema declared.

No examples provided.

list_history_dates ~33

Free catalog of available historical SPX market-structure replay dates. No API key required; actual replay datasets are paid.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_subscriptions ~17

List this agent's active event subscriptions.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

subscribe_event ~258

Subscribe a callback URL to a market-structure event (zero_gamma_flip | new_wall | regime_transition). The answer includes signing_secret, shown only once: store it. Each time the event fires, the callback receives an HTTPS POST whose JSON body has id (one per delivered event; ignore a repeat), event, at (ISO 8601 UTC time of the market snapshot the event was seen in), subscription_id and data, the event's values: zero_gamma_flip has gamma_flip and spot, new_wall has which (call_wall or put_wall) and level, regime_transition has from and to. To verify a delivery, read the ZDtE-Signature header, t=<unix seconds>,v1=<hex>: compute HMAC-SHA256 keyed with signing_secret exactly as returned (its text as bytes; do not hex-decode it) over t, a period and the raw request body, compare it with v1 in constant time, and reject the delivery if t is more than 5 minutes old.

NameTypeReqDescription
callback_urlstringyesHTTPS URL that receives a POST when the event fires.
eventstringyesWhich market-structure event to subscribe to: zero_gamma_flip, new_wall, or regime_transition.

No output schema declared.

No examples provided.

unsubscribe_event ~43

Remove an event subscription by its subscription_id (the id returned when the subscription was created).

NameTypeReqDescription
subscription_idstringyesThe subscription id returned when the subscription was created.

No output schema declared.

No examples provided.

Install

How do I install the zdte.ai SPX Market Structure MCP server?

zdte.ai SPX Market Structure is a hosted endpoint at https://api.zdte.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 · api.zdte.ai

# add to Claude Code
claude mcp add --transport http ai-zdte-market-structure 'https://api.zdte.ai/mcp'
Common questions

What is the zdte.ai SPX Market Structure MCP server?

zdte.ai SPX Market Structure is an MCP server listed in the public MCP registry as ai.zdte/market-structure. SPX 0DTE dealer market structure: GEX, walls, gamma flip, regime, flow. Free preview; pay per read. This page covers its hosted endpoint (https://api.zdte.ai/mcp).

Is the zdte.ai SPX Market Structure MCP server safe to use?

zdte.ai SPX Market Structure scores 91 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 zdte.ai SPX Market Structure MCP server expose?

zdte.ai SPX Market Structure exposes 13 tools: get_market_structure, get_regime, list_history_dates, get_day, get_regime_segments, and 8 more. Their descriptions and schemas cost roughly 1,099 tokens of context every time the server is loaded.

Does the zdte.ai SPX Market Structure MCP server require authentication?

No. We connected to zdte.ai SPX Market Structure without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the zdte.ai SPX Market Structure MCP server still maintained?

zdte.ai SPX Market Structure 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 zdte.ai SPX Market Structure MCP server?

VerifyMCP ran 13 checks on zdte.ai SPX Market Structure, 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.