io.zerogex/gamma-levels
Registry code: b9ce32f375a77e3e
ZeroGEX publishes modeled options dealer-positioning levels for SPX, SPY, QQQ, NDX, ES and NQ:
the gamma flip, call wall, put wall, max pain, pin strike and net dealer gamma at spot.
- endpoint
- https://zerogex.io/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is io.zerogex/gamma-levels live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
- Is io.zerogex/gamma-levels free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does io.zerogex/gamma-levels have?
- 2 tools: get_gamma_levels, get_market_gamma_overview.
- Is io.zerogex/gamma-levels safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.4%· all time 99.4%
last good check
of 2 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- unknown → live
- used for
- get options gamma levels for spx or qqq
- get dealer positioning overview
- takes → gives
- text → data
- tools
- 2 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_market_gamma_overview reads open 5h ago
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.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_gamma_levels reads unknown 5h ago
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 - at least 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.
{ "type": "object", "required": [ "symbol" ], "properties": { "symbol": { "enum": [ "SPY", "QQQ", "SPX", "NDX", "ES", "NQ" ], "type": "string", "description": "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." } }, "additionalProperties": false }arguments 21 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idb9ce32f375a77e3e.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/b9ce32f375a77e3e/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/b9ce32f375a77e3e?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.