Can I Vibe? — AI coding provider status MCP Server

by canivibe Your server? Claim it

answering

Can I Vibe? — AI coding provider status is answering right now. Last checked 15 min ago. It exposes 2 tools.

Live status and health checks for AI coding providers: Claude, Cursor, Copilot, Codex and more.

Uptime history 91 days of history

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

264 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Can I Vibe? — AI coding provider status every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add status --transport http https://canivibe.ai/mcp

Settings → Connectors → Add custom connector, then paste this address

https://canivibe.ai/mcp

~/.codex/config.toml

[mcp_servers.status]
url = "https://canivibe.ai/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "status": {
      "url": "https://canivibe.ai/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "status": {
      "type": "http",
      "url": "https://canivibe.ai/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

provider

ai_provider_status

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.

check_provider_health

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.

Endpoints

URL	Transport	State	Latency	Checked
https://canivibe.ai/mcp	streamable-http	answering	242 ms	15 min ago

Alternatives to Can I Vibe? — AI coding provider status

same job, measured the same way

AI Down: live AI service status

by aidown

Is Claude, ChatGPT, Gemini, Cursor or Copilot down? Live status from API probes and user reports.

1 tools answering

Agent Audit

by fullstackdegen

Turn Lighthouse audits into coding-agent fix packs for Claude Code, Cursor, and Copilot.

47 installs/wk local only

StillOnline

by shenwell

StillOnline MCP: uptime, status pages, checks. REST API for Cursor and Claude Code.

42 installs/wk local only

Industry Pulse

by openkrill

What happened in AI coding agents like Claude Code, Codex, Cursor and Copilot, and what people say.

7 tools answering

Contextforge MCP

by alfredoizdev

Persistent memory MCP server for Claude Code, Cursor, and GitHub Copilot.

216 installs/wk local only

AI Context Kit

by ofershap

Lint, measure, and sync AI context files across Cursor, Claude Code, Copilot.

117 installs/wk local only

Preflight

by newrelic-experimental

New Relic MCP server for observing AI coding assistants (Claude Code, Cursor, Copilot, etc.)

1 614 installs/wk local only

LLM Provider MCP

by manishiitg

Delegate asynchronous coding jobs between Claude Code, Codex, Cursor Agent, and Pi.

local only

Can I Vibe? — AI coding provider status — questions

Answers built from our own checks of this server.

What can Can I Vibe? — AI coding provider status do?

It exposes 2 tools, read directly from the server on our last check. Among them: ai_provider_status, check_provider_health. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Can I Vibe? — AI coding provider status working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 264 ms. The bar chart above shows every period we have measured.

How do I connect Can I Vibe? — AI coding provider status?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Can I Vibe? — AI coding provider status need an API key?

No. Can I Vibe? — AI coding provider status completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Can I Vibe? — AI coding provider status?

It answers our handshake in 264 ms on average, which is faster than 54% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.