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/sand0vvv/mayan-mcpWrote 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/sand0vvv/mayan-mcp/mayan-mcp)<a href="https://agentmods.dev/mcp/sand0vvv/mayan-mcp/mayan-mcp"><img src="https://agentmods.dev/badge/mcp/sand0vvv/mayan-mcp/mayan-mcp/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/sand0vvv/mayan-mcp/mayan-mcp"><img src="https://agentmods.dev/badge/mcp/sand0vvv/mayan-mcp/mayan-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mayan-mcp 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 10d 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
{ "mayan-mcp": { "command": "npx", "args": [ "-y", "@sand0vvv/mayan-mcp" ] } }
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.
- 10d ago First seen · 9 lines scan A bf94a48f748f
mayan-mcp is an MCP server published in the GitHub repository sand0vvv/mayan-mcp (0 stars, last pushed 1mo 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
mcp-mercado-bitcoin
MCP server for Mercado Bitcoin — Brazilian crypto exchange, trading, orderbook, withdrawals. Runs locally from the @codespar/mcp-mercado-bitcoin npm package. Needs 1 environment variable to run.
sap-mcp
Solana-native MCP gateway for SAP, DeFi tools, SNS identity, and x402 payments. Runs locally from the @oobe-protocol-labs/sap-mcp-server npm package. Needs 2 environment variables to run.
x402-cleanweb-agent
Deterministic Web3 x402 Micropayment MCP & AI Agent Tool Suite with Gemini 3.6 Flash Video Intelligence on Polygon, Base, and Arbitrum. Runs locally from the x402-cleanweb-agent Python package.
agentfund
Fundraising tools for AI agents on Solana: create campaigns, donate via x402, check reputation. Runs locally from the @agentfund/mcp npm package. Needs 2 environment variables to run.
binance-mcp-server
Binance USDS-M Futures MCP server: 61 tools across market / indicator / analysis / trading domains, built on MCP server v2 + official Binance SDK. Runs locally from the @iuk-ink/binance-mcp-server npm package.
mintclub
Trade bonding curve tokens on Base via Mint Club V2 — buy, sell, swap, create. Runs locally from the mintclub-mcp npm package. Needs 1 environment variable to run.