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/midasflowai-lab/midasflow-mcp-quickstart/midasflowgit clone --depth 1 https://github.com/midasflowai-lab/midasflow-mcp-quickstartWrote 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/midasflowai-lab/midasflow-mcp-quickstart/midasflow)<a href="https://agentmods.dev/mcp/midasflowai-lab/midasflow-mcp-quickstart/midasflow"><img src="https://agentmods.dev/badge/mcp/midasflowai-lab/midasflow-mcp-quickstart/midasflow.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
midasflow 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 5d 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
{
"midasflow": {
"type": "http",
"url": "https://mcp.midasflow.ai/mcp",
"headers": {
"Authorization": "Bearer mf_live_YOUR_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.
- 5d ago First seen · 9 lines scan A e83ddc18a3b6
midasflow is an MCP server published in the GitHub repository midasflowai-lab/midasflow-mcp-quickstart (0 stars, last pushed 2mo 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
price-data-mcp
An MCP server that gives AI agents live market prices and candles. Data only, no trading advice. Runs locally from the hyperliquid-price-mcp Python package.
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.
mcp-server
MCP server that gives coding agents typed 0xArchive market data tools across Hyperliquid (perps, HIP-3, HIP-4, spot) and Lighter.xyz. Runs locally from the @0xarchive/mcp-server npm package.
mcp
MCP server "mcp" as configured in longbridge/longbridge-mcp. Runs in Docker (ghcr.io/longbridge/longbridge-mcp:0.9.0). Needs 3 environment variables to run.
hive
MCP server "hive", hosted remotely at mcp.hiveintelligence.xyz, as configured in hive-intel/hive-sdk.
decker
Deterministic market-state engine for trading agents — state, gate, coordinates, with receipts. Remote server at api.decker-ai.com.