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/edgedepthhq/edgedepth-research-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/edgedepthhq/edgedepth-research-mcp/research)<a href="https://agentmods.dev/mcp/edgedepthhq/edgedepth-research-mcp/research"><img src="https://agentmods.dev/badge/mcp/edgedepthhq/edgedepth-research-mcp/research/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/edgedepthhq/edgedepth-research-mcp/research"><img src="https://agentmods.dev/badge/mcp/edgedepthhq/edgedepth-research-mcp/research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
research 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 1mo 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
{
"research": {
"command": "npx",
"args": [
"-y",
"@edgedepth/research-mcp"
],
"env": {
"EDGEDEPTH_API_KEY": ""
}
}
}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.
- 1mo ago First seen · 12 lines scan A f548cc561926
research is an MCP server published in the GitHub repository edgedepthhq/edgedepth-research-mcp (3 stars, last pushed 15d 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
undertow
Daily editorials, exit costs, depth concentration, tiers, and sealed records. No commodity futures. Remote server at api.seiche.info.
tickscope-mcp
Real-time, free crypto market data for any AI coding agent — via MCP. Runs locally from the tickscope-mcp Python package.
cnequity
Open, self-hosted financial data infrastructure for China markets, starting with A-shares. Runs locally from the cnequity Python package.
defeatbeta-api
An open-source alternative to Yahoo Finance's market data APIs with higher reliability. Runs locally from the defeatbeta-api Python package.
mcp
Hyperliquid and Lighter market data: order books, trades, candles, funding, OI, and webhooks. Remote server at mcp.0xarchive.io.
pulse-verity
MCP server for signed, verifiable Pulse Verity Index crypto prices and private API feedback. Runs locally from the pulse-verity npm package. Needs 1 environment variable to run.