DFS Lineup Optimizer MCP server
com.kindoflost.nhl-lineup-optimizer/dfs-lineup-optimizernhl-lineup-optimizer.kindoflost.comstreamable-httpv1.0.0Scanned
Builds MLB, NFL, NHL and NBA DFS lineups with a real optimizer: cap, stacks, exposure. Free.
5 tools: 2 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the DFS Lineup Optimizer MCP server can do
The DFS Lineup Optimizer MCP server is published by nhl-lineup-optimizer.kindoflost.com, a domain the MCP Registry verified. It has 5 tools. It can create or change data (2 tools: check_request and build_lineups), but cannot delete data. 3 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 17, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 2Claude Code: ask
build_lineupsBuild up to 20 lineups for a Classic contest.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Build up to 20 lineups for a Classic contest. Pass `example` (a sample slate) or `players` (the site's salary CSV text, or a list of player objects for DraftKings). Returns each lineup with its players, slots, salary and projected points, player exposure, notes about what defaults were applied, and `upload_csv`: a DraftKings/FanDuel/Yahoo upload-ready CSV string. Takes 2-60 s; if the result has status 'running', call get_lineup_result with the job_id. Lineups are optimal for the PROJECTIONS used, not predictions of results.
Annotations the server declares
- title: Build DFS lineups
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
check_requestValidate a build_lineups request WITHOUT solving: arguments, rule names and ranges, that the players parse, that locks/exclusions/projection names match real players, and that ever…1 finding
Why it is in this group
- The name "check_request" says "request": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "check_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "check_request" says "request": a word for a change.
Description, as the server wrote it Validate a build_lineups request WITHOUT solving: arguments, rule names and ranges, that the players parse, that locks/exclusions/projection names match real players, and that every roster slot has enough eligible players. Takes the same arguments as build_lineups. Fast.
Annotations the server declares
- title: Check a lineup request
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
Only reads 3Show 3 read-only tools
get_lineup_exampleReturn a ready-to-run build_lineups request for a sport using its bundled sample slate, a short preview of the slate, the player-list format, and the rules available for that sport…No findings
Why it is in this group
- The name "get_lineup_example" says "get": a word for reading.
Description, as the server wrote it Return a ready-to-run build_lineups request for a sport using its bundled sample slate, a short preview of the slate, the player-list format, and the rules available for that sport.
Annotations the server declares
- title: Get an example lineup request
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_lineup_resultFetch the result of a build_lineups job that returned status 'running'.No findings
Why it is in this group
- The name "get_lineup_result" says "get": a word for reading.
Description, as the server wrote it Fetch the result of a build_lineups job that returned status 'running'. Waits up to wait_seconds; call again while status is 'running'. Jobs expire 15 minutes after they finish.
Annotations the server declares
- title: Get a lineup result
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_lineup_examplesList the bundled sample slates, one per sport (real past DraftKings Classic slates).No findings
Why it is in this group
- The name "list_lineup_examples" says "list": a word for reading.
Description, as the server wrote it List the bundled sample slates, one per sport (real past DraftKings Classic slates). Each can be built as-is with build_lineups(example=...).
Annotations the server declares
- title: List sample slates
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 18, 2026, 16:18 UTC, unchanged since Nov 18, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://nhl-lineup-optimizer.kindoflost.com/mcp: tools/list returned 5 tools to an anonymous client, including check_request (write), build_lineups (write)
Findings
Matches of fixed checks, with the text they matched.
- Warncheck_request
The server marks "check_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "check_request" says "request": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http dfs-lineup-optimizer https://nhl-lineup-optimizer.kindoflost.com/mcpclaude mcp add --transport http dfs-lineup-optimizer https://nhl-lineup-optimizer.kindoflost.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__dfs-lineup-optimizer__list_lineup_examples",
"mcp__dfs-lineup-optimizer__get_lineup_example",
"mcp__dfs-lineup-optimizer__get_lineup_result"
],
"ask": [
"mcp__dfs-lineup-optimizer__check_request",
"mcp__dfs-lineup-optimizer__build_lineups"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as dfs-lineup-optimizer. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.kindoflost.nhl-lineup-optimizer/dfs-lineup-optimizer/verify?hash=c876bd93ad5ab70d3c543a1db2b44e37ea6057345c34fc9c9bdb8b98b4e2a711" | jq -e '.changed == false'Pinned hash c876bd93ad5a, from Nov 17, 2026, 21:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.kindoflost.nhl-lineup-optimizer/dfs-lineup-optimizer/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.kindoflost.nhl-lineup-optimizer/dfs-lineup-optimizer)Source: MCP Registry. Synced Nov 17, 2026, 21:17 UTC.
DFS Lineup Optimizer MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the DFS Lineup Optimizer MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the DFS Lineup Optimizer MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the DFS Lineup Optimizer MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the DFS Lineup Optimizer MCP server have?
- 5 tools: 2 write, 3 read. check_request, build_lineups, list_lineup_examples, get_lineup_example and get_lineup_result.
Does the DFS Lineup Optimizer MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the DFS Lineup Optimizer MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the DFS Lineup Optimizer MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.