_ registry / mcp streamable-http · checked 43m ago

gexlog

https://agent.gexlog.com

Registry code: 3021e36156e4a110

api record

GEXLOG read-only morning/evening market briefs. Cover conditions, events, risk, then GEX/walls/gamma from returned fields only. Never invent strikes. Never execute trades. Never call paid historical/range/regime endpoints. GEXLOG publishes options-derived dealer gamma estimates, not identical to proprietary GEX vendors. Educational market-structure context only — not personalized investment advice. Do not place trades from this plugin.

endpoint
https://agent.gexlog.com/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
10 · newcomer
_ is it live, free and safe measured by this hub
Is gexlog live?
Yes — it answered the hub's last check (checked 43m ago). It answered 100% of checks over the last 30 days.
Is gexlog free to use?
Yes — the hub reached it with no key and no payment.
What tools does gexlog have?
5 tools: get_gexlog_playbook, get_gexlog_gamma, list_gexlog_archive_dates, get_gexlog_snapshot, get_gexlog_site_map.
Is gexlog 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.
reachable
live
uptime, 30 days
99.7%

90 days 99.4%· all time 99.4%

latency
551ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 625 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
finance & markets stock & market data
used for
  • get a morning or evening market brief
  • get dealer gamma exposure levels
  • get a session playbook
  • list archived brief dates
takes → gives
text → data, text
tools
5 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address stands behind 2 doors on this origin, so the chain figures are the operator's. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
2

distinct

settlements
3

last 2026-11-08

received on chain
0.06 USDC

counted from three payers (thin, concentrated)

_ what it can do 5 tools
4 open 1 never probed 4 of 5 classified

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_gexlog_gamma reads open 3h ago

    Use this when the user asks specifically about net GEX, GEX flip, borderline regime, or the gamma histogram. Flip null is valid — do not invent a flip strike.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "report": {
      "enum": [
        "current",
        "morning",
        "evening",
        "weekend"
      ],
      "type": "string"
    },
    "profile_limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1
    },
    "include_profile": {
      "type": "boolean"
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • list_gexlog_archive_dates reads open 17h ago

    Use this when the user asks which GEXLOG briefing dates exist. Lists dates only. Historical JSON is a paid agent-API route and is not available in this plugin.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 40,
      "minimum": 1
    },
    "report_type": {
      "enum": [
        "morning",
        "evening",
        "weekend"
      ],
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • get_gexlog_snapshot reads open 3h ago

    Use this when the user wants the GEXLOG morning or evening market brief: session conditions, calendar events/catalysts, risk, playbook, plus GEX walls and gamma. current/morning = AM brief; evening = PM brief; weekend = week-ahead. Do not use for historical dates, paid archives, brokerage accounts, or placing trades.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "report": {
      "enum": [
        "current",
        "morning",
        "evening",
        "weekend"
      ],
      "type": "string",
      "description": "current/morning = AM market brief; evening = PM brief; weekend = week-ahead preview."
    },
    "profile_limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1
    },
    "include_profile": {
      "type": "boolean",
      "description": "If true, attach largest-magnitude GEX histogram rows (capped)."
    }
  },
  "additionalProperties": false
}
    arguments 25 lines
  • get_gexlog_site_map reads open 3h ago

    Use this when the user asks how to use gexlog.com, where methodology lives, or which pages to open. Do not scrape HTML. Agent SKILL.md files (use-gexlog-site, gather-gexlog-data, interpret-gexlog) are at https://gexlog.com/skills/

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_gexlog_playbook reads unknown never probed

    Use this when the user asks for GEXLOG's published session playbook, guidance, or look-ahead. Quote it as GEXLOG's published briefing, not as a trade recommendation. Do not execute trades.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "report": {
      "enum": [
        "current",
        "morning",
        "evening",
        "weekend"
      ],
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 3021e36156e4a110.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3021e36156e4a110/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/3021e36156e4a110/badge.svg)](https://brick.blue/agent/3021e36156e4a110?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.

_ how we know
card completeness
90%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.