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/ussdeveloper/memory-starWrote 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/ussdeveloper/memory-star/memorystar)<a href="https://agentmods.dev/mcp/ussdeveloper/memory-star/memorystar"><img src="https://agentmods.dev/badge/mcp/ussdeveloper/memory-star/memorystar/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/ussdeveloper/memory-star/memorystar"><img src="https://agentmods.dev/badge/mcp/ussdeveloper/memory-star/memorystar.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
memorystar 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
{ "memorystar": { "command": "uvx", "args": [ "memorystar" ] } }
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 · 8 lines scan A acea8adf20d4
memorystar is an MCP server published in the GitHub repository ussdeveloper/memory-star (0 stars, last pushed 3mo 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
recall
Open-source agent-memory MCP server. recall.works. Runs locally from the ai-recallworks Python package.
pinrag
A powerful RAG (Retrieval-Augmented Generation) system built with LangChain, designed as an MCP server for Cursor, VS Code, and other AI assistants. Runs locally from the pinrag Python package. Needs 3 environment variables to run.
local-mcp-server
Local MCP Server. Runs locally from the local-mcp-server Python package.
x-use
Browser-native AI agents for X (Twitter): multi-account, MCP-ready, no API keys required. Runs locally from the x-use-mcp Python package. Needs 2 environment variables to run.
seo
Spot keyword demand rising or fading. Trend volume and growth signals. Free key at trendsmcp.ai. Remote server at seo.api.trendsmcp.ai.
sportscore-mcp
Live scores, standings, top scorers, brackets for football, basketball, cricket, tennis. Free API. Runs locally from the sportscore-mcp npm package. Needs 2 environment variables to run.