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/kostyk348/sint-ua-v2.1Wrote 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/kostyk348/sint-ua-v2.1/sint-memory-mcp)<a href="https://agentmods.dev/mcp/kostyk348/sint-ua-v2.1/sint-memory-mcp"><img src="https://agentmods.dev/badge/mcp/kostyk348/sint-ua-v2.1/sint-memory-mcp/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/kostyk348/sint-ua-v2.1/sint-memory-mcp"><img src="https://agentmods.dev/badge/mcp/kostyk348/sint-ua-v2.1/sint-memory-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sint-memory-mcp 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
{ "sint-memory-mcp": { "command": "uvx", "args": [ "sint-memory-mcp" ] } }
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 d67d0f06910f
sint-memory-mcp is an MCP server published in the GitHub repository kostyk348/sint-ua-v2.1 (0 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-08-31.
Other mcp servers, from other repositories
midas
MCP server for Midas — local-first, source-traceable agent memory with no LLM at ingest. Runs locally from the midas-memory-mcp Python package. Needs 4 environment variables to run.
mnemon-memory
Universal long-term memory layer for AI agents via MCP. Runs locally from the mnemon-memory Python package.
trinity-memory
Trinity v8.2.0: Memory Operating System — Multi-Agent Shared Memory, 50-Layer Guardian Chain, 129-Paper Brain-Inspired Alignment, GraphQL API, Raft Cluster, BM25+Jieba Chinese Retrieval. Runs locally from the trinity-memory Python package.
pensyve
MCP server "pensyve", hosted remotely at mcp.pensyve.com, as configured in major7apps/pensyve.
pensyve
Universal memory runtime for AI agents — episodic, semantic, and procedural memory. Remote server at mcp.pensyve.com.
aimem-mcp
Local-first, project-scoped MCP memory server for AI coding assistants. Runs locally from the aimem-mcp npm package.