# Fill My Bracket (remote · mcp.fillmybracket.com)

March Madness bracket help: picks, matchup analysis, and upset guidance for your pool.

- Trust score: 71/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.fillmybracket.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-fillmybracket-fill-my-bracket/mcp.md), [page](https://verifymcp.io/servers/com-fillmybracket-fill-my-bracket/mcp)

## Channel facts

- Endpoint: `https://mcp.fillmybracket.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1441 tokens (~360/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Fill My Bracket MCP server?

Fill My Bracket is a hosted endpoint at https://mcp.fillmybracket.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.

### Claude

```bash
claude mcp add --transport http com-fillmybracket-fill-my-bracket 'https://mcp.fillmybracket.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-fillmybracket-fill-my-bracket": {
      "url": "https://mcp.fillmybracket.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-fillmybracket-fill-my-bracket": {
      "type": "http",
      "url": "https://mcp.fillmybracket.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-fillmybracket-fill-my-bracket]
url = "https://mcp.fillmybracket.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-fillmybracket-fill-my-bracket": {
      "type": "remote",
      "url": "https://mcp.fillmybracket.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-fillmybracket-fill-my-bracket --url 'https://mcp.fillmybracket.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-fillmybracket-fill-my-bracket:
    url: "https://mcp.fillmybracket.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-fillmybracket-fill-my-bracket": {
      "Transport": "http",
      "Url": "https://mcp.fillmybracket.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-fillmybracket-fill-my-bracket -t streamable-http -u 'https://mcp.fillmybracket.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-fillmybracket-fill-my-bracket": {
      "type": "http",
      "url": "https://mcp.fillmybracket.com/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 71, +1)

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

### 2026-11-19 (score 70, +1)

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

### 2026-11-17 (score 69, +1)

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

### 2026-11-15 (score 68, +1)

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

### 2026-11-13 (score 67, +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.

### 2026-11-11 (score 66, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_backtest” rewrote its description, which is the text the model reads
- [security] Tool “get_cinderella_radar” rewrote its description, which is the text the model reads
- [security] Tool “get_rankings” rewrote its description, which is the text the model reads
- [security] Tool “get_upset_counts” rewrote its description, which is the text the model reads
- [cosmetic] “get_backtest” reworded the description of “year”

### 2026-11-10 (score 66, +1)

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

### 2026-11-08 (score 65, +1)

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

## MCP tools (4)

### `get_rankings` (~278 tokens)

Get current rankings

Returns the current college basketball rankings exactly as published on fillmybracket.com/college-basketball-rankings: the AP Top 25, Week 1 (released Monday, November 9, 2026, with first-place votes), the other teams receiving votes, and the Bart Torvik T-Rank model ranks (read November 1, 2026). Rankings as of Monday, November 9, 2026, and every result says so. With no argument, returns the full Top 25 plus the model's own top 10, so the poll-vs-model gaps are visible. With a team name, returns that team's AP rank or votes, its model rank, and any radar or vulnerable-favorite note the site carries for it. A team outside the published data gets a plain not-found: nothing is invented. Real teams and real ranks only; this is current-season data, not the 2027 tournament field, which is set on Selection Sunday, March 14, 2027.

Input parameters:

- `limit` (number): Optional: how many of the Top 25 to return, 1 to 25. Default 25.
- `team` (string): Optional: one team name, e.g. 'Duke' or 'Grand Canyon'. Omit for the full Top 25 table.

### `get_cinderella_radar` (~164 tokens)

Get the Cinderella radar

Returns Fill My Bracket's Cinderella radar, as of Monday, November 9, 2026, exactly as published on the site's rankings page: the unranked teams the model rates far above their poll votes (each with its league, AP votes, model rank, and a plain why line), the Cinderella watch list, and the ranked teams flagged as vulnerable favorites on their projected seed lines, each with that line's counted first-round record from 1985-2026. These are November signals from the Week 1 poll and one model, stated as the site states them: not predictions, not odds, and no guarantee any of these teams makes the 2027 field, which is set on Selection Sunday, March 14, 2027.

### `get_upset_counts` (~189 tokens)

Get counted upset history

Answers upset questions from the men's tournament counted game by game, 1985-2026 (41 tournaments, 2,583 games): how often a seed line wins its first-round game (stated as wins in 164 games), how many first-round upsets a typical year has, and how far a seed has gone. Ask with a matchup ('12 vs 5'), a seed, or no argument for the whole table. These are counted historical facts, not odds, not win probabilities for any future game, and not betting advice. The dataset is men's only and covers the main bracket from the round of 64 (no First Four games).

Input parameters:

- `matchup` (string): A first-round seed pairing, e.g. '12 vs 5'. Optional.
- `seed` (number): One seed, 1 to 16: returns its first-round seed line. Optional.

### `get_backtest` (~329 tokens)

Get backtested winning recipes

For a past men's tournament (2016-2026; no tournament was played in 2020), returns the winning recipes: the site's own five-question engine was run over that year's REAL field (real teams, real seeds) across 108 answer combinations, and every bracket was scored against what actually happened under standard pool scoring (1-2-4-8-16-32, max 192). With no style inputs, returns the year's real champion and Final Four, the best total score and the recipe that earned it, the best first-weekend score, how many recipes ended with the real champion, and how many reproduced the full Final Four (in most years, none did). With style inputs (chaos, tiebreak, champion_pick, loyalty), scores that exact recipe instead. Counted history, not a prediction: a recipe is what WOULD have scored in a finished tournament, and the result says so. No odds, no betting advice.

Input parameters:

- `champion_pick` (string): Optional recipe input: one of that year's real Final Four teams, or 'none'.
- `chaos` (string): Optional recipe input: 'chalk', 'some', 'lots', or 'chaos'.
- `loyalty` (string): Optional recipe input: 'none' or 'home' (root for the champion pick as your home team).
- `tiebreak` (string): Optional recipe input: 'mascot', 'colors', or 'familiar'.
- `year` (number): Tournament year, 2016-2026 (no 2020). Default 2025.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-fillmybracket-fill-my-bracket/mcp#diagnostics

## Score history

- 2026-11-21: 71
- 2026-11-20: 70
- 2026-11-19: 70
- 2026-11-18: 69
- 2026-11-17: 69
- 2026-11-16: 68
- 2026-11-15: 68
- 2026-11-14: 67
- 2026-11-13: 67
- 2026-11-12: 66
- 2026-11-11: 66
- 2026-11-10: 66
- 2026-11-09: 65
- 2026-11-08: 65
- 2026-11-07: 64
- 2026-11-06: 64
- 2026-11-05: 63

## Common questions

### What is the Fill My Bracket MCP server?

Fill My Bracket is an MCP server listed in the public MCP registry as com.fillmybracket/fill-my-bracket. March Madness bracket help: picks, matchup analysis, and upset guidance for your pool. This page covers its hosted endpoint (https://mcp.fillmybracket.com/mcp).

### Is the Fill My Bracket MCP server safe to use?

Fill My Bracket scores 71 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 Fill My Bracket MCP server expose?

Fill My Bracket exposes 4 tools: get_rankings, get_cinderella_radar, get_upset_counts, get_backtest. Their descriptions and schemas cost roughly 960 tokens of context every time the server is loaded.

### Does the Fill My Bracket MCP server require authentication?

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

### Is the Fill My Bracket MCP server still maintained?

Fill My Bracket is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Fill My Bracket MCP server?

VerifyMCP ran 12 checks on Fill My Bracket, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Fill My Bracket: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.fillmybracket.com/mcp
- Repository: https://github.com/wdlcmu/fill-my-bracket
- Website: https://fillmybracket.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-fillmybracket-fill-my-bracket/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-fillmybracket-fill-my-bracket/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-fillmybracket-fill-my-bracket/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-fillmybracket-fill-my-bracket/mcp
