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

negativeev-bet-checker

https://negativeev.com

Registry code: d07c14cdc0d547ec

api record

Grade MLB, WNBA, PGA, ATP, and NFL bets against NegativeEV's thousands of play-by-play game simulations. Call get_slate first to confirm there's a checkable slate; check_bet spends one of the caller's checks only when the bet fully grades, and every check_bet result says so outright (`status`, `check_spent`), so read those rather than inferring from the numbers. A bet that came back `ungraded` was understood — it is simply not on the simulated slate, so re-sending it with different wording returns the same answer; check get_slate instead. get_usage shows what's left. Anonymous calls share a…

endpoint
https://negativeev.com/mcp
door code
118a56d1cb8aff4a
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 negativeev-bet-checker live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is negativeev-bet-checker free to use?
Yes — the hub reached it with no key and no payment.
What tools does negativeev-bet-checker have?
3 tools: check_bet, get_slate, get_usage.
Is negativeev-bet-checker 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.8%· all time 99.6%

latency
373ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 927 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • grade a sports bet against game simulations
  • check which sports have a checkable slate
  • check remaining bet checks
takes → gives
text → data
tools
3 reads
_ 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 3 tools
2 open 1 never probed 2 of 3 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_slate reads open 19h ago

    Which of MLB, WNBA, PGA, ATP, and NFL have a checkable slate right now - at least one simulated game that has not started. Pass `sport` for one; omit it for all. Free, spends no check. It is not required before `check_bet`, which reports a missing slate itself at no cost. Call it to answer "what can be checked today", or after a `no_slate` or `ungraded` result, which mean the game is not on the simulated slate rather than that the bet was worded wrong.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "sport": {
          "enum": [
            "MLB",
            "WNBA",
            "PGA",
            "ATP",
            "NFL"
          ],
          "type": "string",
          "description": "One of: MLB, WNBA, PGA, ATP, NFL. Omit to get every live sport."
        }
      }
    }
    arguments 17 lines
  • get_usage reads open 19h ago

    How many bet checks the caller has left and when the next one frees up - 100 a day shared per device anonymously, 1000 an hour with a signed-in user's token. Free, spends no check. It grades nothing, so it is not a step before a check: call it when a check comes back refused for quota, or before working through a long list of bets.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • check_bet reads unknown 19h ago

    Check a specific sports bet against thousands of play-by-play game simulations: each leg's simulated probability, the sportsbook's implied probability, and the edge. Send the bet as plain text - teams or players, market, line, odds. A parlay in one string is graded leg by leg and priced as a whole. Call this first; nothing has to be set up, and a missing slate, an unrecognized bet, or an unsupported market comes back as a plain `status` without spending a check. It prices a bet the caller names and never suggests one, so there is nothing to send for "what should I bet tonight". Every result leads with `status` and `check_spent` and says whether re-wording would change anything; when it says no, it means no. Covers MLB, WNBA, PGA, ATP, and NFL. A game that already started still checks, against the simulations from before it began.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "bet"
      ],
      "properties": {
        "bet": {
          "type": "string",
          "description": "The bet text, e.g. 'Shohei Ohtani over 1.5 total bases -120'"
        }
      }
    }
    arguments 13 lines
_ try it over mcp 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 d07c14cdc0d547ec.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d07c14cdc0d547ec/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/d07c14cdc0d547ec/badge.svg)](https://brick.blue/agent/d07c14cdc0d547ec?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 knowoff the mcp door
card completeness
70%

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.