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/astandrik/local-ydb-toolkitWrote 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/astandrik/local-ydb-toolkit/local-ydb)<a href="https://agentmods.dev/mcp/astandrik/local-ydb-toolkit/local-ydb"><img src="https://agentmods.dev/badge/mcp/astandrik/local-ydb-toolkit/local-ydb/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/astandrik/local-ydb-toolkit/local-ydb"><img src="https://agentmods.dev/badge/mcp/astandrik/local-ydb-toolkit/local-ydb.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
local-ydb 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
{
"local-ydb": {
"command": "npx",
"args": [
"--yes",
"@astandrik/[email protected]"
]
}
}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 · 9 lines scan A 6a87f297fdc4
local-ydb is an MCP server published in the GitHub repository astandrik/local-ydb-toolkit (4 stars, last pushed yesterday), 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
chromadb-remote-mcp
MCP server "chromadb-remote-mcp" as configured in meloncafe/chromadb-remote-mcp. Runs in Docker (devsaurus/chromadb-remote-mcp:latest). Needs 2 environment variables to run.
mad-mcp-qdrant
MCP server for retrieving context from a Qdrant vector database. Runs locally from the mad-mcp-qdrant Python package.
sap-hana-mcp-server
MCP server "sap-hana-mcp-server" as configured in Elkhn/sap-hana-mcp. Runs locally from the sap-hana-mcp-server Python package.
sqlite_server
MCP server "sqliteserver" as configured in santos-404/mcp-server.sqlite. Runs locally from the sqlite_server npm package.
mssql-mcp-server
A Model Context Protocol (MCP) server that enables secure interaction with MSSQL databases. This server allows AI assistants to list tables, read data, and execute SQL queries through a controlled interface, making database exploration and analysis safer and more structured. Runs locally from the mssql-mcp-server…
postgres
PostgreSQL Tuning and Analysis Tool. Runs locally from the postgres-mcp Python package. Needs 1 environment variable to run.