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/hj1105/kontext-brain-tsWrote 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/hj1105/kontext-brain-ts/kontext-brain-kontext_brain)<a href="https://agentmods.dev/mcp/hj1105/kontext-brain-ts/kontext-brain-kontext_brain"><img src="https://agentmods.dev/badge/mcp/hj1105/kontext-brain-ts/kontext-brain-kontext_brain/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/hj1105/kontext-brain-ts/kontext-brain-kontext_brain"><img src="https://agentmods.dev/badge/mcp/hj1105/kontext-brain-ts/kontext-brain-kontext_brain.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
kontext_brain 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 8d 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
{
"kontext_brain": {
"command": "node",
"args": [
"./server.mjs"
],
"cwd": ".",
"env_vars": [
"HOME",
"USERPROFILE",
"LOCALAPPDATA",
"APPDATA",
"XDG_DATA_HOME",
"KONTEXT_PLUGIN_DATA"
],
"startup_timeout_sec": 10,
"tool_timeout_sec": 60
}
}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.
- 8d ago First seen · 19 lines scan A 189b20a56016
kontext_brain is an MCP server published in the GitHub repository hj1105/kontext-brain-ts (26 stars, last pushed 2d ago), 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-09-04.
Other mcp servers, from other repositories
fortemi
MCP server "fortemi" as configured in Fortemi/fortemi. Runs ./mcp-server/index.js with node. Needs 2 environment variables to run.
remnic
MCP server "remnic", hosted remotely at localhost, as configured in joshuaswarren/remnic.
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.
veritasgraph
The first zero-trust, air-gapped Enterprise GraphRAG server for the Model Context Protocol (MCP). Runs locally from the veritasgraph-mcp Python package. Needs 3 environment variables to run.
mcp-neo4j-knowledge-graph
Neo4j-based knowledge graph MCP server with temporal versioning and semantic search. Runs locally from the @henrychong-ai/mcp-neo4j-knowledge-graph npm package.
multi-agent-memory
MCP server "multi-agent-memory" as configured in jhunter11/multi-agent-memory-MCP. Launched with __NODE_EXECUTABLE__ __SERVER_ENTRYPOINT__. Needs 1 environment variable to run.