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/lemahq/lema-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/lemahq/lema-mcp/lema)<a href="https://agentmods.dev/mcp/lemahq/lema-mcp/lema"><img src="https://agentmods.dev/badge/mcp/lemahq/lema-mcp/lema/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/lemahq/lema-mcp/lema"><img src="https://agentmods.dev/badge/mcp/lemahq/lema-mcp/lema.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lema 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 2mo 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
{
"lema": {
"command": "npx",
"args": [
"-y",
"lema-mcp@latest"
],
"env": {
"LEMA_MCP_MODE": "public",
"LEMA_PUBLIC_REPO": "react-rfcs"
}
}
}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.
- 2mo ago First seen · 13 lines scan A 000504033699
lema is an MCP server published in the GitHub repository lemahq/lema-mcp (1 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
engram
Ranked local code-graph context for AI coding agents. Intercepts reads + greps. Apache-2.0. Runs locally from the engramx npm package. Needs 5 environment variables to run.
superskill
One-entry orchestrator for coding agents: jailed vault, FTS knowledge graph, 18-axis review, in-harness Chrome QA. Curated packs — not a 90k-skill dump. Runs locally from the superskill npm package.
graphyloop
Agentic workflow kit for AI coding agents: one command wires Claude Code, Codex, Cursor, Gemini CLI, OpenCode, Oh My Pi and DeepSeek with Workflow v3, a 25-agent squad, memory, Agent Skills and MCP. Claude Code plugin + MCP Registry. Zero deps. Runs locally from the graphyloop npm package.
fonto-docs
Fonto (FontoXML) documentation for AI tools. Converts DITA XML to Markdown on demand. Remote server at fonto-docs.elliat.nl.
contextforge-mcp
Persistent memory MCP server for Claude Code, Cursor, and GitHub Copilot. Runs locally from the contextforge-mcp npm package. Needs 2 environment variables to run.
agents-docs
Local markdown docsets with header-aware BM25 search via CLI and MCP. Runs locally from the agents-docs Python package.