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/derkcc/market-depth-lab-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/derkcc/market-depth-lab-mcp/market-depth-lab)<a href="https://agentmods.dev/mcp/derkcc/market-depth-lab-mcp/market-depth-lab"><img src="https://agentmods.dev/badge/mcp/derkcc/market-depth-lab-mcp/market-depth-lab/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/derkcc/market-depth-lab-mcp/market-depth-lab"><img src="https://agentmods.dev/badge/mcp/derkcc/market-depth-lab-mcp/market-depth-lab.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
market-depth-lab 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
{
"market-depth-lab": {
"command": "npx",
"args": [
"-y",
"market-depth-lab-mcp-server"
],
"env": {
"MDL_POSITION_INDEX_URL": "https://data.marketdepthlab.com/v1/positions/latest",
"MDL_POSITION_INDEX_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 · 13 lines scan A 1e001e635f7a
market-depth-lab is an MCP server published in the GitHub repository derkcc/market-depth-lab-mcp (0 stars, last pushed 1mo 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
traderspy
MCP server "traderspy", hosted remotely, as configured in target1m/traderspy-mcp.
carrydesk
Cross-sectional funding-carry rankings for Hyperliquid perpetuals, sold per call in USDC. Runs locally from the carrydesk Python package. Needs 2 environment variables to run.
agent-feed
Crypto perps data for AI agents: funding rates, open interest, liquidations, order book, CVD. Remote server at api.markettrace.ai.
hyperliquid-mcp
Read-only Hyperliquid data: markets, funding rates, order books, candles, positions and fills. Runs locally from the @kitsune-de/hyperliquid-mcp npm package.
polskidegen-hl-tracker
Model Context Protocol server for Hyperliquid — read-only public data (positions, fills, funding, PnL) for any wallet address. Runs locally from the polskidegen-hl-tracker npm package.
polymarket-mcp
The simplest MCP server for Polymarket prediction-market data. Runs locally from the polymarket-mcp Python package.