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/MarketTrace/markettrace-agent-feedWrote 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/markettrace/markettrace-agent-feed/agent-feed)<a href="https://agentmods.dev/mcp/markettrace/markettrace-agent-feed/agent-feed"><img src="https://agentmods.dev/badge/mcp/markettrace/markettrace-agent-feed/agent-feed.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
agent-feed 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 6d 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
{ "agent-feed": { "url": "https://api.markettrace.ai/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.
- 6d ago First seen · 6 lines scan A 1604ee57ef48
agent-feed is an MCP server published in the GitHub repository MarketTrace/markettrace-agent-feed (0 stars, last pushed 4d 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
headless-tracker
Not financial advice. Crypto portfolio aggregation across exchanges, wallets, prediction markets. Runs locally from the headless-tracker npm package.
crypto-quant-signal-mcp
Quant trading signals, funding rate arb scanning, and market regime detection for crypto perps. Runs locally from the crypto-quant-signal-mcp npm package.
mcp
Live crypto data: funding rates, funding arbitrage, OI pressure, Fear & Greed. Free, no API key. Runs locally from the bykaranteli-mcp npm package.
cerebrus-pulse-mcp
MCP server for Cerebrus Pulse — real-time crypto intelligence API for Hyperliquid perpetuals. Runs locally from the cerebrus-pulse-mcp Python package.
traderspy
MCP server "traderspy", hosted remotely, as configured in target1m/traderspy-mcp.
kainext-binance-mcp
MCP server for Binance spot: read market data, analyze, and propose real-money trades behind a human-gated confirmer. The model never holds a trade key. Runs locally from the kainext-binance-mcp Python package. Needs 3 environment variables to run.