mcp-registry/io.github.jorgeperez0825/v12-dfs · v1.0.0
As of 2026-10-24 23:22 UTC, the Jorgeperez0825 V12 Dfs MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 36 outages in 90 days, with a median recovery of 2 minutes.
AI-driven DFS lineup optimizer for MLB & NBA — build FanDuel & DraftKings lineups via MCP.
Claude Code
claude mcp add --transport http jorgeperez0825-v12-dfs-mcp-server https://v12dfs-production.up.railway.app/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"jorgeperez0825-v12-dfs-mcp-server": {
"type": "http",
"url": "https://v12dfs-production.up.railway.app/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
1 tool definition(s) exceed ~1,200 tokens each (largest: generate_lineups, ~2,473).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~1,873 tokens every session. How to fix →
34 of 34 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
83 parameter(s) across 28 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
4 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 1 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 28 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.jorgeperez0825%2Fv12-dfs/fixes
{
"name": "betting_analyze_prop",
"description": "Analyze Prop\n\nModel a single player's prop vs tonight's FanDuel line -> edge.\n\n### Responses:\n\n**200**: Successful Response (Success Response)\nContent-Type: application/json\n**422**: Validation Error\nContent-Type: application/json\n\n**Example Response:**\n```json\n{\n \"detail\": [\n {\n \"loc\": [],\n \"msg\": \"Message\",\n \"type\": \"Error Type\",\n \"ctx\": {}\n }\n ]\n}\n```",
"inputSchema": {
"type": "object",
"title": "betting_analyze_propArguments",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"title": "name"
},
"prop": {
"type": "string",
"title": "prop",
"default": "home_run"
},
"season": {
"type": "integer",
"title": "season",
"default": 2026
},
"threshold": {
"type": "integer",
"title": "threshold",
"default": 2
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "betting_cross_book",
"description": "Cross Book\n\nCross-book value: FanDuel vs DraftKings (DK pulled via ESPN's public API,\nno key/WS). LINE_SHOP (the books hang different numbers — take the easier\nside) and PRICE_SHOP (better price, same line) are CONFIRMED edges, no model\nneeded. Arbitrage is NOT auto-reported (needs over/under sides, which ESPN\ndoesn't label). Overnight only pitcher_strikeouts overlaps; richer markets\nappear near game time.\n\n### Responses:\n\n**200**: Successful Response (Success Response)\nContent-Type: application",
"inputSchema": {
"type": "object",
"title": "betting_cross_bookArguments",
"properties": {
"prop": {
"type": "string",
"title": "prop",
"default": "pitcher_strikeouts"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "betting_market_movers",
"description": "Market Movers\n\nMARKET pattern (not model opinion): how FanDuel lines MOVED today, from the\ncaptured snapshots. A line that shortened = money coming in (sharp/news); a\ndrift = money off. This is the 'obvious opportunity' signal — market-confirmed,\nindependent of our unproven model. Needs accumulated capture; thin → thin.\n\n### Responses:\n\n**200**: Successful Response (Success Response)\nContent-Type: application/json\n**422**: Validation Error\nContent-Type: application/json\n\n**Example Response:**\n``",
"inputSchema": {
"type": "object",
"title": "betting_market_moversArguments",
"properties": {
"date": {
"type": "string",
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "date"
},
"prop": {
"type": "string",
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "prop"
},
"min_move": {
"type": "number",
"title": "min_move",
"default": 3
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.jorgeperez0825/v12-dfs"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.jorgeperez0825/v12-dfs"}) over MCP.
generate_lineups ~2,473 tokensrun_mlb_postmortem ~563 tokensbetting_build_parlay ~509 tokensbetting_log_bet ~374 tokensslate_health ~312 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.jorgeperez0825%2Fv12-dfs?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.jorgeperez0825%2Fv12-dfs?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jorgeperez0825%2Fv12-dfs.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jorgeperez0825%2Fv12-dfs.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.jorgeperez0825%2Fv12-dfs?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:a5583df5a579b029…, first seen 2026-10-22, included at leaf 48461 of 62,085. Version history · verify what your client received.
Compare: most reliable security servers · most reliable knowledge servers · most reliable ml servers · most reliable finance servers · most reliable data servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-24 23:22 UTC, the Jorgeperez0825 V12 Dfs MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 36 outages in 90 days, with a median recovery of 2 minutes.
Jorgeperez0825 V12 Dfs MCP server advertises 34 tools, including admin_issue_key, agent_guide, betting_agent_guide, betting_analyze_prop, betting_best_bets.
Point your MCP client at this streamable-http endpoint: https://v12dfs-production.up.railway.app/mcp
Glimind scanned all 34 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.