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.
npx agentmods add mcp/gsl0001/cortex/cortexgit clone --depth 1 https://github.com/gsl0001/CortexGrade A, and why
cortex 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 yesterday.
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
{
"cortex": {
"command": "node",
"args": [
"src/mcp.js"
],
"env": {
"CORTEX_URL": "http://127.0.0.1:4317",
"CORTEX_TOKEN": "${CORTEX_TOKEN}",
"CORTEX_AGENT": "claude-code"
}
}
}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.
- yesterday First seen · 13 lines scan A d3d59dab1038
cortex is an MCP server published in the GitHub repository gsl0001/Cortex (3 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
graymatter
MCP server "graymatter" as configured in angelnicolasc/graymatter. Launched with graymatter mcp serve.
palinode
MCP server "palinode" as configured in phasespace-labs/palinode. Launched with palinode-mcp.
memex
Temporal engineering context for agents via MCP. Runs locally from the stifler-memex-mcp npm package. Needs 4 environment variables to run.
reelier
Agents make claims, Reelier writes receipts - record an agent workflow once, replay it deterministically at 0 tokens, and get an asserted receipt on every run. Runs locally from the reelier npm package.
memini
MCP server "memini", hosted remotely, as configured in eleboucher/memini.
hive-mind
MCP server "hive-mind" as configured in toml0006/hive-mind. Runs locally from the hive-mind Python package.