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/gigshow/decker-ai/deckergit clone --depth 1 https://github.com/gigshow/decker-aiWrote 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/gigshow/decker-ai/decker)<a href="https://agentmods.dev/mcp/gigshow/decker-ai/decker"><img src="https://agentmods.dev/badge/mcp/gigshow/decker-ai/decker.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
decker 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
{
"decker": {
"url": "https://api.decker-ai.com/api/v1/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 03e91357af47
decker is an MCP server published in the GitHub repository gigshow/decker-ai (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
mcp-upbit
Fast MCP server for interacting with Upbit (public market data and optional private trading tools). Runs locally from the @iqai/mcp-upbit npm package.
midasflow
MCP server "midasflow", hosted remotely at mcp.midasflow.ai, as configured in midasflowai-lab/midasflow-mcp-quickstart.
midasflow-mcp-quickstart
Agent-native crypto market-data over MCP+REST: order flow, whales, liquidations, calibrated scores. Remote server at mcp.midasflow.ai.
trading212-mcp-server
MCP server for Trading 212 - 32 tools for portfolio management, trading, pies, dividends, and analytics. Works with Claude, ChatGPT, Cursor, and any MCP client. Runs locally from the trading212-mcp-server Python package. Needs 3 environment variables to run.
coinlobster
MCP server "coinlobster", hosted remotely at coinlobster.com, as configured in CoinLobster/agent-skills.
mcp-trading
Keyless prediction-market data across 12 venues plus paper-trading of crypto spot, futures, and PM. Runs locally from the @coinrithm/mcp-trading npm package. Needs 2 environment variables to run.