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/asgard-ai-platform/mcp-mayoWrote 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/asgard-ai-platform/mcp-mayo/mayo)<a href="https://agentmods.dev/mcp/asgard-ai-platform/mcp-mayo/mayo"><img src="https://agentmods.dev/badge/mcp/asgard-ai-platform/mcp-mayo/mayo/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/asgard-ai-platform/mcp-mayo/mayo"><img src="https://agentmods.dev/badge/mcp/asgard-ai-platform/mcp-mayo/mayo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mayo 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
{
"mayo": {
"command": "uv",
"args": [
"run",
"mcp-mayo"
],
"cwd": "${PWD}",
"env": {
"PYTHONPATH": "${PWD}",
"MAYO_API_KEY": "${MAYO_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.
- 9d ago First seen · 14 lines scan A 3b9f1b9c6357
mayo is an MCP server published in the GitHub repository asgard-ai-platform/mcp-mayo (0 stars, last pushed 23d 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
ynab-mcp-server
Local MCP server for YNAB budget operations. Runs locally from the @oliverames/mcp-server-for-ynab npm package. Needs 5 environment variables to run.
mcp
Korean stocks: median price path after each DART filing type, plus T+1 closes. Remote server at mcp.aikstockdata.com.
bcb-br-mcp
Banco Central do Brasil (BCB): SGS series, Focus expectations, PTAX, stats + provenance. 15 tools. Runs locally from the bcb-br-mcp npm package.
jp-payroll-mcp
A local tool for Japanese payroll and social-insurance calculations, including regional rates, withholding tax, overtime pay, paid leave, salary revisions, and minimum wages.
pexbot-mcp
PexBot simulated spot/futures trading, competitions, portfolios, and AI analytics. Runs locally from the @pexbot/mcp npm package. Needs 4 environment variables to run.
exchange-rates-mcp-server
Convert currencies, get FX rates, and query historical ECB exchange rate data. Runs locally from the @cyanheads/exchange-rates-mcp-server npm package. Needs 4 environment variables to run.