Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/parlay-run/parlay-mcp/parlaygit clone --depth 1 https://github.com/parlay-run/parlay-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/parlay-run/parlay-mcp/parlay)<a href="https://agentmods.dev/mcp/parlay-run/parlay-mcp/parlay"><img src="https://agentmods.dev/badge/mcp/parlay-run/parlay-mcp/parlay.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
parlay scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"parlay": {
"url": "https://mcp.parlay.run/mcp",
"transport": "streamable-http",
"headers": {
"Authorization": "Bearer ${PARLAY_TOKEN}"
},
"connectionTimeoutMs": 30000
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 10 lines scan A 51fed274630b
parlay is an MCP server published in the GitHub repository parlay-run/parlay-mcp (6 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
oddsrail
MCP server giving AI trading agents access to prediction markets (Polymarket, Kalshi) with on-chain builder-code attribution and trading signals. Runs locally from the oddsrail Python package. Needs 1 environment variable to run.
simmer-mcp
Trade prediction markets with AI agents — skill discovery, autoresearch, and execution. Runs locally from the simmer-mcp npm package. Needs 2 environment variables to run.
clearmarket
Reference data for prediction markets: graded resolution clarity, cross-venue links, provenance. Remote server at api.clearmarket.fyi.
whale-data-mcp
Signed settled outcomes (Polymarket, sports, Kalshi) + whale signals as agent tools, paid via x402. Runs locally from the @predge/whale-data-mcp npm package. Needs 7 environment variables to run.
parlayapi
MCP server for ParlayAPI: sports odds, live previews, source-quality proof, and frictionless agent signup. Runs locally from the parlayapi-mcp Python package.
kalshi
Kalshi MCP — US-regulated prediction-market data (no auth on public reads). Remote server at gateway.pipeworx.io.