Home / MCP registry index / io.github.VibeKit-Bot/vibekit-mcp

VibeKit

io.github.VibeKit-Bot/vibekit-mcp in the official MCP registry. Endpoint https://mcp.vibekit.bot/mcp. Source: github.com/VibeKit-Bot/vibekit-mcp.

The registry describes it as: Build, deploy, and operate hosted web apps on VibeKit (vibekit.bot) from any MCP client.

We read its 36 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http vibekit-mcp https://mcp.vibekit.bot/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "vibekit-mcp": {
      "url": "https://mcp.vibekit.bot/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"vibekit-mcp","type":"http","url":"https://mcp.vibekit.bot/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

vibekit_list_apps vibekit_get_app vibekit_create_app vibekit_list_templates vibekit_deploy vibekit_redeploy vibekit_app_logs vibekit_restart_app vibekit_stop_app vibekit_start_app vibekit_app_env vibekit_set_env vibekit_delete_app vibekit_chat vibekit_agent_status vibekit_agent_history vibekit_enable_database vibekit_database_status vibekit_db_schema vibekit_db_query vibekit_db_table vibekit_list_deploys vibekit_rollback_deploy vibekit_run_qa vibekit_qa_status vibekit_submit_task vibekit_get_task vibekit_list_tasks vibekit_wait_for_task vibekit_cancel_task vibekit_create_schedule vibekit_list_schedules vibekit_delete_schedule vibekit_account vibekit_list_skills vibekit_get_skill

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-vibekit-bot-vibekit-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-vibekit-bot-vibekit-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.