ai.kaiv/is-it-down
REMOTE · API.KAIV.AI · SCANNED SEP 20
Is GitHub, npm, Cloudflare or your AI provider down right now? 20 status pages, one call.
Available components
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. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 383 tokens (~127/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · api.kaiv.ai
claude mcp add --transport http ai-kaiv-is-it-down 'https://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c'
{
"mcpServers": {
"ai-kaiv-is-it-down": {
"url": "https://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c"
}
}
} {
"servers": {
"ai-kaiv-is-it-down": {
"type": "http",
"url": "https://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c"
}
}
} [mcp_servers.ai-kaiv-is-it-down] url = "https://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c"
{
"$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 mcp add ai-kaiv-is-it-down --url 'https://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c' --transport streamable-http
mcp_servers:
ai-kaiv-is-it-down:
url: "https://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c" {
"McpServers": {
"ai-kaiv-is-it-down": {
"Transport": "http",
"Url": "https://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c"
}
}
} assistant mcp add ai-kaiv-is-it-down -t streamable-http -u 'https://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 12 Sept 26 +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.
- 10 Sept 26 +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.
- 8 Sept 26 +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.
- 6 Sept 26 +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.
- 5 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=kaiv.ai | CN=WE1,O=Google Trust Services,C=US | 9 Sept 2026 | 8 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | b225111947d906a40e56536076ff66c0 |
| SANs: kaiv.ai, *.kaiv.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.kaiv.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| kaiv.ai. | present | 2371 | 13 | Verified |
| api.kaiv.ai. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self';form-action 'self' https://auth.kaiv.ai;script-src 'self' https://cdnjs.cloudflare.com https://challenges.cloudflare.com 'unsafe-inline';style-src 'self' https://cdnjs.cloudflare.com 'unsafe-inline';img-src 'self' data: blob:;connect-src 'self' https://api.openai.com https://api.anthropic.com https://generativelanguage.googleapis.com https://challenges.cloudflare.com https://*.kaiv.ai;frame-src 'self' https://challenges.cloudflare.com;font-src 'self' https://cdnjs.cloudflare.com;object-src 'none';media-src 'self';base-uri 'self';frame-ancestors 'self';script-src-attr 'none';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c | Verified | 200 | |
| http (plaintext) | http://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c | HTTPS enforced | 301 | https://api.kaiv.ai/api/bridge/mcp/is-it-down-a0a9031c |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_all_services Check All Services ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| services | string | – | Optional comma-separated slugs to narrow the check, e.g. "github,npm,cloudflare". Omit to check all. |
| Name | Type | Req | Description |
|---|---|---|---|
| all_operational | boolean | yes | True only when every checked service reports no known problems AND every status page was reachable. |
| checked | integer | yes | 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 | yes | Full per-service detail. |
| summary | string | yes | One sentence answering "is anything broken right now", safe to show verbatim. |
| unknown | array | – | Slugs whose status page could not be read. |
No examples provided.
check_service_status Check Service Status ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| service | string | yes | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Plain-language reading of the state, safe to show a user verbatim. |
| name | string | yes | Human name of the provider. |
| reachable | boolean | yes | Whether the status page itself answered. |
| service | string | yes | The slug that was checked. |
| state | string | yes | 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). |
No examples provided.
list_supported_services List Supported Services ~39
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| services | array | – | – |
No examples provided.
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.