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/gsl0001/CortexInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote 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/gsl0001/cortex/cortex)<a href="https://agentmods.dev/mcp/gsl0001/cortex/cortex"><img src="https://agentmods.dev/badge/mcp/gsl0001/cortex/cortex/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/gsl0001/cortex/cortex"><img src="https://agentmods.dev/badge/mcp/gsl0001/cortex/cortex.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade 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 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
{
"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.
- 1mo ago First seen · 13 lines scan A d3d59dab1038
cortex is an MCP server published in the GitHub repository gsl0001/Cortex (12 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
yantrikdb-mcp
YantrikDB — Cognitive memory for AI agents. Persistent semantic recall, knowledge graph, contradiction detection, and procedural learning. Ships as embeddable engine, network database, or MCP server. Runs locally from the yantrikdb-mcp Python package.
yantrikdb
YantrikDB — Cognitive memory for AI agents. Persistent semantic recall, knowledge graph, contradiction detection, and procedural learning. Ships as embeddable engine, network database, or MCP server. Runs locally from the yantrikdb-mcp Python package.
engram
MCP server "engram" as configured in rwnalds/engram. Runs in Docker (ghcr.io/rwnalds/engram:0.1.2).
thought-mcp
THOUGHT — Temporal Hierarchical Object Union & Graph Hybrid Toolkit. A local MCP memory server with bi-temporal graph + vector + temporal layers, a query router, and a consolidation engine. Runs locally from the thought-mcp Python package.
mnemo
MCP server "mnemo" as configured in oyekamal/mnemo-agent. Runs mnemo.mcp_server with ${CLAUDE_PROJECT_DIR:-.}/.venv/bin/python. Needs 1 environment variable to run.
memory-mcp
A python implementation of AI memory in MCP. Runs locally from the memory-mcp Python package.