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.

0to100

REMOTE · MCP.0TO100.XYZ · SCANNED SEP 20

Schedules, injury reports and fan-hub links for all 32 NFL and 30 NBA teams.

Available components

+3 this week 76 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 Security74
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 435 tokens (~54/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 67% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the 0to100 MCP server?

0to100 is a hosted endpoint at https://mcp.0to100.xyz/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 · mcp.0to100.xyz

# add to Claude Code
claude mcp add --transport http xyz-0to100-mcp-sports 'https://mcp.0to100.xyz/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "xyz-0to100-mcp-sports": {
      "url": "https://mcp.0to100.xyz/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "xyz-0to100-mcp-sports": {
      "type": "http",
      "url": "https://mcp.0to100.xyz/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.xyz-0to100-mcp-sports]
url = "https://mcp.0to100.xyz/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-0to100-mcp-sports": {
      "type": "remote",
      "url": "https://mcp.0to100.xyz/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add xyz-0to100-mcp-sports --url 'https://mcp.0to100.xyz/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  xyz-0to100-mcp-sports:
    url: "https://mcp.0to100.xyz/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "xyz-0to100-mcp-sports": {
      "Transport": "http",
      "Url": "https://mcp.0to100.xyz/mcp"
    }
  }
}
# add to Vellum
assistant mcp add xyz-0to100-mcp-sports -t streamable-http -u 'https://mcp.0to100.xyz/mcp'
// mcp.json
{
  "mcpServers": {
    "xyz-0to100-mcp-sports": {
      "type": "http",
      "url": "https://mcp.0to100.xyz/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.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +3
    • The server changed its declared name: 0to100 → 0to100-mcp security
    • Schema quality: 43 → 54 functional
    • Tool coverage: 43% → 67% functional
    • MCP protocol: fail → pass functional
    • MCP protocol version: 2025-06-18 → 2025-11-25 functional
    • New tool “get_consensus_board” functional
    • New tool “get_tips” functional
  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Sept 26 +1
    • Stability: unverified → 0.03 functional
  • 6 Sept 26 67

    First indexed and scored.

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 20 Sept 2026 · Probed https://mcp.0to100.xyz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.0to100.xyz CN=WE1,O=Google Trust Services,C=US 5 Sept 2026 4 Dec 2026 ECDSA 256 ECDSA-SHA256 86d9b63f0c887e140e48ffb8af070ee8
SANs: mcp.0to100.xyz
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 insecure

Validation of mcp.0to100.xyz. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
xyz. present 3599, 18130 8, 8 Verified
0to100.xyz. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.0to100.xyz/mcp Verified 200
http (plaintext) http://mcp.0to100.xyz/mcp HTTPS enforced 301 https://mcp.0to100.xyz/mcp
MCP tools · 8 exposed · ~435 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
get_consensus_board ~86

Podcast-consensus futures boards (e.g. Super Bowl winner): ranked teams with consensus probabilities, lean direction, and episode-level provenance (show, quote, timestamp).

NameTypeReqDescription
boardstringBoard name, e.g. 'Super Bowl LXI' or 'sb-lxi'
include_provenancebooleanInclude per-entry show/quote/timestamp provenance

No output schema declared.

No examples provided.

get_injury_report ~24

Current injury report for a team.

NameTypeReqDescription
teamstringyes

No output schema declared.

No examples provided.

get_live_odds ~49

Live betting markets for a team's next game: moneyline, spread, total with $1-payout math (NFL live now; NBA opens with the season).

NameTypeReqDescription
teamstringyes

No output schema declared.

No examples provided.

get_player_stats ~64

Season stats for one player on a team (points/assists/rebounds for NBA, passing/rushing/etc for NFL).

NameTypeReqDescription
playerstringyesPlayer name, e.g. 'Jalen Brunson' or 'Mahomes'
teamstringyes

No output schema declared.

No examples provided.

get_roster ~26

Full roster grouped by position, with jersey numbers.

NameTypeReqDescription
teamstringyes

No output schema declared.

No examples provided.

get_team_schedule ~55

Upcoming games for a team (dates, opponent, venue).

NameTypeReqDescription
teamstringyesTeam name, nickname, slug, or abbreviation - e.g. 'Chiefs', 'newyorkknicks', 'NYK'

No output schema declared.

No examples provided.

get_tips ~89

Latest 0to100 betting tips from the podcast-inference pipeline: pick, probability, lean, line context. Filter by team or tip type.

NameTypeReqDescription
limitnumberMax rows (default 10)
teamstringTeam filter, e.g. 'Giants'
tip_typestringe.g. 'single-game sample' or 'consensus board'

No output schema declared.

No examples provided.

list_teams ~42

List all 62 pro teams 0to100 covers (32 NFL + 30 NBA) with hub URLs.

NameTypeReqDescription
sportstringOptional league filter

No output schema declared.

No examples provided.

Common questions

What is the 0to100 MCP server?

0to100 is an MCP server listed in the public MCP registry as xyz.0to100.mcp/sports. Schedules, injury reports and fan-hub links for all 32 NFL and 30 NBA teams. This page covers its hosted endpoint (https://mcp.0to100.xyz/mcp).

Is the 0to100 MCP server safe to use?

0to100 scores 76 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 0to100 MCP server expose?

0to100 exposes 8 tools: list_teams, get_team_schedule, get_injury_report, get_roster, get_player_stats, and 3 more. Their descriptions and schemas cost roughly 435 tokens of context every time the server is loaded.

Does the 0to100 MCP server require authentication?

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

Is the 0to100 MCP server still maintained?

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