Vibgrate

com.vibgratePublished by vibgrate.comOfficial publisherv2026.921.1Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Vibgrate is a remote MCP server that lets an AI assistant query a team's drift, vulnerability and upgrade data through OAuth-authenticated access.

What you can do
Query the team's drift data from an AI assistant via the hosted endpoint, which exposes 51 tools according to the registry description. Query vulnerability data for the team. Query upgrade data for the team. Access is authenticated with OAuth 2.1, so results are tied to the connected account.
When to use it
Useful when a team already tracks dependency drift, vulnerabilities and upgrades in Vibgrate and wants to ask an AI assistant about that data without leaving the chat. Less relevant if the team does not use Vibgrate or needs local file or code access.
Requirements
A remote MCP endpoint at mcp.vibgrate.com over streamable HTTP, plus an OAuth 2.1 sign-in to a Vibgrate account. No packages, environment variables or headers are declared; network access is required.
Before you install
OAuth grants the assistant access to the team's Vibgrate data, so review the scopes and permissions requested during sign-in. The registry lists 51 tools but does not describe them, so confirm which tools read data and which may change it before relying on them. Data is sent to a third-party hosted service.

Installation

In SourceWeft

  1. Open Vibgrate in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.vibgrate%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "vibgrate": {
      "type": "http",
      "url": "https://mcp.vibgrate.com/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v2026.921.1LatestSep 21, 2026
  2. v2026.915.1Sep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Vibgrate integrations