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/ssmurfgg04-gif/context-mWrote 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/ssmurfgg04-gif/context-m/cortexm)<a href="https://agentmods.dev/mcp/ssmurfgg04-gif/context-m/cortexm"><img src="https://agentmods.dev/badge/mcp/ssmurfgg04-gif/context-m/cortexm.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
cortexm 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 6d 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
{ "cortexm": { "command": "uvx", "args": [ "cortexm" ] } }
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.
- 6d ago First seen · 8 lines scan A 15f845786f61
cortexm is an MCP server published in the GitHub repository ssmurfgg04-gif/context-m (1 stars, last pushed today), licensed Apache-2.0. 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
halomem
MCP server "halomem", hosted remotely, as configured in halofyai/halofy.
titen-memory
Evidence-grounded agent memory with mandatory provenance, on local SQLite or Cloudflare D1. Runs locally from the titen-memory npm package. Needs 2 environment variables to run.
memseek
MCP server "memseek", hosted remotely, as configured in memseekai/memseek.
remem-mcp
Local-first memory for AI coding agents. Memory + CodeGraph + Wiki in one SQLite file. Runs locally from the remem-mcp npm package.
memharness
Bi-temporal, provenance-carrying long-term memory for AI agents, in one SQLite file. Runs locally from the @memharness/mcp npm package. Needs 1 environment variable to run.
snipara
Hosted MCP for source-backed project context, memory, code impact, and agent workflow continuity. Remote server at api.snipara.com.