# BetSlip Doctor (remote · api.betslipdoctor.ai)

Read, grade, and track a subscriber's betslips with preserved truth and no wager placement.

- Trust score: 92/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `api.betslipdoctor.ai`: 92/100 (this document), [markdown](https://verifymcp.io/servers/ai-betslipdoctor-mcp/api-mcp.md), [page](https://verifymcp.io/servers/ai-betslipdoctor-mcp/api-mcp)

## Channel facts

- Endpoint: `https://api.betslipdoctor.ai/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## 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-09-20.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 762 tokens (~108/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 94% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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 BetSlip Doctor MCP server?

BetSlip Doctor is a hosted endpoint at https://api.betslipdoctor.ai/api/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 ai-betslipdoctor-mcp 'https://api.betslipdoctor.ai/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-betslipdoctor-mcp": {
      "url": "https://api.betslipdoctor.ai/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-betslipdoctor-mcp": {
      "type": "http",
      "url": "https://api.betslipdoctor.ai/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-betslipdoctor-mcp]
url = "https://api.betslipdoctor.ai/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-betslipdoctor-mcp": {
      "type": "remote",
      "url": "https://api.betslipdoctor.ai/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-betslipdoctor-mcp --url 'https://api.betslipdoctor.ai/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-betslipdoctor-mcp:
    url: "https://api.betslipdoctor.ai/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-betslipdoctor-mcp": {
      "Transport": "http",
      "Url": "https://api.betslipdoctor.ai/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-betslipdoctor-mcp -t streamable-http -u 'https://api.betslipdoctor.ai/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-betslipdoctor-mcp": {
      "type": "http",
      "url": "https://api.betslipdoctor.ai/api/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-09-18 (score 92, +1)

- [security] Stability: 0.97 → pass

### 2026-09-16 (score 91, +1)

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

### 2026-09-13 (score 90, +1)

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

### 2026-09-11 (score 89, +1)

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

### 2026-09-09 (score 88, +1)

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

### 2026-09-07 (score 87, +1)

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

### 2026-09-05 (score 86, +1)

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

### 2026-09-03 (score 85, +1)

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

## MCP tools (7)

### `get_tracked_slips` (~47 tokens)

Tracked slips

Read the authenticated user's tracked ticket trees and tracking lifecycle. Provider placement ids and sportsbook deep links are never returned.

Input parameters:

- `limit` (integer): Tickets to return (default 20).

### `track_slip` (~114 tokens)

Track a slip

Create or revise one of the authenticated user's ticket trees. This stores truth state only; it never places, prepares, or hands off a wager.

Input parameters:

- `client_mutation_id` (string, required): Caller-generated idempotency key.
- `expected_revision` (integer): Required with ticket_id; stale writes fail with a conflict.
- `ticket` (object, required): BSD two-level BetTicketContract. SGP children stay nested under one outer pick.
- `ticket_id` (string): Server ticket id when revising an existing tracked slip.

### `get_todays_board` (~122 tokens)

Today's board (live odds)

Live sports board: upcoming and in-play games with main-market prices (moneyline, spread, total) and the best posted price per selection across connected books. Read-only decision support; never a guarantee and never a wager.

Input parameters:

- `leagues` (array): League labels to filter by, e.g. ['MLB','NFL']. Omit for all leagues.
- `limit` (integer): Games to return (default 20, max 50). Live plus soonest first.
- `offset` (integer): Window offset for paging (default 0).

### `grade_slip` (~150 tokens)

Grade a betslip

Submit betslip text and get BetSlip Doctor's graded second opinion: rank, score, per-leg calls, ten-dimension checkup and sourced evidence. Entertainment/decision support only. Uses the user's plan allowance exactly like grading in the app.

Input parameters:

- `mode` (string): Research depth. 'fast' (default) answers quickly; 'deep' fans out to every research provider.
- `slipText` (string): The betslip as pasted text: one leg per line with odds where known.
- `stake` (number): Optional stake in dollars for payout context.
- `ticket` (object): Optional BSD two-level BetTicketContract. Use this for screenshot/manual parses and SGP trees.

### `get_saved_reports` (~70 tokens)

Saved reports

List the authenticated user's saved diagnosis reports (newest first), or fetch one full report by id. Only ever the calling user's own reports.

Input parameters:

- `limit` (integer): Compact list size (default 10).
- `report_id` (string): Return this one report in full instead of the compact list.

### `get_history_summary` (~74 tokens)

Betting history summary

The authenticated user's imported betting-history ledger: W-L record, stake and net over lifetime/30d/7d windows, sync freshness, and their most recent bets. Numbers come only from the user's own imported slips; nothing is fabricated.

Input parameters:

- `recent` (integer): How many recent bets to include (default 5).

### `price_shop_slip` (~72 tokens)

Price-shop a slip

Compare posted prices across books for each leg of a slip (main markets). Reports every book's quote, the best price for the bettor, and how much the user's own line gives up. Only ever describes books with real posted data; read-only, never places a wager.

Input parameters:

- `legs` (array, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-betslipdoctor-mcp/api-mcp#diagnostics

## Score history

- 2026-09-20: 92
- 2026-09-19: 92
- 2026-09-18: 92
- 2026-09-17: 91
- 2026-09-16: 91
- 2026-09-15: 90
- 2026-09-14: 90
- 2026-09-13: 90
- 2026-09-12: 89
- 2026-09-11: 89
- 2026-09-10: 88
- 2026-09-09: 88
- 2026-09-08: 87
- 2026-09-07: 87
- 2026-09-06: 86
- 2026-09-05: 86
- 2026-09-04: 85
- 2026-09-03: 85
- 2026-09-02: 84
- 2026-09-01: 84
- 2026-08-31: 83
- 2026-08-30: 83
- 2026-08-29: 83
- 2026-08-28: 82
- 2026-08-27: 82
- 2026-08-26: 81
- 2026-08-25: 79
- 2026-08-24: 79
- 2026-08-23: 78
- 2026-08-22: 78

## Common questions

### What is the BetSlip Doctor MCP server?

BetSlip Doctor is an MCP server listed in the public MCP registry as ai.betslipdoctor/mcp. Read, grade, and track a subscriber's betslips with preserved truth and no wager placement. This page covers its hosted endpoint (https://api.betslipdoctor.ai/api/mcp).

### Is the BetSlip Doctor MCP server safe to use?

BetSlip Doctor scores 92 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 BetSlip Doctor MCP server expose?

BetSlip Doctor exposes 7 tools: get_tracked_slips, track_slip, get_todays_board, grade_slip, get_saved_reports, and 2 more. Their descriptions and schemas cost roughly 649 tokens of context every time the server is loaded.

### Does the BetSlip Doctor MCP server require authentication?

Yes. BetSlip Doctor asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the BetSlip Doctor MCP server still maintained?

BetSlip Doctor 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.

## Links

- Remote endpoint: https://api.betslipdoctor.ai/api/mcp
- Repository: https://github.com/opspot-ai/betslipdoctor
- Changelog RSS feed: https://verifymcp.io/servers/ai-betslipdoctor-mcp/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-betslipdoctor-mcp/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-betslipdoctor-mcp/api-mcp