# ai.kaiv/can-i-use (remote · api.kaiv.ai)

Browser support for web features, live from caniuse. From which version, and is it safe to ship?

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

## Components

- remote · `api.kaiv.ai`: 84/100 (this document), [markdown](https://verifymcp.io/servers/ai-kaiv-can-i-use/api-bridge-mcp-can-i-use-5446c68b.md), [page](https://verifymcp.io/servers/ai-kaiv-can-i-use/api-bridge-mcp-can-i-use-5446c68b)

## Channel facts

- Endpoint: `https://api.kaiv.ai/api/bridge/mcp/can-i-use-5446c68b`
- 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**: 83/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 338 tokens (~112/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/can-i-use MCP server?

ai.kaiv/can-i-use is a hosted endpoint at https://api.kaiv.ai/api/bridge/mcp/can-i-use-5446c68b, 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-can-i-use 'https://api.kaiv.ai/api/bridge/mcp/can-i-use-5446c68b'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-kaiv-can-i-use": {
      "url": "https://api.kaiv.ai/api/bridge/mcp/can-i-use-5446c68b"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-kaiv-can-i-use": {
      "type": "http",
      "url": "https://api.kaiv.ai/api/bridge/mcp/can-i-use-5446c68b"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-kaiv-can-i-use]
url = "https://api.kaiv.ai/api/bridge/mcp/can-i-use-5446c68b"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-kaiv-can-i-use": {
      "type": "remote",
      "url": "https://api.kaiv.ai/api/bridge/mcp/can-i-use-5446c68b",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-kaiv-can-i-use --url 'https://api.kaiv.ai/api/bridge/mcp/can-i-use-5446c68b' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-kaiv-can-i-use:
    url: "https://api.kaiv.ai/api/bridge/mcp/can-i-use-5446c68b"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-kaiv-can-i-use": {
      "Transport": "http",
      "Url": "https://api.kaiv.ai/api/bridge/mcp/can-i-use-5446c68b"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-kaiv-can-i-use -t streamable-http -u 'https://api.kaiv.ai/api/bridge/mcp/can-i-use-5446c68b'
```

### Other

```json
{
  "mcpServers": {
    "ai-kaiv-can-i-use": {
      "type": "http",
      "url": "https://api.kaiv.ai/api/bridge/mcp/can-i-use-5446c68b"
    }
  }
}
```

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-20 (score 84, +1)

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

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

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

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

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

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

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 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-09 (score 79, +1)

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

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

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

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

- [functional improvement] Stability: unverified → 0.03

## MCP tools (3)

### `check_feature_support` (~116 tokens)

Check Feature Support

Can I use this feature, and from which browser version?

Accepts a loose name (":has()", "container queries", "css-grid") and resolves it to a caniuse feature, then returns the earliest continuously-supported version per major browser, global usage percentage, and a conservative safe_to_use flag. Use this first; it answers the whole question in one call.

Input parameters:

- `feature` (string, required): Feature name or caniuse id. Loose names are resolved, e.g. "has selector" finds "css-has".

Output parameters:

- `description` (string)
- `feature` (string): Resolved caniuse feature id.
- `global_partial_percent` (number)
- `global_support_percent` (number): Percentage of tracked global users on a browser version that fully supports it.
- `meaning` (string): One sentence, safe to show a user verbatim.
- `other_matches` (array): Other features the query could have meant.
- `resolved_from` (string): The query that was matched, so a caller can see what it actually asked about.
- `safe_to_use` (boolean): True only when global support is at least 90% AND no major browser is missing it. A conservative single answer.
- `spec` (string)
- `support` (object): Per-browser detail, keyed by caniuse browser id.
- `title` (string)
- `unsupported_in` (array): Major browsers whose newest release still does not support it.

### `get_feature_by_id` (~63 tokens)

Get Feature By Id

Support table for an exact caniuse feature id.

Use when the id is already known, for example from a previous search. No fuzzy matching is applied.

Input parameters:

- `id` (string, required): Exact caniuse feature id, e.g. "css-has".

Output parameters:

- `description` (string)
- `feature` (string): Resolved caniuse feature id.
- `global_partial_percent` (number)
- `global_support_percent` (number): Percentage of tracked global users on a browser version that fully supports it.
- `meaning` (string): One sentence, safe to show a user verbatim.
- `other_matches` (array): Other features the query could have meant.
- `resolved_from` (string): The query that was matched, so a caller can see what it actually asked about.
- `safe_to_use` (boolean): True only when global support is at least 90% AND no major browser is missing it. A conservative single answer.
- `spec` (string)
- `support` (object): Per-browser detail, keyed by caniuse browser id.
- `title` (string)
- `unsupported_in` (array): Major browsers whose newest release still does not support it.

### `search_features` (~58 tokens)

Search Features

Find the caniuse feature id for a loose query.

Use when a query is ambiguous and you want to choose between candidates before checking support.

Input parameters:

- `q` (string, required): Free-text query, e.g. "grid" or "web share".

Output parameters:

- `count` (integer)
- `matches` (array)
- `query` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-kaiv-can-i-use/api-bridge-mcp-can-i-use-5446c68b#diagnostics

## Score history

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

## Common questions

### What is the ai.kaiv/can-i-use MCP server?

ai.kaiv/can-i-use is an MCP server listed in the public MCP registry as ai.kaiv/can-i-use. Browser support for web features, live from caniuse. From which version, and is it safe to ship? This page covers its hosted endpoint (https://api.kaiv.ai/api/bridge/mcp/can-i-use-5446c68b).

### Is the ai.kaiv/can-i-use MCP server safe to use?

ai.kaiv/can-i-use scores 84 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/can-i-use MCP server expose?

ai.kaiv/can-i-use exposes 3 tools: check_feature_support, get_feature_by_id, search_features. Their descriptions and schemas cost roughly 237 tokens of context every time the server is loaded.

### Does the ai.kaiv/can-i-use MCP server require authentication?

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

### Is the ai.kaiv/can-i-use MCP server still maintained?

ai.kaiv/can-i-use 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/can-i-use-5446c68b
- Changelog RSS feed: https://verifymcp.io/servers/ai-kaiv-can-i-use/api-bridge-mcp-can-i-use-5446c68b.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-kaiv-can-i-use/api-bridge-mcp-can-i-use-5446c68b.json
- HTML version of this page: https://verifymcp.io/servers/ai-kaiv-can-i-use/api-bridge-mcp-can-i-use-5446c68b