mcpbeat Sign in

VibeVaults MCP Server

by vibe-vaults Your server? Claim it
answering

VibeVaults is answering right now. Last checked 9 min ago.

Read clients' pinned website feedback and, if allowed, reply and set status from your AI tool.

Uptime history 12 days of history
12 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
369 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check VibeVaults every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add vibevaults --transport http https://www.vibe-vaults.com/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://www.vibe-vaults.com/api/mcp
~/.codex/config.toml
[mcp_servers.vibevaults]
url = "https://www.vibe-vaults.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "vibevaults": {
      "url": "https://www.vibe-vaults.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "vibevaults": {
      "type": "http",
      "url": "https://www.vibe-vaults.com/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://www.vibe-vaults.com/api/mcp streamable-http sign-in 512 ms 9 min ago

Alternatives to VibeVaults

same job, measured the same way
Pinthread
by wladefant

Read, reply to and resolve website feedback threads from your coding agent.

answering
Drobber
by drobber

Read, reply to and resolve client feedback pinned on websites, PDFs, images and video.

answering
Ybug
by ybug

Read, filter and triage Ybug website feedback and bug reports from your AI assistant

answering
Huddlekit
by huddlekit

Read client feedback left on your website, with its screenshot and page, then reply and resolve.

answering
Pindicate
by pindicate

Send your work to clients for feedback. Get a review link, then read their pinned comments.

answering
PageProofer
by pageproofer

Read, fix and reply to PageProofer website feedback notes from Claude Code, Cursor and other agents.

answering
AgentMsgr
by agentmsgr

AI group chat for all your agents: read and reply to AgentMsgr chats from any MCP client.

answering
Tyrekick
by richardofortune

Read and resolve human feedback pinned on your live prototype, straight from your coding agent.

77 installs/wk local only

VibeVaults — questions

Answers built from our own checks of this server.

Why is there no tool list for VibeVaults?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is VibeVaults working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 369 ms. The bar chart above shows every period we have measured.
How do I connect VibeVaults?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to VibeVaults?
No API key is involved. VibeVaults answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is VibeVaults?
It answers our handshake in 369 ms on average, which is faster than 36% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.