Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

NegativeEV bet checker

REMOTE · NEGATIVEEV.COM · SCANNED SEP 22

Grade any MLB, WNBA, PGA or ATP bet against thousands of play-by-play sims. No key, no signup.

Available components

0 this week 81 Trust /100
Trust breakdown (7 categories)

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 Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 666 tokens (~222/item across 3 items; 3 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the NegativeEV bet checker MCP server?

NegativeEV bet checker is a hosted endpoint at https://negativeev.com/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 · negativeev.com

# add to Claude Code
claude mcp add --transport http com-negativeev-bet-checker 'https://negativeev.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-negativeev-bet-checker": {
      "url": "https://negativeev.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-negativeev-bet-checker": {
      "type": "http",
      "url": "https://negativeev.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-negativeev-bet-checker]
url = "https://negativeev.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-negativeev-bet-checker": {
      "type": "remote",
      "url": "https://negativeev.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-negativeev-bet-checker --url 'https://negativeev.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-negativeev-bet-checker:
    url: "https://negativeev.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-negativeev-bet-checker": {
      "Transport": "http",
      "Url": "https://negativeev.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-negativeev-bet-checker -t streamable-http -u 'https://negativeev.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-negativeev-bet-checker": {
      "type": "http",
      "url": "https://negativeev.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 29 Aug 26 0
    • Server version: 1.4.4 → 1.4.5 functional
  • 27 Aug 26 +2
    • HSTS header: fail → pass security
    • Tool “check_bet” rewrote its description, which is the text the model reads security
    • Tool “get_slate” rewrote its description, which is the text the model reads security
    • Tool “get_usage” rewrote its description, which is the text the model reads security
    • Schema quality: 262 → 222 functional
    • Server version: 1.4.3 → 1.4.4 functional
  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 16 Aug 26 0
    • Server version: 1.4.2 → 1.4.3 functional
  • 11 Aug 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
  • 5 Aug 26 0
    • HTTPS: unverified → pass security
  • 3 Aug 26 0
    • Server version: 1.4.1 → 1.4.2 functional
Diagnostics

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 22 Sept 2026 · Probed https://negativeev.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=negativeev.com CN=WE1,O=Google Trust Services,C=US 19 Sept 2026 18 Dec 2026 ECDSA 256 ECDSA-SHA256 c7f9f2d90eee85913480e620d5888e2
SANs: negativeev.com, marketing.negativeev.com, *.marketing.negativeev.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of negativeev.com. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
negativeev.com. present 2371 13 Verified
negativeev.com. Verified address RRset verified with the apex keys
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
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; base-uri 'self'; object-src 'none'; form-action 'self'; frame-ancestors 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://*.i.posthog.com https://challenges.cloudflare.com https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline'; font-src 'self' data:; img-src 'self' data: blob: https:; media-src 'self' https://media.negativeev.com; connect-src 'self' https://*.supabase.co https://*.i.posthog.com https://www.google-analytics.com https://*.google-analytics.com https://*.analytics.google.com https://media.negativeev.com https://cloudflareinsights.com; frame-src https://www.youtube-nocookie.com https://challenges.cloudflare.com; worker-src 'self' blob:
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://negativeev.com/mcp Verified 200
http (plaintext) http://negativeev.com/mcp HTTPS enforced 301 https://negativeev.com/mcp
MCP tools · 3 exposed · ~459 tokens

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 →

Tool Tokens
check_bet ~225

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, and ATP. A game that already started still checks, against the simulations from before it began.

NameTypeReqDescription
betstringyesThe bet text, e.g. 'Shohei Ohtani over 1.5 total bases -120'

No output schema declared.

No examples provided.

get_slate ~148

Which of MLB, WNBA, PGA, and ATP 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.

NameTypeReqDescription
sportstringOne of: MLB, WNBA, PGA, ATP. Omit to get every live sport.

No output schema declared.

No examples provided.

get_usage ~86

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the NegativeEV bet checker MCP server?

NegativeEV bet checker is an MCP server listed in the public MCP registry as com.negativeev/bet-checker. Grade any MLB, WNBA, PGA or ATP bet against thousands of play-by-play sims. No key, no signup. This page covers its hosted endpoint (https://negativeev.com/mcp).

Is the NegativeEV bet checker MCP server safe to use?

NegativeEV bet checker scores 81 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 NegativeEV bet checker MCP server expose?

NegativeEV bet checker exposes 3 tools: check_bet, get_slate, get_usage. Their descriptions and schemas cost roughly 459 tokens of context every time the server is loaded.

Does the NegativeEV bet checker MCP server require authentication?

No. We connected to NegativeEV bet checker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the NegativeEV bet checker MCP server still maintained?

NegativeEV bet checker is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.