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.
npx agentmods add mcp/nerdconf/veta/veta-vetagit clone --depth 1 https://github.com/nerdconf/vetaWrote 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/nerdconf/veta/veta-veta)<a href="https://agentmods.dev/mcp/nerdconf/veta/veta-veta"><img src="https://agentmods.dev/badge/mcp/nerdconf/veta/veta-veta.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
veta 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 4d 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
{
"veta": {
"command": "node",
"args": [
"./scripts/veta-plugin-launcher.mjs"
],
"cwd": "."
}
}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.
- 4d ago First seen · 9 lines scan A b990d16cc2fd
veta is an MCP server published in the GitHub repository nerdconf/veta (0 stars, last pushed 1mo 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
sverklo
MCP server "sverklo" as configured in sverklo/sverklo. Launched with /opt/homebrew/bin/sverklo .. Needs 1 environment variable to run.
local-memory-mcp
Persistent local AI memory. SQLite + FTS5 + vector search, knowledge graph. No cloud, no API keys. Runs locally from the @studiomeyer/local-memory-mcp npm package. Needs 4 environment variables to run.
lians_memory
MCP server "liansmemory" as configured in Lians-ai/Lians. Launched with lians-memory-mcp. Needs 11 environment variables to run.
lians
Correct, temporal, and auditable memory infrastructure for AI agents. Runs locally from the lians-sdk Python package. Needs 5 environment variables to run.
piia-engram
Local-first personal AI identity and memory for MCP-compatible coding tools — lessons, decisions, playbooks, and project context you can see, edit, and override. Runs locally from the piia-engram Python package. Needs 3 environment variables to run.
pathmark
MCP server "pathmark" as configured in hacksurvivor/pathmark. Launched with pathmark. Needs 1 environment variable to run.