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 · SCANNED OCT 2

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

Available components

0 this week 81 Trust /100
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 Security63
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 993 tokens (~76/item across 13 items; 13 tools + 0 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 14 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
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'
// .cursor/mcp.json
{
  "mcpServers": {
    "ai-zdte-market-structure": {
      "url": "https://api.zdte.ai/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ai-zdte-market-structure": {
      "type": "http",
      "url": "https://api.zdte.ai/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.ai-zdte-market-structure]
url = "https://api.zdte.ai/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-zdte-market-structure": {
      "type": "remote",
      "url": "https://api.zdte.ai/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-zdte-market-structure --url 'https://api.zdte.ai/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ai-zdte-market-structure:
    url: "https://api.zdte.ai/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ai-zdte-market-structure": {
      "Transport": "http",
      "Url": "https://api.zdte.ai/mcp"
    }
  }
}
# add to Vellum
assistant mcp add ai-zdte-market-structure -t streamable-http -u 'https://api.zdte.ai/mcp'
// mcp.json
{
  "mcpServers": {
    "ai-zdte-market-structure": {
      "type": "http",
      "url": "https://api.zdte.ai/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 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
  • 24 Sept 26 +1

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

  • 22 Sept 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “list_history_dates” rewrote its description, which is the text the model reads security
    • Schema quality: 730 → 993 ▼ functional
    • New tool “create_credit_checkout” functional
    • New tool “create_guest_key” functional
    • New tool “get_access_options” functional
    • New tool “get_credit_balance” functional
  • 21 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 20 Sept 26 +1

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

  • 18 Sept 26 +1

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

  • 16 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_market_structure” rewrote its description, which is the text the model reads security
    • Tool “get_regime” rewrote its description, which is the text the model reads security
    • Schema quality: 70 → 77 ▼ 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 2 Oct 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 23 Aug 2026 21 Nov 2026 ECDSA 256 ECDSA-SHA384 5aaacee6374cf983327e403503721976315
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 insecure

Validation of api.zdte.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
zdte.ai. 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
strict-transport-security max-age=15552000
content-security-policy default-src 'self'; script-src 'self' https://web.squarecdn.com https://sandbox.web.squarecdn.com; 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 https://pci-connect.squareup.com https://pci-connect.squareupsandbox.com; frame-src https://web.squarecdn.com https://sandbox.web.squarecdn.com https://connect.squareup.com https://connect.squareupsandbox.com; 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 · ~739 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 ~82

Create a Stripe Checkout link for the authenticated key. Does not charge or fund until payment is authorized and confirmed. Return and check get_credit_balance.

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

No output schema declared.

No examples provided.

create_guest_key ~42

Create a zero-credit API key, returned once. Save it securely, configure HTTP Authorization: Bearer, and reconnect. Does not authenticate this connection. No arguments.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_access_options ~25

Free pricing and accountless access instructions. Start here; no website account required.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_credit_balance ~31

Free balance check for the API key in this connection's HTTP header. Never pass a key as an argument.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_day ~62

Per-day SPX market-structure timeline + summary for one replay date (YYYY-MM-DD). Data only -- not investment advice or a trade recommendation.

NameTypeReqDescription
datestringyesReplay date in YYYY-MM-DD; use list_history_dates for the set of valid dates.

No output schema declared.

No examples provided.

get_field_guide ~66

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_market_structure ~192

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. Realtime requires a funded X-API-Key (create one at https://zdte.ai/agent/credits); without a key this serves a delayed headline preview only (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 ~37

Current SPX dealer regime label + confidence only. Realtime with an X-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 ~50

Compressed dealer-regime segment tape for one replay date (YYYY-MM-DD).

NameTypeReqDescription
datestringyesReplay date in YYYY-MM-DD; use list_history_dates for the set of valid dates.

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 ~73

Subscribe a callback URL to a market-structure event (zero_gamma_flip | new_wall | regime_transition).

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 ~29

Remove an event subscription by id.

NameTypeReqDescription
subscription_idstringyesThe subscription id returned by subscribe_event.

No output schema declared.

No examples provided.

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. Free previews; 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 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 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 739 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 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.