mcpbeat Sign in

Vibgrate MCP Server

answering

Vibgrate is answering right now. Last checked 6 min ago.

Query your team's drift, vulnerability, and upgrade data from any AI assistant. OAuth 2.1, 51 tools.

Uptime history 47 days of history
47 days agonow
100.0%
Uptime 24h
92 of 92 checks
Tools
hidden behind auth
217 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Vibgrate 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 6 min ago.

run in your terminal
claude mcp add mcp --transport http https://mcp.vibgrate.com
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.vibgrate.com"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.vibgrate.com"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.vibgrate.com"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.vibgrate.com"
    }
  }
}

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://mcp.vibgrate.com streamable-http sign-in 184 ms 6 min ago

Alternatives to Vibgrate

same job, measured the same way
mytesla.io
by mytesla

Control your Tesla from your AI assistant - climate, charging, access, and security.

answering
nvd
by pipeworx-io

NVD MCP — wraps the NIST National Vulnerability Database API (free, no auth)

39 tools answering
Fetter MCP
by fetter-io

Real-time Python package and vulnerability data for AI coding agents.

3 tools answering
middleBrick
by middlebrick

Scan APIs for OWASP Top 10, LLM, and GraphQL security vulnerabilities.

24 installs/wk local only
SiteVitals
by tom18a

Monitor website health, uptime, SEO, security and performance via your AI assistant.

answering
Action1 MCP
by servosity

Every Action1 endpoint, plus fleet-wide patch and vulnerability views across all your organizations.

local only
Mem
by mem-labs

Securely search, create, and organize your Mem notes and collections from AI assistants.

answering
ScriptDocs MCP
by timwal78

Real, live npm/PyPI docs and OSV.dev vulnerability data for AI coding agents. No fake data.

32 installs/wk local only

Vibgrate — questions

Answers built from our own checks of this server.

Why is there no tool list for Vibgrate?
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 Vibgrate working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 217 ms. The bar chart above shows every period we have measured.
How do I connect Vibgrate?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path 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 Vibgrate?
No API key is involved. Vibgrate 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 Vibgrate?
It answers our handshake in 217 ms on average, which is faster than 63% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.