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/esherialabs/esheria-pythonWrote 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/esherialabs/esheria-python/esheria)<a href="https://agentmods.dev/mcp/esherialabs/esheria-python/esheria"><img src="https://agentmods.dev/badge/mcp/esherialabs/esheria-python/esheria/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/esherialabs/esheria-python/esheria"><img src="https://agentmods.dev/badge/mcp/esherialabs/esheria-python/esheria.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
esheria 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 1mo 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
{
"esheria": {
"command": "uvx",
"args": [
"esheria"
],
"env": {
"ESHERIA_API_BASE_URL": "https://api.esheria.ai",
"ESHERIA_API_KEY": ""
}
}
}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.
- 1mo ago First seen · 12 lines scan A 88a8d4d8de3c
esheria is an MCP server published in the GitHub repository esherialabs/esheria-python (0 stars, last pushed 3mo 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
clio-mcp
Connect Claude to Clio: 34 tools for matters, custom fields, notes, documents, folders, billing. Runs locally from the @oktopeak/clio-mcp npm package. Needs 9 environment variables to run.
trademarks
Trademark search, monitoring and conflict research across 30+ registers, with provenance. Remote server at markmesh.com.
german-legal-mcp
MCP server and typed components for German, Austrian and EU legal research. Runs locally from the @metaneutrons/german-legal-mcp npm package.
vnlaw-kg
MCP server "vnlaw-kg" as configured in handonn2000/vnlawkg. Runs locally from the vnlaw-kg Python package.
lr-labs
Deterministic cross-border tax engine: PE, GAAR, Indian TP, rule-level lookup. Compiled law, no LLM. Remote server at lrlabs.ai.
open-agreements
Fill standard legal agreement templates (NDAs, SAFEs, NVCA docs, employment) as DOCX files. Runs locally from the @open-agreements/contract-templates-mcp npm package.