BetSlip Doctor
REMOTE · API.BETSLIPDOCTOR.AI · SCANNED SEP 20
Read, grade, and track a subscriber's betslips with preserved truth and no wager placement.
Available components
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 762 tokens (~108/item across 7 items; 7 tools + 0 resources), lean.Pass
- 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 Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% 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 7 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · api.betslipdoctor.ai
claude mcp add --transport http ai-betslipdoctor-mcp 'https://api.betslipdoctor.ai/api/mcp'
{
"mcpServers": {
"ai-betslipdoctor-mcp": {
"url": "https://api.betslipdoctor.ai/api/mcp"
}
}
} {
"servers": {
"ai-betslipdoctor-mcp": {
"type": "http",
"url": "https://api.betslipdoctor.ai/api/mcp"
}
}
} [mcp_servers.ai-betslipdoctor-mcp] url = "https://api.betslipdoctor.ai/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-betslipdoctor-mcp": {
"type": "remote",
"url": "https://api.betslipdoctor.ai/api/mcp",
"enabled": true
}
}
} openclaw mcp add ai-betslipdoctor-mcp --url 'https://api.betslipdoctor.ai/api/mcp' --transport streamable-http
mcp_servers:
ai-betslipdoctor-mcp:
url: "https://api.betslipdoctor.ai/api/mcp" {
"McpServers": {
"ai-betslipdoctor-mcp": {
"Transport": "http",
"Url": "https://api.betslipdoctor.ai/api/mcp"
}
}
} assistant mcp add ai-betslipdoctor-mcp -t streamable-http -u 'https://api.betslipdoctor.ai/api/mcp'
{
"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.
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.
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 9 Sept 26 +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.
- 7 Sept 26 +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.
- 5 Sept 26 +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.
- 3 Sept 26 +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.
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://api.betslipdoctor.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.betslipdoctor.ai | CN=YR1,O=Let's Encrypt,C=US | 17 Aug 2026 | 15 Nov 2026 | RSA 2048 | SHA256-RSA | 5642b6faaf7cae5489ba4115bcc49393399 |
| SANs: api.betslipdoctor.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.betslipdoctor.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| betslipdoctor.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://api.betslipdoctor.ai/.well-known/oauth-protected-resource", error="invalid_token"
Bearer resource_metadata="https://api.betslipdoctor.ai/.well-known/oauth-protected-resource", error="invalid_token"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | frame-ancestors 'none' |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Document | https://api.betslipdoctor.ai/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://api.betslipdoctor.ai/api/mcp |
| Authorisation server | https://api.betslipdoctor.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.betslipdoctor.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://api.betslipdoctor.ai/api/mcp | HTTPS enforced | 308 | https://api.betslipdoctor.ai/api/mcp |
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 →
get_history_summary Betting history summary ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| recent | integer | – | How many recent bets to include (default 5). |
No output schema declared.
No examples provided.
get_saved_reports Saved reports ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Compact list size (default 10). |
| report_id | string | – | Return this one report in full instead of the compact list. |
No output schema declared.
No examples provided.
get_todays_board Today's board (live odds) ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
get_tracked_slips Tracked slips ~47
Read the authenticated user's tracked ticket trees and tracking lifecycle. Provider placement ids and sportsbook deep links are never returned.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Tickets to return (default 20). |
No output schema declared.
No examples provided.
grade_slip Grade a betslip ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
price_shop_slip Price-shop a slip ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| legs | array | yes | – |
No output schema declared.
No examples provided.
track_slip Track a slip ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client_mutation_id | string | yes | Caller-generated idempotency key. |
| expected_revision | integer | – | Required with ticket_id; stale writes fail with a conflict. |
| ticket | object | yes | BSD two-level BetTicketContract. SGP children stay nested under one outer pick. |
| ticket_id | string | – | Server ticket id when revising an existing tracked slip. |
No output schema declared.
No examples provided.
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.