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/FilippoPilo/cortex-connectorWrote 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/filippopilo/cortex-connector/cortex)<a href="https://agentmods.dev/mcp/filippopilo/cortex-connector/cortex"><img src="https://agentmods.dev/badge/mcp/filippopilo/cortex-connector/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/filippopilo/cortex-connector/cortex"><img src="https://agentmods.dev/badge/mcp/filippopilo/cortex-connector/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": {
"url": "https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp",
"type": "streamable-http"
}
}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 · 6 lines scan A ba6c9c4f4a0d
cortex is an MCP server published in the GitHub repository FilippoPilo/cortex-connector (1 stars, last pushed 19d 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
alice
Alice: the continuity layer for AI agents. Local-first memory with provenance, open loops, resumption, and review-governed writes. Runs locally from the alice-memory Python package.
usrcp
Encrypted local ledger of structured user state, shared across every MCP-aware AI tool. Runs locally from the usrcp npm package. Needs 1 environment variable to run.
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.
ai-memory
MCP server "ai-memory" as configured in alphaonedev/ai-memory-mcp. Runs in Docker (ghcr.io/alphaonedev/ai-memory:0.5.1). Needs 1 environment variable to run.
mcp-memory-server
Hosted memory for AI agents that learns from outcomes — one key across Claude, Cursor & ChatGPT. Runs locally from the @mnemoverse/mcp-memory-server npm package. Needs 2 environment variables to run.
perenna
A lightweight, Git-backed permanent memory for AI agents. Runs locally from the perenna Python package. Needs 4 environment variables to run.