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/julianoczkowski/mcp-modusWrote 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/julianoczkowski/mcp-modus/mcp-modus)<a href="https://agentmods.dev/mcp/julianoczkowski/mcp-modus/mcp-modus"><img src="https://agentmods.dev/badge/mcp/julianoczkowski/mcp-modus/mcp-modus.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mcp-modus 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 8d 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
{ "mcp-modus": { "command": "npx", "args": [ "-y", "@julianoczkowski/mcp-modus" ] } }
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.
- 8d ago First seen · 9 lines scan A 336e88c36a26
mcp-modus is an MCP server published in the GitHub repository julianoczkowski/mcp-modus (4 stars, last pushed 2mo 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-server
MCP server for SAPUI5/OpenUI5 development. Runs locally from the @ui5/mcp-server npm package. Needs 5 environment variables to run.
mcp
AI-powered design and management for Webflow Sites. Remote server at mcp.webflow.com.
performance-ai-mcp
Performance Ai automation via MCP. Includes analyze waterfall data, suggest optimizations, calculate core web vitals. By MEOK AI Labs. Runs locally from the performance-ai-mcp Python package.
web-ui-component-spec-mcp
MCP server for the Web UI Component Specification — behavioral specs, tests, and principles for web UI component libraries. Runs locally from the web-ui-component-spec-mcp Python package.
podium
Mobile + canvas automation MCP for AI agents — one stdio server, 60 tools: iOS (simulator + real) & Android control, native UI automation, Maestro E2E flows, evidenced oracle-ladder assertions, React Native/Metro debugging, WebView DOM + network capture. Runs locally from the podium-mcp npm package.
flowbite-mcp
MCP server to convert Figma designs to Flowbite UI components in Tailwind CSS. Runs locally from the flowbite-mcp npm package. Needs 1 environment variable to run.