# ai.kaiv/is-it-down (remote · api.kaiv.ai)

Is GitHub, npm, Cloudflare or your AI provider down right now? 20 status pages, one call.

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `api.kaiv.ai`: 83/100 (this document), [markdown](https://verifymcp.io/servers/ai-kaiv-is-it-down/api-bridge-mcp-is-it-down-a0a9031c.md), [page](https://verifymcp.io/servers/ai-kaiv-is-it-down/api-bridge-mcp-is-it-down-a0a9031c)

## Channel facts

- Endpoint: `https://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 383 tokens (~127/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the ai.kaiv/is-it-down MCP server?

ai.kaiv/is-it-down is a hosted endpoint at https://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ai-kaiv-is-it-down 'https://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-kaiv-is-it-down": {
      "url": "https://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-kaiv-is-it-down": {
      "type": "http",
      "url": "https://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-kaiv-is-it-down]
url = "https://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-kaiv-is-it-down": {
      "type": "remote",
      "url": "https://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-kaiv-is-it-down --url 'https://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-kaiv-is-it-down:
    url: "https://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-kaiv-is-it-down": {
      "Transport": "http",
      "Url": "https://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-kaiv-is-it-down -t streamable-http -u 'https://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c'
```

### Other

```json
{
  "mcpServers": {
    "ai-kaiv-is-it-down": {
      "type": "http",
      "url": "https://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 76, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (3)

### `check_all_services` (~111 tokens)

Check All Services

Is anything I depend on broken right now?

Checks every supported provider in parallel and returns a one-sentence summary plus per-service detail. Use this first: it answers the whole question in one call. Optionally narrow with ?services=github,npm. A provider whose status page cannot be read is reported as "unknown", never as healthy.

Input parameters:

- `services` (string): Optional comma-separated slugs to narrow the check, e.g. "github,npm,cloudflare". Omit to check all.

Output parameters:

- `all_operational` (boolean): True only when every checked service reports no known problems AND every status page was reachable.
- `checked` (integer): How many services were checked.
- `degraded` (array): Slugs with a minor incident open.
- `down` (array): Slugs with a major or critical incident open.
- `services` (array): Full per-service detail.
- `summary` (string): One sentence answering "is anything broken right now", safe to show verbatim.
- `unknown` (array): Slugs whose status page could not be read.

### `check_service_status` (~132 tokens)

Check Service Status

Current incident state for one named service.

Returns the normalised state (operational, degraded, down, unknown), the provider's own description, and a link to the full status page. Use when you already know which provider you care about.

Input parameters:

- `service` (string, required): Slug of the service to check. One of: github, npm, cloudflare, anthropic, openai, vercel, netlify, render, supabase, mongodb, digitalocean, docker, circleci, sentry, datadog, twilio, atlassian, bitbu…

Output parameters:

- `cached` (boolean): Whether this answer came from the 45 second cache rather than a fresh fetch.
- `description` (string): The provider's own one-line summary, when it publishes one.
- `healthy` (boolean): True when operational, false when degraded or down, null when unknown.
- `indicator` (string): Raw statuspage.io indicator: none, minor, major or critical.
- `meaning` (string): Plain-language reading of the state, safe to show a user verbatim.
- `name` (string): Human name of the provider.
- `reachable` (boolean): Whether the status page itself answered.
- `service` (string): The slug that was checked.
- `state` (string): Normalised state. "unknown" means the status page could not be read, NOT that the service is down.
- `status_page` (string): URL a human can open to read the full incident history.
- `updated_at` (string): When the provider last updated the page (ISO 8601).

### `list_supported_services` (~39 tokens)

List Supported Services

Which services can be checked.

Lists every supported slug with its human name and status page URL. The list is fixed; arbitrary URLs are not accepted.

Output parameters:

- `count` (integer)
- `services` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-kaiv-is-it-down/api-bridge-mcp-is-it-down-a0a9031c#diagnostics

## Score history

- 2026-09-20: 83
- 2026-09-19: 83
- 2026-09-18: 82
- 2026-09-17: 82
- 2026-09-16: 81
- 2026-09-15: 81
- 2026-09-14: 80
- 2026-09-13: 80
- 2026-09-12: 80
- 2026-09-11: 79
- 2026-09-10: 79
- 2026-09-09: 78
- 2026-09-08: 78
- 2026-09-07: 77
- 2026-09-06: 77
- 2026-09-05: 76
- 2026-09-04: 76

## Common questions

### What is the ai.kaiv/is-it-down MCP server?

ai.kaiv/is-it-down is an MCP server listed in the public MCP registry as ai.kaiv/is-it-down. Is GitHub, npm, Cloudflare or your AI provider down right now? 20 status pages, one call. This page covers its hosted endpoint (https://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c).

### Is the ai.kaiv/is-it-down MCP server safe to use?

ai.kaiv/is-it-down scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the ai.kaiv/is-it-down MCP server expose?

ai.kaiv/is-it-down exposes 3 tools: check_all_services, check_service_status, list_supported_services. Their descriptions and schemas cost roughly 282 tokens of context every time the server is loaded.

### Does the ai.kaiv/is-it-down MCP server require authentication?

No. We connected to ai.kaiv/is-it-down without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ai.kaiv/is-it-down MCP server still maintained?

ai.kaiv/is-it-down is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c
- Changelog RSS feed: https://verifymcp.io/servers/ai-kaiv-is-it-down/api-bridge-mcp-is-it-down-a0a9031c.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-kaiv-is-it-down/api-bridge-mcp-is-it-down-a0a9031c.json
- HTML version of this page: https://verifymcp.io/servers/ai-kaiv-is-it-down/api-bridge-mcp-is-it-down-a0a9031c