Vibe Mcp — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Vibe Mcp (Agent Skill) and scored it 92/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 2 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 2 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Message people from Claude Code or Codex.
Presence, DMs, and messages that wait across sessions, between the people (and agents) you already work with — nobody has to be online at the same time.
npx slashvibe-mcpIt configures your coding agent, opens GitHub to sign you in, and your GitHub username becomes your @handle. About 30 seconds. Then restart your coding session so it loads the /vibe server.
show me who's on /vibe
message @brightseth — what are you building?
did anyone message me?No commands to learn. Your coding agent routes those to /vibe. If it ever asks you to sign in, say sign in to /vibe.
Works in: Claude Code and Codex. Setup also writes Cursor's config; Cursor is not part of the walked, proven path yet.
For the small, opt-in Gate 1 pilot, install the read-only Claude Code SessionStart hook:
npx slashvibe-mcp hook installThe hook checks the ordinary inbox when Claude starts or resumes. It writes no read state, delivery claim or receipt, so a waiting message may honestly appear again on another startup during the pilot. Check or reverse the installation at any time:
npx slashvibe-mcp hook status
npx slashvibe-mcp hook uninstallIf you'd rather wire it yourself, add to ~/.claude.json (or your host's MCP config):
{
"mcpServers": {
"vibe": {
"command": "npx",
"args": ["-y", "slashvibe-mcp@latest"],
"env": {
"VIBE_API_URL": "https://www.slashvibe.dev"
}
}
}
}Then run vibe init in your session to sign in.
The default surface is deliberately small — 10 tools:
read-only Claude hook can put a waiting reply at the top of your next session
shipping, debugging)start, init, token, bye)The culture layer (games, poems, exquisite corpse, the weave) still ships but is opt-in: set VIBE_EXTRAS=1 to register all 20 tools.
Once installed, in your coding session:
| Say | Get |
|---|---|
vibe | inbox + who's online |
vibe who | the presence board |
vibe dm @stan "does the seam handle retries?" | a DM that outlives both your sessions |
vibe status shipping | your status, in words |
The server talks to www.slashvibe.dev for presence, message routing, and identity (GitHub OAuth). Protocol compliance is ledgered in PROTOCOL-COMPLIANCE.md.
VibeCodingInc/vibe-mcp) is the source-of-record for theslashvibe-mcp client — the published npm tarball is built and released from here.
MIT
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.