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/vibestackdev/vibe-stackWrote 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/vibestackdev/vibe-stack/filesystem)<a href="https://agentmods.dev/mcp/vibestackdev/vibe-stack/filesystem"><img src="https://agentmods.dev/badge/mcp/vibestackdev/vibe-stack/filesystem.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
filesystem 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 yesterday.
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.
This is a copy
100% identical to filesystem — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"./"
]
}
}What else mcp.json configures
This page is one entry in a file that holds 4. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- yesterday First seen · 10 lines scan A 422059b53e46
filesystem is an MCP server published in the GitHub repository vibestackdev/vibe-stack (8 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. It is 100% identical to filesystem, differing in 3 lines, and is treated as a copy.
Other mcp servers, from other repositories
guardvibe
Deterministic security layer your AI can't be. 441 rules, 37 tools, CLI + doctor + host audit. Runs locally from the guardvibe npm package.
boilerforge
MCP server "boilerforge" as configured in MRKT365-India/boilerforge. Runs ./dist/mcp-server/index.js with node.
mcp-frontend-analyzer
MCP server "mcp-frontend-analyzer" as configured in Samet-Berkay-Taskin/MCP-Frontend-Analyzer. Runs locally from the mcp-frontend-analyzer npm package.
seo
Spot keyword demand rising or fading. Trend volume and growth signals. Free key at trendsmcp.ai. Remote server at seo.api.trendsmcp.ai.
flashalpha
MCP server "flashalpha", hosted remotely at lab.flashalpha.com, as configured in FlashAlpha-lab/flashalpha-mcp.
sayba-platform
Sayba AI Agent Social Platform MCP Server — 26 tools, 27 skills, 100+ API endpoints (register, post, comment, vote, DM+inbox, notifications, goals, memory, XC wallet, skill market, social, heartbeat, item exchange, agent zone, skill update check). Runs locally from the sayba-platform npm package. Needs 1 environment…