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/TingdeLiu/quant.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/tingdeliu/quant.ai/quant-ai)<a href="https://agentmods.dev/mcp/tingdeliu/quant.ai/quant-ai"><img src="https://agentmods.dev/badge/mcp/tingdeliu/quant.ai/quant-ai/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/tingdeliu/quant.ai/quant-ai"><img src="https://agentmods.dev/badge/mcp/tingdeliu/quant.ai/quant-ai.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
quant-ai 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
{ "quant-ai": { "command": "uvx", "args": [ "quant-ai" ] } }
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 · 8 lines scan A f574f95347a4
quant-ai is an MCP server published in the GitHub repository TingdeLiu/quant.ai (1 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
keel-trade
Keel — CLI and MCP server for building and backtesting Hyperliquid strategies with your AI assistant. Runs locally from the keel-trade Python package.
trading-cli
MCP server "trading-cli" as configured in Alorse/trading-cli. Launched with trading-cli mcp.
helvetic-research
Research-only MCP server: turn your AI into a quant research desk — backtests, no trades. Remote server at helveticresearch.com.
citeguard-cli
Check a bibliography for retracted papers -- retractions, corrections, and expressions of concern via Crossref (including Retraction Watch records). CLI, Python library, MCP server, GitHub Action. Runs locally from the citeguard-cli Python package.
rewynd
MCP server "rewynd" as configured in SrinjoyDev/rewynd. Launched with rewynd mcp.
tracer
MCP server "tracer" as configured in aiquilibria/contAIned. Runs contained.tracer_mcp with python3.