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/hoangsonww/AI-Agents-OrchestratorWrote 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/hoangsonww/ai-agents-orchestrator/memory)<a href="https://agentmods.dev/mcp/hoangsonww/ai-agents-orchestrator/memory"><img src="https://agentmods.dev/badge/mcp/hoangsonww/ai-agents-orchestrator/memory.svg" alt="Measured on agentmods" 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 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
{
"memory": {
"command": "npx",
"args": [
"-y",
"@anthropic-ai/mcp-memory"
],
"description": "Persistent memory storage for conversation context"
}
}What else .mcp.json configures
This page is one entry in a file that holds 4. 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.
- 8d ago First seen · 10 lines scan A 41297d32c7f8
memory is an MCP server published in the GitHub repository hoangsonww/AI-Agents-Orchestrator (84 stars, last pushed 22d 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-30.
Other mcp servers, from other repositories
context-stream
MCP server "context-stream", hosted remotely at localhost, as configured in thejavapirate/model-context-stream.
claude-flow
Ruflo CLI - Enterprise AI agent orchestration with 60+ specialized agents, swarm coordination, MCP server, self-learning hooks, and vector memory for Claude Code. Runs locally from the @claude-flow/cli npm package. Needs 6 environment variables to run.
vault-cortex
MCP server "vault-cortex" as configured in aliasunder/vault-cortex. Runs in Docker (ghcr.io/aliasunder/vault-cortex:0.45.0). Needs 24 environment variables to run.
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.
contextforge-mcp
Persistent memory MCP server for Claude Code, Cursor, and GitHub Copilot. Runs locally from the contextforge-mcp npm package. Needs 2 environment variables to run.
ctxmem
Git-native, shareable project memory for AI coding agents — fully local, no cloud. Runs locally from the ctxmem Python package.