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/YosoAgents/agent-sdkWrote 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/yosoagents/agent-sdk/yoso-agent)<a href="https://agentmods.dev/mcp/yosoagents/agent-sdk/yoso-agent"><img src="https://agentmods.dev/badge/mcp/yosoagents/agent-sdk/yoso-agent.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
yoso-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 6d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 6d ago First seen · 9 lines scan A e634d8e70ef4
yoso-agent is an MCP server published in the GitHub repository YosoAgents/agent-sdk (0 stars, last pushed 16d ago), with no licence file. 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
fibx
Swap, transfer, track a portfolio and use Aave V3 on Base, HyperEVM and Monad. Runs locally from the fibx npm package. Needs 2 environment variables to run.
hyperevm-mcp
Read-only Hyperliquid and HyperEVM data: yields, protocols, fees, markets, funding, depth. Runs locally from the @sand0vvv/hyperevm-mcp npm package.
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.
claude-octopus
Spawn multiple specialized Claude Code agents as MCP servers, each independently configured. Runs locally from the claude-octopus npm package. Needs 7 environment variables to run.
stellar-rpc
MCP server "stellar-rpc" as configured in rylsherdamz-rgb/stellar-forge. Runs locally from the @stellar/mcp-server npm package. Needs 2 environment variables to run.
bug-bounty-intelligence-mcp
AI security scanner for Solidity + free CC0 dataset of Sherlock audit-competition acceptance rates. Remote server at wazir-x402.duckdns.org.