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.
git clone --depth 1 https://github.com/yakub268/kalshi-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/yakub268/kalshi-mcp/kalshi)<a href="https://agentmods.dev/mcp/yakub268/kalshi-mcp/kalshi"><img src="https://agentmods.dev/badge/mcp/yakub268/kalshi-mcp/kalshi/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/yakub268/kalshi-mcp/kalshi"><img src="https://agentmods.dev/badge/mcp/yakub268/kalshi-mcp/kalshi.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
kalshi 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 10d 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
{
"kalshi": {
"command": "uvx",
"args": [
"kalshi-mcp"
],
"env": {
"KALSHI_API_KEY": "",
"KALSHI_PRIVATE_KEY_PATH": ""
}
}
}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.
- 10d ago First seen · 12 lines scan A 7d25b72756c9
kalshi is an MCP server published in the GitHub repository yakub268/kalshi-mcp (0 stars, last pushed 6mo 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
etoro-mcp
MCP server "etoro-mcp" as configured in florinel-chis/etoro-mcp. Runs locally from the etoro-mcp Python package.
trading212-mcp
MCP server "trading212-mcp" as configured in florinel-chis/trading212-mcp. Runs locally from the trading212-mcp Python package.
expense-tracker-mcp
MCP server "expense-tracker-mcp" as configured in tanishra/Expense-Tracker-MCP. Runs locally from the expense-tracker-mcp Python package.
tradingview-mcp
Real-time market data, screeners, technical analysis & backtesting for stocks, crypto and forex. Remote server at mcp.cryptosieve.com.
polymarket-toolkit
Read-only Polymarket data tools for AI agents: profiles, PnL, market scans. No keys, no orders. Runs locally from the polymarket-toolkit-mcp npm package.
docker_twstockmcpserver
MCP server "dockertwstockmcpserver" as configured in twjackysu/TWSEMCPServer. Runs in Docker (ghcr.io/twjackysu/twsemcpserver:latest).