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/EtanHey/brainlayerInstalling this writes the configuration, not the program: `brainlayer-mcp-stdio-bridge` has to be on your PATH already, or the server will not start.
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/etanhey/brainlayer/brainlayer-plugin-brainlayer)<a href="https://agentmods.dev/mcp/etanhey/brainlayer/brainlayer-plugin-brainlayer"><img src="https://agentmods.dev/badge/mcp/etanhey/brainlayer/brainlayer-plugin-brainlayer/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/etanhey/brainlayer/brainlayer-plugin-brainlayer"><img src="https://agentmods.dev/badge/mcp/etanhey/brainlayer/brainlayer-plugin-brainlayer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
brainlayer 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
{
"brainlayer": {
"command": "brainlayer-mcp-stdio-bridge"
}
}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 · 5 lines scan A 27885ac081fc
brainlayer is an MCP server published in the GitHub repository EtanHey/brainlayer (9 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
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.
vscode-warnerco-schematica
MCP server "vscode-warnerco-schematica" as configured in timothywarner-org/context-engineering. Runs locally from the warnerco-mcp Python package. Needs 1 environment variable to run.
ghcopilot-warner
GitHub's hosted MCP server: lets the agent search code, read and create issues and pull requests. Remote server at api.githubcopilot.com.
keymem
Associative memory for LLM agents — a key-graph memory layer (MCP server) that recalls by association, not just vector similarity. A graph-based alternative to vector-store agent memory. Runs locally from the keymem npm package. Needs 3 environment variables to run.
distillory
MCP server "distillory" as configured in everyai-com/distillory. Runs locally from the distillory Python package.