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/Zhao73/alphacouncil-agentWrote 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/zhao73/alphacouncil-agent/alphacouncil-agent)<a href="https://agentmods.dev/mcp/zhao73/alphacouncil-agent/alphacouncil-agent"><img src="https://agentmods.dev/badge/mcp/zhao73/alphacouncil-agent/alphacouncil-agent/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/zhao73/alphacouncil-agent/alphacouncil-agent"><img src="https://agentmods.dev/badge/mcp/zhao73/alphacouncil-agent/alphacouncil-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
alphacouncil-agent 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 9d 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
{
"alphacouncil-agent": {
"command": "npx",
"args": [
"-y",
"alphacouncil-agent"
],
"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.
- 9d ago First seen · 10 lines scan A a60aa883d94d
alphacouncil-agent is an MCP server published in the GitHub repository Zhao73/alphacouncil-agent (3 stars, last pushed 2d 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
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.
openfilings
Official Python client for the OpenFilings API — multi-market filings, canonical KPIs, and signed webhooks. Runs locally from the openfilings Python package.
finance-agent-mcp
MCP server "finance-agent-mcp" as configured in arturio-amorim/finance-agent-mcp. Runs locally from the finance-agent-mcp Python package.
authoryze
Give your AI agent a spending limit: approval controls and single-use virtual cards. Remote server at authoryze.ai.
junto-mcp
The payment protocol for people and agents. One MCP server, any payment rail. Runs locally from the junto-mcp npm package. Needs 4 environment variables to run.
equity-intel-mcp
Institutional-grade equity analysis (insider, superinvestor, valuation) over MCP. Runs locally from the equity-intel-mcp Python package.