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/KhazixW2/Everything-MaaWrote 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/khazixw2/everything-maa/maa-mcp)<a href="https://agentmods.dev/mcp/khazixw2/everything-maa/maa-mcp"><img src="https://agentmods.dev/badge/mcp/khazixw2/everything-maa/maa-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
maa-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 7d 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
{
"maa-mcp": {
"command": "uvx",
"args": [
"--from",
"maa-mcp==1.2.3",
"maa-mcp"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 3. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 7d ago First seen · 10 lines scan A 686133f9e3af
maa-mcp is an MCP server published in the GitHub repository KhazixW2/Everything-Maa (12 stars, last pushed 4d 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-30.
Other mcp servers, from other repositories
android-mcp
Android MCP Server for automated app control using uiautomator2. Runs locally from the android-mcp npm package.
playwright-test
A high-level API to automate web browsers. Runs locally from the playwright npm package.
skyvern
AI-powered browser automation — navigate, click, fill forms, and extract data from any website. Remote server at api.skyvern.com.
fetch
Lets the agent fetch a URL and read its content as markdown. Runs locally from the mcp-server-fetch Python package.
hunch
Drive your Mac focus-free over MCP: OS APIs, AppleScript, CDP, and Accessibility. Runs locally from the hunch-sdk Python package.
chrome-mcp-server
MCP server "chrome-mcp-server", hosted remotely at 127.0.0.1, as configured in iloveitaly/llm-ide-rules.