Developer · Remote MCP server
vibgrate.com
Query your team's drift, vulnerability, and upgrade data from any AI assistant. OAuth 2.1, 51 tools.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.vibgrate/mcp- Version
- 2026.921.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-21
- Updated
- 2026-09-21
- Publisher
- com.vibgrate · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via the domain vibgrate.com · how
- Website
- vibgrate.com/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.vibgrate.com | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect vibgrate.com
vibgrate.com is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.vibgrate.com, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from com.vibgrate
| Server | Runs |
|---|---|
| Ai ContextLocal-first MCP server: version-correct library docs, code map, and offline drift for your repo. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| Vibescan MCP ServerMCP server for VibeScan - scan projects for leaked secrets and security issues. | Local · stdio |
| Vibeshare LiveShare a live agent coding session by URL. Spectate or invite in. | Local · stdio |
| VibesharingDeploy prototypes and collect team feedback from Claude Code, Cursor, or any MCP client. | Local · stdio |
| VibeViewDrive cloud iOS, Android, Apple TV, Android TV and Roku devices to verify app changes. | Local · stdio |
| Vibie MCPDeploy HTML folders to vibie.page from Claude / Cursor - one-line install, OAuth, auto-update. | Local · stdio |
| VidinTurn a screen recording into agent-readable annotated keyframes. MCP server + CLI on ffmpeg. | Local · stdio |
| ViewportWitness by Apex LabsAgent website testing: browser QA, visual regression, Markdown extraction, and security checks. | Remote · HTTPLive check: ✓ handshake |
| VigíaWhat breaks between versions, per-version vulnerabilities, compatible versions: npm/PyPI facts. | Remote · HTTPLive check: ✓ handshake |