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/razz-games/razz-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/razz-games/razz-mcp/razz)<a href="https://agentmods.dev/mcp/razz-games/razz-mcp/razz"><img src="https://agentmods.dev/badge/mcp/razz-games/razz-mcp/razz/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/razz-games/razz-mcp/razz"><img src="https://agentmods.dev/badge/mcp/razz-games/razz-mcp/razz.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
razz 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
{
"razz": {
"command": "npx",
"args": [
"-y",
"@razzgames/mcp-server"
],
"env": {
"RAZZ_API_KEY": "",
"PLATFORM_WS_URL": "",
"PLATFORM_API_URL": ""
}
}
}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 · 14 lines scan A fba712cb2a73
razz is an MCP server published in the GitHub repository razz-games/razz-mcp (1 stars, last pushed 5mo 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
clash-mcp
Play three.ws Coin Clash — read the faction battle board and leaderboard, enlist, and rally. Runs locally from the @three-ws/clash-mcp npm package. Needs 3 environment variables to run.
fairseal-mcp-server
Verifiable entropy, provably-fair games, and receipt verification for AI agents (FairSeal API). Runs locally from the @fairseal/mcp-server npm package. Needs 2 environment variables to run.
arcade1v1
Play 1v1 arcade games vs AI agents & humans, ranked by ELO. Replay-verified, on-chain escrow (Base). Runs locally from the @arcade1v1/mcp npm package. Needs 1 environment variable to run.
mcp-server
BattleGrid MCP server — play crypto prediction games from AI agents. Runs locally from the @battlegrid/mcp-server npm package.
loot-agent-mcp
MCP server "loot-agent-mcp" as configured in D-Kek/loot-agent-mcp. Runs locally from the loot-agent-mcp npm package. Needs 4 environment variables to run.
axie-mcp
MCP server for Axie Infinity — search Axies, land, players, leaderboards, and marketplace data. Runs locally from the axie-mcp npm package.