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/cute-aaa/OmniParser-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/cute-aaa/omniparser-mcp/omniparser)<a href="https://agentmods.dev/mcp/cute-aaa/omniparser-mcp/omniparser"><img src="https://agentmods.dev/badge/mcp/cute-aaa/omniparser-mcp/omniparser/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/cute-aaa/omniparser-mcp/omniparser"><img src="https://agentmods.dev/badge/mcp/cute-aaa/omniparser-mcp/omniparser.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
omniparser 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 4d 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
Licensed CC-BY-4.0
The repository is licensed CC-BY-4.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 4d ago First seen · 13 lines scan A e63568b52967
omniparser is an MCP server published in the GitHub repository cute-aaa/OmniParser-MCP (0 stars, last pushed 5d ago), licensed CC-BY-4.0. 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-10-16.
Other mcp servers, from other repositories
context7
Gives the agent up-to-date documentation and code examples for libraries and frameworks, fetched on demand so answers are not stuck at the model's training cutoff. Runs locally from the @upstash/context7-mcp npm package. Needs 1 environment variable to run.
mcp-server-search
MCP server for web search operations. Runs locally from the @agent-infra/mcp-server-search npm package.
email-mcp
IMAP/SMTP email MCP server — 52 tools, stdio + HTTP, IMAP IDLE push, multi-account, AI triage. Runs locally from the @codefuturist/email-mcp npm package.
web-access
The most accurate web access API. Stop getting blocked. Runs locally from the @usestring/mcp npm package. Needs 1 environment variable to run.
sendgrid-mcp
MCP server for SendGrid's v3 API: email marketing, transactional mail, templates, and analytics. Runs locally from the sendgrid-mcp npm package. Needs 2 environment variables to run.
root-mcp
Production-grade MCP server for CERN ROOT file analysis. Runs locally from the root-mcp Python package.