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/Regsorm/code-index-mcpWrote 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/regsorm/code-index-mcp/code-index)<a href="https://agentmods.dev/mcp/regsorm/code-index-mcp/code-index"><img src="https://agentmods.dev/badge/mcp/regsorm/code-index-mcp/code-index/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/regsorm/code-index-mcp/code-index"><img src="https://agentmods.dev/badge/mcp/regsorm/code-index-mcp/code-index.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
code-index 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
{
"code-index": {
"command": "npx",
"args": [
"-y",
"@regsorm/code-index-mcp"
],
"env": {}
}
}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 · 10 lines scan A 01d9eae3230e
code-index is an MCP server published in the GitHub repository Regsorm/code-index-mcp (148 stars, last pushed 2d 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-30.
Other mcp servers, from other repositories
mcp-1c-platform-tools
An MCP server for 1C Platform Tools. MCP is a standard that lets coding agents call tools, while this server connects those calls to a local 1C extension through IPC, a local process-to-process connection.
sqry
MCP server "sqry" as configured in verivus-oss/sqry. Launched with sqry-mcp --no-daemon. Needs 1 environment variable to run.
codemap
MCP server "codemap" as configured in stainless-code/codemap. Launched with bun src/index.ts mcp --watch --root ${workspaceFolder}.
stellaris-mcp
MCP server "stellaris-mcp" as configured in GDM-Pixel/stellaris-code-search. Runs locally from the stellaris-mcp npm package.
sensegrep
Semantic + structural code search MCP server for AI-native development. Runs locally from the @sensegrep/mcp npm package. Needs 3 environment variables to run.
parecode
Token-aware ripgrep code search and atomic multi-file edits for coding agents. Runs locally from the parecode npm package.