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/alphasmo/alphasmo-toolsWrote 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/alphasmo/alphasmo-tools/alphasmo-tools)<a href="https://agentmods.dev/mcp/alphasmo/alphasmo-tools/alphasmo-tools"><img src="https://agentmods.dev/badge/mcp/alphasmo/alphasmo-tools/alphasmo-tools/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/alphasmo/alphasmo-tools/alphasmo-tools"><img src="https://agentmods.dev/badge/mcp/alphasmo/alphasmo-tools/alphasmo-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
alphasmo-tools 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
{
"alphasmo-tools": {
"command": "npx",
"args": [
"-y",
"alphasmo"
],
"env": {
"ALPHASMO_API_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.
- 1mo ago First seen · 12 lines scan A d39acbc5712c
alphasmo-tools is an MCP server published in the GitHub repository alphasmo/alphasmo-tools (2 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
ko-mcp
Real SEC, 13F, insider, congress & macro data your AI agent can cite. Hosted MCP, 24 tools. Remote server at mcp.ko.io.
mcp-banco-do-brasil
MCP server for Banco do Brasil — Pix, Cobrança (boleto), Conta-Corrente, Arrecadação (OAuth2 + mTLS). Runs locally from the @codespar/mcp-banco-do-brasil npm package. Needs 6 environment variables to run.
mcp-bradesco
MCP server for Bradesco — Pix, Cobrança (boleto), Arrecadação, Extrato (OAuth2 + mTLS). Runs locally from the @codespar/mcp-bradesco npm package. Needs 5 environment variables to run.
mcp-worldpay
MCP server for Access Worldpay — enterprise processor: authorize, capture, refund, tokenize. Runs locally from the @codespar/mcp-worldpay npm package. Needs 5 environment variables to run.
mcp-epayco
MCP server for ePayco — Colombian gateway: cards, PSE, Daviplata and cash networks. Runs locally from the @codespar/mcp-epayco npm package. Needs 3 environment variables to run.
mcp-belvo
Belvo — Open Finance aggregator for LATAM. Runs locally from the @codespar/mcp-belvo npm package. Needs 3 environment variables to run.