Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add JSungMin/vs-token-safer/plugin install vs-token-saferWrote 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/jsungmin/vs-token-safer/vs-search)<a href="https://agentmods.dev/mcp/jsungmin/vs-token-safer/vs-search"><img src="https://agentmods.dev/badge/mcp/jsungmin/vs-token-safer/vs-search/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/jsungmin/vs-token-safer/vs-search"><img src="https://agentmods.dev/badge/mcp/jsungmin/vs-token-safer/vs-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vs-search 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 9d 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- dase — 86% identical, 4 lines differ
- counterpoint — 80% identical, 4 lines differ
- videomemory — 78% identical, 4 lines differ
What it actually says
{
"vs-search": {
"command": "node",
"args": [
"${CLAUDE_PLUGIN_ROOT}/server/index.js"
]
}
}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.
- 9d ago First seen · 8 lines scan A 00c2ba86734e
vs-search is an MCP server published in the GitHub repository JSungMin/vs-token-safer (11 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-30.
Other mcp servers, from other repositories
code-index
Rust code index MCP server, native 1C:Enterprise (BSL) support. 32 tools, AST for 14 languages. Runs locally from the @regsorm/code-index-mcp npm package.
sverklo
MCP server "sverklo" as configured in sverklo/sverklo. Launched with /opt/homebrew/bin/sverklo .. Needs 1 environment variable to run.
sqry
MCP server "sqry" as configured in verivus-oss/sqry. Runs in Docker (ghcr.io/verivus-oss/sqry:4.8.16).
ivygrep
MCP server "ivygrep" as configured in bvolpato/ivygrep. Launched with https://github.com/bvolpato/ivygrep/releases/download/v1.2.9/ivygrep-mcp-v1.2.9..
ivygrep
MCP server "ivygrep" as configured in bvolpato/ivygrep. Launched with ig --mcp.
stellaris-mcp
MCP server "stellaris-mcp" as configured in GDM-Pixel/stellaris-code-search. Runs locally from the stellaris-mcp npm package.