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/MUSE-CODE-SPACE/vibe-coding-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/muse-code-space/vibe-coding-mcp/vibe-coding)<a href="https://agentmods.dev/mcp/muse-code-space/vibe-coding-mcp/vibe-coding"><img src="https://agentmods.dev/badge/mcp/muse-code-space/vibe-coding-mcp/vibe-coding/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/muse-code-space/vibe-coding-mcp/vibe-coding"><img src="https://agentmods.dev/badge/mcp/muse-code-space/vibe-coding-mcp/vibe-coding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vibe-coding 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 1mo 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
{
"vibe-coding": {
"command": "npx",
"args": [
"-y",
"vibe-coding-mcp"
],
"env": {}
}
}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.
- 1mo ago First seen · 10 lines scan A 8636c19ad261
vibe-coding is an MCP server published in the GitHub repository MUSE-CODE-SPACE/vibe-coding-mcp (1 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
papi
MCP server "papi", hosted remotely at mcp.getpapi.ai, as configured in getpapi/papi.
twitterapi-io-mcp
Offline access to TwitterAPI.io docs for AI assistants. 67 endpoints, 32 pages, 24 blog posts. Runs locally from the twitterapi-io-mcp npm package.
mcp
Architecture docs and patterns for NestJS + Nuxt full-stack apps. Remote server at mcp.cleanslice.org.
fonto-docs
Fonto (FontoXML) documentation for AI tools. Converts DITA XML to Markdown on demand. Remote server at fonto-docs.elliat.nl.
agentdocs-mcp
MCP server for AgentDocs (agentdocs.eu): read, search, write, comment on & share Markdown docs. Runs locally from the agentdocs-mcp npm package. Needs 2 environment variables to run.
codebase-context
MCP server "codebase-context", hosted remotely at 127.0.0.1, as configured in PatrickSys/codebase-context.