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/aphrody-code/bxcWrote 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/aphrody-code/bxc/memory)<a href="https://agentmods.dev/mcp/aphrody-code/bxc/memory"><img src="https://agentmods.dev/badge/mcp/aphrody-code/bxc/memory/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/aphrody-code/bxc/memory"><img src="https://agentmods.dev/badge/mcp/aphrody-code/bxc/memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
memory 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
{
"memory": {
"command": "bunx",
"args": [
"--bun",
"@modelcontextprotocol/server-memory"
]
}
}What else settings.json configures
This page is one entry in a file that holds 3. Installing the file brings all of them; each is measured and scanned on its own page.
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 cb41c06f424b
memory is an MCP server published in the GitHub repository aphrody-code/bxc (3 stars, last pushed 1mo 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-07.
Other mcp servers, from other repositories
ui-debugger-mcp
Autonomous UI debugging MCP server: an agent drives the browser/desktop, reports bugs + UX issues. Runs locally from the @developerz.ai/ui-debugger-mcp npm package. Needs 2 environment variables to run.
sentry-mcp
Lets the agent search and read Sentry issues, errors and traces, and act on them. Runs locally from the @sentry/mcp-server npm package. Needs 2 environment variables to run.
developerz
MCP server "developerz", hosted remotely at mcp.developerz.ai, as configured in developerz-ai/ui-debugger-mcp.
codegraph
MCP server "codegraph" as configured in developerz-ai/ui-debugger-mcp. Launched with codegraph serve --mcp.
browser-gateway
AI browser tools with Chrome CDP. Navigate, screenshot, interact. Multi-provider failover. Runs locally from the browser-gateway npm package. Needs 1 environment variable to run.
scout
MCP server "scout" as configured in klarlabs-studio/scout. Runs in Docker (ghcr.io/klarlabs-studio/scout:1.15.3).