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/pooriaarab/vibedatingWrote 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/pooriaarab/vibedating/vibedate)<a href="https://agentmods.dev/mcp/pooriaarab/vibedating/vibedate"><img src="https://agentmods.dev/badge/mcp/pooriaarab/vibedating/vibedate/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/pooriaarab/vibedating/vibedate"><img src="https://agentmods.dev/badge/mcp/pooriaarab/vibedating/vibedate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vibedate 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
{
"vibedate": {
"command": "npx",
"args": [
"-y",
"vibedate",
"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.
- 1mo ago First seen · 10 lines scan A 94ec8abe3800
vibedate is an MCP server published in the GitHub repository pooriaarab/vibedating (0 stars, last pushed 2d 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
vibelive
Multiplayer for agentic coding terminals — shared Claude Code/Codex/Gemini sessions with live cursors, presence, and in-terminal chat. Local-first, e2e, self-hostable relay. Runs locally from the vibelive npm package.
viberadio-fm
Your agent's output as audio — spoken narration, monologue, two-host podcast, or reactive music. For Claude Code, Codex, Gemini, and other agentic CLIs. Local-first. Runs locally from the viberadio-fm npm package.
vibeshare-live
Share your live agent coding session by URL — spectate read-only or invite into the session. Local-first: runs on your machine, nothing readable leaves without consent. Part of the Vibe Suite. Runs locally from the vibeshare-live npm package.
vibemovie
Your agent coding session as a short recap video — Hyperframes (HTML/CSS/JS) with zero gen-video keys, or your own video model. For Claude Code, Codex, Gemini, and other agentic CLIs. Local-first. Runs locally from the vibemovie npm package.
pare-test
Pare Test ג€” Auto-detects test framework (pytest, jest, vitest, mocha), returns typed JSON. Runs locally from the @paretools/test npm package.
woven
MCP server "woven" as configured in Ducksss/LifeHack-2026. Runs ./node_modules/tsx/dist/cli.mjs with node. Needs 2 environment variables to run.