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/tamasPetki/HeadlessTrackerWrote 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/tamaspetki/headlesstracker/headless-tracker)<a href="https://agentmods.dev/mcp/tamaspetki/headlesstracker/headless-tracker"><img src="https://agentmods.dev/badge/mcp/tamaspetki/headlesstracker/headless-tracker/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/tamaspetki/headlesstracker/headless-tracker"><img src="https://agentmods.dev/badge/mcp/tamaspetki/headlesstracker/headless-tracker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
headless-tracker 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
{
"headless-tracker": {
"command": "npx",
"args": [
"-y",
"headless-tracker"
],
"env": {}
}
}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 · 10 lines scan A 7f336e3697c6
headless-tracker is an MCP server published in the GitHub repository tamasPetki/HeadlessTracker (6 stars, last pushed 26d 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
agent-feed
Crypto perps for AI agents: funding, open interest, liquidations, order book, CVD, volume profile. Remote server at api.markettrace.ai.
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.
binance-mcp
MCP server for Binance exchange - spot trading, staking, wallet, NFT, pay, mining, and more. Runs locally from the @nirholas/binance-mcp-server npm package. Needs 2 environment variables to run.
binance-mcp
MCP server for live crypto trading via Binance.US with comprehensive market intelligence, news, and advanced analytics. Runs locally from the binance-mcp Python 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.
traderspy
MCP server "traderspy", hosted remotely, as configured in target1m/traderspy-mcp.