ZeroGEX — SPX/SPY/QQQ/NDX dealer positioning
REMOTE · ZEROGEX.IO · SCANNED SEP 25
Free delayed gamma flip, call and put walls, max pain and net dealer gamma
Available components
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 545 tokens (~272/item across 2 items; 2 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 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
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
How do I install the ZeroGEX — SPX/SPY/QQQ/NDX dealer positioning MCP server?
ZeroGEX — SPX/SPY/QQQ/NDX dealer positioning is a hosted endpoint at https://zerogex.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 · zerogex.io
claude mcp add --transport http io-zerogex-gamma-levels 'https://zerogex.io/mcp'
{
"mcpServers": {
"io-zerogex-gamma-levels": {
"url": "https://zerogex.io/mcp"
}
}
} {
"servers": {
"io-zerogex-gamma-levels": {
"type": "http",
"url": "https://zerogex.io/mcp"
}
}
} [mcp_servers.io-zerogex-gamma-levels] url = "https://zerogex.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-zerogex-gamma-levels": {
"type": "remote",
"url": "https://zerogex.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-zerogex-gamma-levels --url 'https://zerogex.io/mcp' --transport streamable-http
mcp_servers:
io-zerogex-gamma-levels:
url: "https://zerogex.io/mcp" {
"McpServers": {
"io-zerogex-gamma-levels": {
"Transport": "http",
"Url": "https://zerogex.io/mcp"
}
}
} assistant mcp add io-zerogex-gamma-levels -t streamable-http -u 'https://zerogex.io/mcp'
{
"mcpServers": {
"io-zerogex-gamma-levels": {
"type": "http",
"url": "https://zerogex.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 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 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 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.
- 20 Sept 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.
- 18 Sept 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.
- 16 Sept 26 +7
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- 15 Sept 26 −6
- HSTS header: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- 14 Sept 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.
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 25 Sept 2026 · Probed https://zerogex.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zerogex.io | CN=YE1,O=Let's Encrypt,C=US | 12 Sept 2026 | 11 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 553cedebe7ff8c7035cb0ac76195bcc0e77 |
| SANs: *.zerogex.io, zerogex.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 zerogex.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| zerogex.io. | 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 |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://zerogex.io/mcp | Verified | 200 | |
| http (plaintext) | http://zerogex.io/mcp | HTTPS enforced | 301 | https://zerogex.io/mcp |
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 →
get_gamma_levels Get delayed gamma levels ~195
Modeled options dealer-positioning levels for one underlying: gamma flip, call wall, put wall, max pain, same-day pin strike, and net dealer gamma at spot (whose sign is the regime). Use for "where is the gamma flip", "where are the walls", "is SPX in positive gamma". FREE DELAYED DATA - up to 15 minutes behind live, and the response states its own age; quote that age and never call these levels live. Not a price feed, not a forecast, and not a trade recommendation: it describes dealer positioning and says nothing on its own about direction. A null level means the modeled book does not support that level right now - report it as unavailable, never as zero.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | ES and NQ have no options book of their own; their levels are the SPX and NDX option-derived levels already projected onto the futures price axis. |
No output schema declared.
No examples provided.
get_market_gamma_overview Get delayed gamma levels for every symbol ~131
One-line dealer-positioning summary for all six covered underlyings (SPX, SPY, QQQ, NDX, ES, NQ) in a single call: spot, modeled regime and gamma flip for each. Use for broad openers like "what does dealer positioning look like today" or "which indices are in negative gamma", instead of calling get_gamma_levels six times. Same free 15-minute-delayed data and the same caveats. When the question is about one symbol, call get_gamma_levels instead - this tool omits the walls, max pain and pin strike.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the ZeroGEX — SPX/SPY/QQQ/NDX dealer positioning MCP server?
ZeroGEX — SPX/SPY/QQQ/NDX dealer positioning is an MCP server listed in the public MCP registry as io.zerogex/gamma-levels. Free delayed gamma flip, call and put walls, max pain and net dealer gamma. This page covers its hosted endpoint (https://zerogex.io/mcp).
Is the ZeroGEX — SPX/SPY/QQQ/NDX dealer positioning MCP server safe to use?
ZeroGEX — SPX/SPY/QQQ/NDX dealer positioning scores 77 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 ZeroGEX — SPX/SPY/QQQ/NDX dealer positioning MCP server expose?
ZeroGEX — SPX/SPY/QQQ/NDX dealer positioning exposes 2 tools: get_gamma_levels, get_market_gamma_overview. Their descriptions and schemas cost roughly 326 tokens of context every time the server is loaded.
Does the ZeroGEX — SPX/SPY/QQQ/NDX dealer positioning MCP server require authentication?
No. We connected to ZeroGEX — SPX/SPY/QQQ/NDX dealer positioning without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ZeroGEX — SPX/SPY/QQQ/NDX dealer positioning MCP server still maintained?
ZeroGEX — SPX/SPY/QQQ/NDX dealer positioning is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.