# ai.kaiv/can-i-use

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

- name: ai.kaiv/can-i-use
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 76/100 flags: no-repository
- quality: 100/100 (strong)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/ai.kaiv%2Fcan-i-use
- tools: https://api.protogrid.dev/v1/servers/ai.kaiv%2Fcan-i-use/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 80
- liveness: 98
- freshness: 85
- provenance: 45
- drivers: +dns-namespace +reachable +uptime-95% ~updated-46d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 100/100 (strong)

### protocol: 100 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- pass `protocol.list_ttl`: tool list is cacheable (ttlMs 60000)

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 3 of 3 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 390 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 3, about 390 tokens to load them all
- tool set hash: 559f555efde8beaf8f61bda896189158
- badge: [![protogrid quality](https://protogrid.dev/badge/ai.kaiv/can-i-use.svg)](https://protogrid.dev/servers/ai.kaiv/can-i-use)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://api.kaiv.ai/api/bridge/mcp/can-i-use-5446c68b (streamable-http, auth none, reachable true, uptime30d 0.9464286)

## Packages

_none_

## Tools (3)

- `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.
- `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.
- `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.