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/jacob-hartmann/vibeco-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/jacob-hartmann/vibeco-mcp/vibeco-mcp)<a href="https://agentmods.dev/mcp/jacob-hartmann/vibeco-mcp/vibeco-mcp"><img src="https://agentmods.dev/badge/mcp/jacob-hartmann/vibeco-mcp/vibeco-mcp/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/jacob-hartmann/vibeco-mcp/vibeco-mcp"><img src="https://agentmods.dev/badge/mcp/jacob-hartmann/vibeco-mcp/vibeco-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vibeco-mcp 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 11d 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
{ "vibeco-mcp": { "command": "npx", "args": [ "-y", "vibeco-mcp" ] } }
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.
- 11d ago First seen · 9 lines scan A 7c652bd5ddb2
vibeco-mcp is an MCP server published in the GitHub repository jacob-hartmann/vibeco-mcp (1 stars, last pushed 2mo 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
lulu-ads
Self-serve publisher onboarding for Lulu Ads. 70% CPA, disclosed sponsored field. Remote server at ads.getlulu.dev.
mcp-walmart-ads
MCP server for Walmart Connect Ads APIs (Sponsored Search + Display). Runs locally from the mcp-walmart-ads Python package.
mcp-server
Kadam advertising platform — manage ads, campaigns, creatives, audiences and stats. Runs locally from the @kadam-net/mcp-server npm package. Needs 2 environment variables to run.
pinterest-ads
Pinterest Ads: 26 read tools and 5 write tools that preview before they apply. Runs locally from the @getmcpads/pinterest-ads-mcp-server npm package. Needs 6 environment variables to run.
tiktok-ads
TikTok Ads: 27 read tools, 277 metrics, and 5 write tools that preview before applying. Runs locally from the @getmcpads/tiktok-ads-mcp-server npm package. Needs 5 environment variables to run.
agentic-ads
Ad network for AI agents — monetize MCP servers with contextual ads. 70% revenue share. Runs locally from the agentic-ads npm package.