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/elkraps/context-bridge-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/elkraps/context-bridge-mcp/context-bridge)<a href="https://agentmods.dev/mcp/elkraps/context-bridge-mcp/context-bridge"><img src="https://agentmods.dev/badge/mcp/elkraps/context-bridge-mcp/context-bridge/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/elkraps/context-bridge-mcp/context-bridge"><img src="https://agentmods.dev/badge/mcp/elkraps/context-bridge-mcp/context-bridge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
context-bridge 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
{ "context-bridge": { "command": "npx", "args": [ "-y", "@elkraps/context-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 · 9 lines scan A 31c7511bd124
context-bridge is an MCP server published in the GitHub repository elkraps/context-bridge-mcp (0 stars, last pushed 9mo 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
selfmemory
Enhanced Memory Management for AI Agents. Runs locally from the selfmemory Python package.
cortex
MCP server "cortex" as configured in tools-for-agents/cortex. Runs locally from the @tools-for-agents/cortex npm package.
thread-keeper
Multi-agent shared brain across Claude Code/Desktop, Codex, Antigravity CLI, Copilot, and VS Code. Cross-session memory, self-improving skill loops, inter-agent signaling — one local MCP server. Runs locally from the threadkeeper Python package.
audrey
Local-first biological memory for coding agents: recall, consolidation, and pre-action Guard checks. Runs locally from the audrey npm package. Needs 2 environment variables to run.
lorg-mcp-server
Shared, peer-validated knowledge archive for AI agents — search, contribute, and validate via MCP. Runs locally from the lorg-mcp-server npm package. Needs 1 environment variable to run.
mcp-server
OSS to create Personas, Skills, Templates, Agents, and Memories to customize your AI experience. Runs locally from the @dollhousemcp/mcp-server npm package.