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/yantrikos/yantrikdb-mcpWrote 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/yantrikos/yantrikdb-mcp/yantrikdb)<a href="https://agentmods.dev/mcp/yantrikos/yantrikdb-mcp/yantrikdb"><img src="https://agentmods.dev/badge/mcp/yantrikos/yantrikdb-mcp/yantrikdb/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/yantrikos/yantrikdb-mcp/yantrikdb"><img src="https://agentmods.dev/badge/mcp/yantrikos/yantrikdb-mcp/yantrikdb.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
yantrikdb 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 27d 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
{
"yantrikdb": {
"command": "uvx",
"args": [
"yantrikdb-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.
- 27d ago First seen · 8 lines scan A 5f5b9f31c3ed
yantrikdb is an MCP server published in the GitHub repository yantrikos/yantrikdb-mcp (25 stars, last pushed today), 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-09-20.
Other mcp servers, from other repositories
titen-memory
Evidence-grounded agent memory with mandatory provenance, on local SQLite or Cloudflare D1. Runs locally from the titen-memory npm package. Needs 2 environment variables to run.
myco-brain
Self-hosted, source-traceable memory layer and MCP server for AI agents, on your own Postgres. Runs locally from the @mycobrain/mcp-server npm package.
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.
palinode
MCP server "palinode" as configured in phasespace-labs/palinode. Launched with palinode-mcp.
acmi-mcp
Persistent agent memory via ACMI — Profile/Signals/Timeline. 16 tools on Upstash Redis. Runs locally from the @madezmedia/acmi-mcp npm package. Needs 2 environment variables to run.
keymem
Associative memory for LLM agents — a key-graph memory layer (MCP server) that recalls by association, not just vector similarity. A graph-based alternative to vector-store agent memory. Runs locally from the keymem npm package. Needs 3 environment variables to run.