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/sourikduttanyu/astralWrote 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/sourikduttanyu/astral/astral-recall)<a href="https://agentmods.dev/mcp/sourikduttanyu/astral/astral-recall"><img src="https://agentmods.dev/badge/mcp/sourikduttanyu/astral/astral-recall/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/sourikduttanyu/astral/astral-recall"><img src="https://agentmods.dev/badge/mcp/sourikduttanyu/astral/astral-recall.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
astral-recall 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 10d 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
{
"astral-recall": {
"command": "python3",
"args": [
"servers/astral_recall_mcp.py"
]
}
}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.
- 10d ago First seen · 8 lines scan A f896283853c2
astral-recall is an MCP server published in the GitHub repository sourikduttanyu/astral (1 stars, last pushed 2mo 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
furl
MCP server "furl" as configured in omar-y-abdi/furl-ctx. Launched with sh -c PATH="$PATH:$HOME/.local/bin:$HOME/.cargo/bin:/opt/homebrew/bin:/usr/local. Needs 3 environment variables to run.
context-sync
Universal AI Memory - Sync context across Claude, VsCode, Cursor, Continue, Windsurf, Zed & more. Runs locally from the @context-sync/server npm package.
mcp-working-context-optimizer
MCP server "mcp-working-context-optimizer" as configured in globalpocket/mcp-working-context-optimizer. Runs locally from the mcp-working-context-optimizer Python package.
context-router
MCP server "context-router" as configured in mohankrishnaalavala/context-router. Launched with context-router mcp.
ruflo
MCP server "ruflo" as configured in martineserios/thebrana. Launched with ${HOME}/enter_thebrana/thebrana/system/scripts/ruflo-mcp.sh mcp start. Needs 1 environment variable to run.
hypermnesia-mcp-viz
Visualization and graph MCP server for Cortex — neural graph, methodology map, workflow graph, and trace UI extracted from the Cortex memory engine. Runs locally from the hypermnesia-mcp-viz Python package.