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/jdsource/clearmarket/clearmarketgit clone --depth 1 https://github.com/JDSource/clearmarketWrote 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/jdsource/clearmarket/clearmarket)<a href="https://agentmods.dev/mcp/jdsource/clearmarket/clearmarket"><img src="https://agentmods.dev/badge/mcp/jdsource/clearmarket/clearmarket.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
clearmarket 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 4d 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
{
"clearmarket": {
"url": "https://api.clearmarket.fyi/mcp",
"type": "streamable-http"
}
}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.
- 4d ago First seen · 6 lines scan A ca7f2cae5f10
clearmarket is an MCP server published in the GitHub repository JDSource/clearmarket (3 stars, last pushed today), 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
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.
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.
polymarket-mcp
MCP server "polymarket-mcp" as configured in beejmaxx/polymarket-mcp-rs. Launched with https://github.com/beejmaxx/polymarket-mcp-rs/releases/download/v0.1.1/polymarke.
pmq
Fail-closed execution and market-data layer for Polymarket CLOB V2: local signing, confirmed fills only, fee-correct math, working deposit-wallet (POLY1271) support. Runs locally from the pmquant Python package. Needs 11 environment variables to run.
parlay
MCP server "parlay", hosted remotely at mcp.parlay.run, as configured in parlay-run/parlay-mcp.
prediction-mcp
MCP server providing unified access to prediction market data from Kalshi and Polymarket. Runs locally from the prediction-mcp npm package.