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/norton77930/corpus-ingest-coreWrote 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/norton77930/corpus-ingest-core/mcp-corpus-ingest-core)<a href="https://agentmods.dev/mcp/norton77930/corpus-ingest-core/mcp-corpus-ingest-core"><img src="https://agentmods.dev/badge/mcp/norton77930/corpus-ingest-core/mcp-corpus-ingest-core/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/norton77930/corpus-ingest-core/mcp-corpus-ingest-core"><img src="https://agentmods.dev/badge/mcp/norton77930/corpus-ingest-core/mcp-corpus-ingest-core.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
corpus-ingest-core 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 11d 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
{
"corpus-ingest-core": {
"command": "corpus-ingest-mcp",
"args": [],
"cwd": "/absolute/path/to/your/corpus-workspace",
"env": {
"CORPUS_INGEST_DATA_DIR": "/absolute/path/to/your/corpus-workspace/data",
"CORPUS_INGEST_CONFIG": "/absolute/path/to/your/corpus-workspace/config/podcasts.yaml"
}
}
}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.
- 11d ago First seen · 11 lines scan A 9ac0197ae392
corpus-ingest-core is an MCP server published in the GitHub repository norton77930/corpus-ingest-core (2 stars, last pushed 11d 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
beever-atlas
MCP server "beever-atlas" as configured in Beever-AI/beever-atlas. Runs beever_atlas.api.mcp_server with python.
hexis
Git-backed platform for skills, tools, and context for AI agents. Remote server at demo.bevel.software.
mb
MCP server for MindBase — query and write to your wiki from Claude Desktop, Cursor, Windsurf, Cline, or any MCP-compatible AI client. Runs locally from the mindbase-mcp npm package.
gnosis
MCP server "gnosis" as configured in nicholasglazer/gnosis-mcp. Launched with gnosis-mcp serve.
sill-ensoul
MCP server "sill-ensoul" as configured in sillogic/sill-ensoul. Runs locally from the sill-ensoul Python package.
llm-wiki
MCP server "llm-wiki" as configured in cobusgreyling/llm-wiki. Runs llm_wiki.mcp_server with python. Needs 1 environment variable to run.