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/sherifkozman/eve-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/sherifkozman/eve-mcp/eve-client)<a href="https://agentmods.dev/mcp/sherifkozman/eve-mcp/eve-client"><img src="https://agentmods.dev/badge/mcp/sherifkozman/eve-mcp/eve-client/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/sherifkozman/eve-mcp/eve-client"><img src="https://agentmods.dev/badge/mcp/sherifkozman/eve-mcp/eve-client.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
eve-client 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 9d 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
{ "eve-client": { "command": "uvx", "args": [ "eve-client" ] } }
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.
- 9d ago First seen · 8 lines scan A d7467b0d8ec9
eve-client is an MCP server published in the GitHub repository sherifkozman/eve-mcp (1 stars, last pushed 2mo ago), licensed Apache-2.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-08-31.
Other mcp servers, from other repositories
usrcp
Encrypted local ledger of structured user state, shared across every MCP-aware AI tool. Runs locally from the usrcp npm package. Needs 1 environment variable to run.
codeatlas-mcp
MCP server that gives AI assistants (Gemini, Claude, Cursor, Windsurf, Copilot) deep understanding of your codebase — 10 tools + persistent memory. Runs locally from the @giauphan/codeatlas-mcp npm package.
deepwork-dev
Framework for enabling AI agents to perform complex, multi-step work tasks. Runs locally from the deepwork Python package.
engram
Hierarchical memory for AI agents. Three-layer (buffer/working/core) with decay and promotion. Runs locally from the engram-rs-mcp npm package. Needs 2 environment variables to run.
petstore
MCP server "petstore", hosted remotely at 127.0.0.1, as configured in gujord/OpenAPI-MCP.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.