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.
npx agentmods add mcp/matias-denatale/eph-context/eph-contextgit clone --depth 1 https://github.com/matias-denatale/eph-contextWrote 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/matias-denatale/eph-context/eph-context)<a href="https://agentmods.dev/mcp/matias-denatale/eph-context/eph-context"><img src="https://agentmods.dev/badge/mcp/matias-denatale/eph-context/eph-context.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
eph-context 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 3d 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
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 8 lines scan A c5481065df41
eph-context is an MCP server published in the GitHub repository matias-denatale/eph-context (1 stars, last pushed 1mo ago), with no licence file. 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
federal-reserve-mcp-server
Search and fetch 800K Federal Reserve economic time-series from the FRED API via MCP. Runs locally from the @cyanheads/federal-reserve-mcp-server npm package. Needs 5 environment variables to run.
rag-rat
CLI and MCP entrypoint for indexing repositories into local source, graph, history, and memory evidence. Runs locally from the @rag-rat/bin npm package.
neverinfamous-memory-journal-mcp
A MCP server built for developers enabling Git based project management with project and personal… Remote server at server.smithery.ai.
cgr-capture
MCP server that captures agent judgments and outcomes as CGR substrate on GRAFOMEM Cloud. Runs locally from the grafomem-cgr Python package. Needs 6 environment variables to run.
june-mcp
MCP server for Junê — give any MCP agent (Claude Desktop, Claude Code, …) a shared, cited knowledge-graph memory backed by a June endpoint. Runs locally from the june-mcp Python package. Needs 13 environment variables to run.
carsxe-mcp
MCP server for CarsXE vehicle data: VIN, specs, history, images, recalls, and OBD codes. Remote server at mcp.carsxe.com.