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/nimelkot/astraWrote 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/nimelkot/astra/astra-code-context)<a href="https://agentmods.dev/mcp/nimelkot/astra/astra-code-context"><img src="https://agentmods.dev/badge/mcp/nimelkot/astra/astra-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/nimelkot/astra/astra-code-context"><img src="https://agentmods.dev/badge/mcp/nimelkot/astra/astra-code-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
astra-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 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
{ "astra-code-context": { "command": "uvx", "args": [ "astra-code-context" ] } }
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 · 8 lines scan A ce984c0394cb
astra-code-context is an MCP server published in the GitHub repository nimelkot/astra (0 stars, last pushed 1mo 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
codestory
MCP server "codestory" as configured in TheGreenCedar/CodeStory. Runs ${workspaceFolder}/plugins/codestory/scripts/codestory-mcp.cjs with node. Needs 1 environment variable to run.
coldstart
Codebase memory for AI agents: an AST index plus agent-written notes that self-stale. Runs locally from the @cstart/coldstart npm package.
codebase-memory-mcp
Codebase knowledge graph for AI agents — 159 languages, sub-ms queries, 99% fewer tokens. Runs locally from the codebase-memory-mcp npm package.
code-index
Rust code index MCP server, native 1C:Enterprise (BSL) support. 32 tools, AST for 14 languages. Runs locally from the @regsorm/code-index-mcp npm package.
codenib
A multi-view data system for serving repository context to coding agents. Runs locally from the codenib Python package.
ariadne
MCP server "ariadne" as configured in CRJFisher/ariadne. Runs ./packages/mcp/dist/cli.js with node. Needs 1 environment variable to run.