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/infino-ai/code-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/infino-ai/code-context/code-context)<a href="https://agentmods.dev/mcp/infino-ai/code-context/code-context"><img src="https://agentmods.dev/badge/mcp/infino-ai/code-context/code-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/infino-ai/code-context/code-context"><img src="https://agentmods.dev/badge/mcp/infino-ai/code-context/code-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
code-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 28d 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
{
"code-context": {
"command": "npx",
"args": [
"-y",
"@infino-ai/[email protected]",
"mcp"
],
"alwaysLoad": true
}
}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.
- 28d ago Changed ff3a4bee9c7a
- 1mo ago Changed 65f4ce110572
- 1mo ago First seen · 11 lines scan A 8d9140e7acbf
code-context is an MCP server published in the GitHub repository infino-ai/code-context (31 stars, last pushed 25d 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-30.
Other mcp servers, from other repositories
codenib
A multi-view data system for serving repository context to coding agents. Runs locally from the codenib Python package.
ivygrep
MCP server "ivygrep" as configured in bvolpato/ivygrep. Launched with ig --mcp.
agents-docs
Local markdown docsets with header-aware BM25 search via CLI and MCP. Runs locally from the agents-docs Python package.
shelfmark-rag
Local hybrid retrieval (BM25 + embeddings + RRF) for agent memory and codebases — one SQLite file, MCP server included. Runs locally from the shelfmark-rag Python package.
llm-provider-mcp
MCP server "llm-provider-mcp" as configured in manishiitg/llm-provider-mcp. Launched with https://github.com/manishiitg/llm-provider-mcp/releases/download/v0.7.3/llm-prov.
memgrep
MCP server "memgrep" as configured in gitwork-oss/memgrep. Launched with ${userHome}/.nvm/versions/node/v20.20.2/bin/memgrep serve.