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/Supa-Media/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/supa-media/context/context-context)<a href="https://agentmods.dev/mcp/supa-media/context/context-context"><img src="https://agentmods.dev/badge/mcp/supa-media/context/context-context/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/supa-media/context/context-context"><img src="https://agentmods.dev/badge/mcp/supa-media/context/context-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
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 20d 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
{
"context": {
"type": "http",
"url": "https://mcp.context.lc/mcp"
}
}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.
- 20d ago First seen · 6 lines scan A 201a806fbe9e
context is an MCP server published in the GitHub repository Supa-Media/context (3 stars, last pushed today), 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-09-26.
Other mcp servers, from other repositories
mcp
Owned, portable working memory: a plain-files markdown brain any model can read and cite. Runs locally from the @br8n/mcp npm package.
link
MCP server for Link local agent memory — remember, recall, search, context, and graph traversal. Runs locally from the link-mcp Python package.
markdown-vault-mcp
Generic markdown vault MCP with hybrid search. Runs locally from the markdown-vault-mcp Python package. Needs 89 environment variables to run.
NOUZ-MCP
MCP server for Obsidian — semantic knowledge graph with auto-classification, DAG hierarchy, and cross-domain bridge detection. Runs locally from the nouz-mcp Python package. Needs 8 environment variables to run.
caelune-mcp
MCP server "caelune-mcp" as configured in EllisMorrow/Caelune. Launched with https://github.com/EllisMorrow/Caelune/releases/download/v0.5.6/caelune-mcp-win-.
LINZA-MCP
Local-first MCP sidecar for agent workspaces, artifacts, review intents, and context export. Runs locally from the linza-mcp Python package. Needs 9 environment variables to run.