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/turfptax/cortex-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/turfptax/cortex-mcp/cortex-mcp)<a href="https://agentmods.dev/mcp/turfptax/cortex-mcp/cortex-mcp"><img src="https://agentmods.dev/badge/mcp/turfptax/cortex-mcp/cortex-mcp/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/turfptax/cortex-mcp/cortex-mcp"><img src="https://agentmods.dev/badge/mcp/turfptax/cortex-mcp/cortex-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cortex-mcp 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.
This is a copy
100% identical to cortex-mcp — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{ "cortex-mcp": { "command": "uvx", "args": [ "cortex-mcp" ] } }
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 3bcb57b1539c
cortex-mcp is an MCP server published in the GitHub repository turfptax/cortex-mcp (0 stars, last pushed 4mo 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. It is 100% identical to cortex-mcp, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
myaitwin
A personal RAG database you build from chat, so AI creates work that sounds like you. Remote server at myaitwin.lutolearn.com.
prism-coder
Session memory for coding agents: local-first recall, drift detection, on-device inference. Runs locally from the prism-mcp-server npm package. Needs 8 environment variables to run.
prism-mcp
Persistent session memory for AI coding agents that never leaves your machine — including the on-device model that reasons over it. Restores your prior decisions, open TODOs, and changed files across sessions; adds associative recall of related past work. Runs locally from the prism-mcp-server npm package. Needs 1…
hypermnesia-mcp
Scientifically-grounded memory system based on computational neuroscience research. Runs locally from the hypermnesia-mcp Python package.
ninjaone-mcp
MCP server "ninjaone-mcp" as configured in WYRE-AI/ninjaone-mcp. Runs in Docker (ghcr.io/wyre-ai/ninjaone-mcp:v2.3.2). Needs 6 environment variables to run.
state-memory-mcp
MCP server "state-memory-mcp" as configured in putervision/state-memory-mcp. Launched with state-memory-mcp run.