Can I Vibe? MCP

An MCP server that provides real-time status and health checks for various AI coding providers such as Claude, Cursor, Copilot, and others. It allows agents to query current availability, 90-day uptime history, and incident timelines via tools like ai_provider_status and check_provider_health.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Vendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-07Operated by Can I Vibe?

MCP endpoint (Streamable HTTP)

https://canivibe.ai/mcp

Vendor documentation

What its tools do

2 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

2 of 2 have a description · 0 of 2 declare behavior hints · 2 of 2 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

Passed Endpoint answered the live check · Nov 7, 2026, 8:43 AM UTC
Passed Official MCP Registry namespace is tied to canivibe.ai · Nov 7, 2026, 6:23 AM UTC
Passed Endpoint is on the registry namespace domain · Nov 7, 2026, 6:23 AM UTC
Availability 1 of 1 checks passed in 30 days

What you can do with it

Check if an AI provider is currently down
Verify health status for CI pipelines
Retrieve 90-day uptime history
Get incident timelines for providers

Source and maintenance

Vendor evidenceRegistry 1.0.0

mcp-registry: ai.canivibe/status@1.0.0 Project website

Protocol and capabilities

Server: canivibe 1.0.0
MCP protocol negotiated in check: 2025-06-18
Tools: 2 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Live availability for AI coding providers. Use check_provider_health before work that depends on a provider; use ai_provider_status for details.

Tools

2 advertised

ai_provider_status

Advertised by the server during the last successful anonymous check.

Get the live status of AI coding providers (Claude, OpenAI, Copilot, Cursor, OpenRouter and more). Returns status, how long each provider has been in its current state, and last check time. Pass service_id for one provider, omit it for all.

ai_provider_status input schema

{
  "type": "object",
  "properties": {
    "service_id": {
      "type": "string",
      "description": "Optional provider id, e.g. claude, openai, github_copilot, cursor, openrouter"
    }
  }
}

check_provider_health

Advertised by the server during the last successful anonymous check.

Check whether one or more AI coding providers are healthy enough to use right now. Returns healthy=true only when every requested provider is operational (or within the allowed statuses). Use this before starting work that depends on a provider, or to decide which provider to route to.

check_provider_health input schema

{
  "type": "object",
  "required": [
    "services"
  ],
  "properties": {
    "services": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Provider ids to check, e.g. [\"claude\", \"openrouter\"]"
    },
    "allow_degraded": {
      "type": "boolean",
      "description": "Treat degraded performance as healthy (default false)"
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 651 ms
95th percentile latency: 651 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 7, 2026, 8:43 AM UTC · probe · passed · 651 ms · metadata changed · 2 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http can-i-vibe-mcp https://canivibe.ai/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add can-i-vibe-mcp --url https://canivibe.ai/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable can-i-vibe-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "can-i-vibe-mcp": {
      "url": "https://canivibe.ai/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "can-i-vibe-mcp": {
      "type": "streamableHttp",
      "url": "https://canivibe.ai/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start can-i-vibe-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "can-i-vibe-mcp": {
      "type": "http",
      "url": "https://canivibe.ai/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http can-i-vibe-mcp https://canivibe.ai/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.

Claude Desktop configuration

https://canivibe.ai/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "can-i-vibe-mcp": {
      "serverUrl": "https://canivibe.ai/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Can I Vibe? MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

See all 8,787

Do you run Can I Vibe? MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing