_ registry / mcp streamable-http · checked 1h ago

maddog

https://api.maddog.finance

Registry code: ebaefc9986926182

api record

MADDOG reads market sessions the way a price action trader does, with measured statistics instead of opinions: a five-class day-type distribution (66% top-1 over a complete US day session vs a 37% baseline), the window's first range breakout with a calibrated failure estimate (AUC 0.646, held-out NQ), and the measured odds that a new session high or low still prints after the 90-minute mark. The close_curve tool adds the full probability curve of where the session closes at any price level — validated on tail levels against real-money prediction-market prices (use it for shape and tails; near…

endpoint
https://api.maddog.finance/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 it live, free and safe measured by this hub
Is maddog live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is maddog free to use?
Yes — the hub reached it with no key and no payment.
What tools does maddog have?
4 tools: request_free_key, close_curve, price_action_read, get_scoreboard.
Is maddog 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
100%

90 days 100%· all time 100%

latency
888ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 297 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
used for
  • read intraday price action statistics for an instrument
  • get session close probability curve
  • get public call scoreboard
  • request a free evaluation key
takes → gives
data → data
tools
3 reads1 changes data
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 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_scoreboard reads open 23h ago

    The standing public record of this service's own calls — free, no key. Every US trading day at 11:00 ET the day-session read for ES=F, NQ=F and QQQ is snapshotted verbatim; after the close each row is scored on whether a new session high or low actually printed after the read. Ties score against the model, days with no live read stay visible as gaps, and no row is ever edited. Recording began 2026-08-25. Use this to verify the claims before trusting any read.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 250,
          "minimum": 1,
          "description": "Rows to return, newest first. Default 30."
        }
      }
    }
    arguments 11 lines
  • request_free_key changes data unknown never probed

    Request a free evaluation key (qd_...): no card, no account — the key is emailed to the address given, never returned in this response. It unlocks 10 successful calls per UTC day. Ask the human for their email address first and send marketing_opt_in=true only with their explicit consent. Full access is $99.90/month with a 3-day free trial, checkout link comes back in any quota-exhausted error.

    mcp-tool

    {
      "type": "object",
      "required": [
        "email"
      ],
      "properties": {
        "email": {
          "type": "string",
          "description": "Where the key is delivered."
        },
        "source": {
          "type": "string",
          "description": "Optional short origin tag, e.g. 'agent'."
        },
        "marketing_opt_in": {
          "type": "boolean",
          "description": "Only with explicit user consent."
        }
      }
    }
    arguments 20 lines
  • close_curve reads unknown never probed

    The full probability curve of where today's US regular session closes: for any set of price levels, the probability that the session close prints above each one. Distances are measured in units of today's own volatility (ATR of the first 90 minutes) against 1,906 historical sessions grouped by day type. Validated against real-money prediction-market prices: on tail levels (>=0.5% from spot) this curve's log-loss beat Polymarket's own 'SPY closes above $K' ladder quotes in two independent windows; near the money the market was MORE accurate — use this for shape and tails, not direction. Available from 90 minutes into the day session. Same key and quota as price_action_read. Historical frequencies, not forecasts.

    mcp-tool

    {
      "type": "object",
      "required": [
        "symbol"
      ],
      "properties": {
        "levels": {
          "type": "array",
          "items": {
            "type": "number"
          },
          "maxItems": 40,
          "description": "Price levels to evaluate. Omit for an automatic grid at ±0.25/0.5/1/1.5/2/3 ATR18 around the anchor."
        },
        "symbol": {
          "type": "string",
          "description": "Ticker: NVDA, SPY, ES=F, EURUSD, BTC-USD, 0700.HK. Index names like SPX do not resolve — use SPY or ES=F. Built and measured on ES; other symbols are descriptive."
        }
      }
    }
    arguments 20 lines
  • price_action_read reads unknown 23h ago

    Read one instrument's current session the way a price action trader would, with measured statistics instead of opinions: a five-class day-type probability distribution (66% top-1 accuracy over a complete US day session against a 37% baseline, published confidence grades from 95% to 41% by grade), the window's first range breakout with its calibrated failure estimate (AUC 0.646 on held-out NQ), and — 90 minutes into the session — the measured odds that a new session high or low still prints before the close. Works on US stocks and ETFs, futures (ES=F), FX, crypto, Hong Kong and China A-shares. Anonymous callers get one first-look response per UTC day; after that, pass an API key in the X-API-Key header (get a free one with the request_free_key tool). Historical frequencies, not forecasts.

    mcp-tool

    {
      "type": "object",
      "required": [
        "symbol"
      ],
      "properties": {
        "symbol": {
          "type": "string",
          "description": "Ticker: NVDA, SPY, ES=F, EURUSD, BTC-USD, 0700.HK, 600519. Index names like SPX do not resolve — use SPY or ES=F."
        },
        "window": {
          "enum": [
            "rth",
            "gap",
            "asia"
          ],
          "type": "string",
          "description": "Omit to follow the freshest bars. rth = US day session; asia = 09:00-16:00 Beijing; gap = the Asia-close-to-US-open stretch. gap/asia are for 24-hour instruments only."
        }
      }
    }
    arguments 21 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 ebaefc9986926182.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ebaefc9986926182/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/ebaefc9986926182/badge.svg)](https://brick.blue/agent/ebaefc9986926182?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
80%

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.