# io.usefulapi/tailscale (remote · tailscale.usefulapi.io)

Read devices, users, keys, ACLs and DNS for a tailnet; manage devices, routes and auth keys.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `tailscale.usefulapi.io`: 70/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-tailscale/tailscale.md), [page](https://verifymcp.io/servers/io-usefulapi-tailscale/tailscale)

## Channel facts

- Endpoint: `https://tailscale.usefulapi.io/mcp`
- 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-08-03.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1451 tokens (~65/item across 22 items; 22 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 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.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http io-usefulapi-tailscale https://tailscale.usefulapi.io/mcp
```

### Codex

```toml
[mcp_servers.io-usefulapi-tailscale]
url = "https://tailscale.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-tailscale": {
      "type": "remote",
      "url": "https://tailscale.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-tailscale --url https://tailscale.usefulapi.io/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-tailscale:
    url: "https://tailscale.usefulapi.io/mcp"
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-tailscale": {
      "type": "http",
      "url": "https://tailscale.usefulapi.io/mcp"
    }
  }
}
```

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-08-03 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-02 (score 70, +52)

- [security improvement] Authorization: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Authorization: partial
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: excellent
- [functional] First check of Schema quality: pass
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: fail

### 2026-08-01 (score 18)

First indexed and scored.

## MCP tools (22)

### `tailscale_list_devices` (~76 tokens)

List devices

List all devices in the tailnet (name, addresses, OS, last seen, tags, etc.). Tailscale REST: GET /tailnet/{tailnet}/devices.

Input parameters:

- `fields` (string): Field set — 'all' returns all fields incl. posture attributes and routes; 'default' is the standard subset.

### `tailscale_get_device` (~70 tokens)

Get device

Get a single device by id. Tailscale REST: GET /device/{deviceId}.

Input parameters:

- `deviceId` (string, required): The device id.
- `fields` (string): Field set — 'all' returns all fields incl. posture attributes and routes; 'default' is the standard subset.

### `tailscale_list_device_routes` (~49 tokens)

List device routes

List the subnet routes a device advertises and which are enabled. Tailscale REST: GET /device/{deviceId}/routes.

Input parameters:

- `deviceId` (string, required): The device id.

### `tailscale_list_keys` (~73 tokens)

List keys

List auth keys and API access tokens for the tailnet. Tailscale REST: GET /tailnet/{tailnet}/keys.

Input parameters:

- `all` (boolean): If true, returns all keys, tokens and OAuth clients in the tailnet, not just the caller's own (requires appropriate scope). Default false.

### `tailscale_get_key` (~60 tokens)

Get key

Get details of a single auth key / API access token by id (capabilities, expiry, usage). Tailscale REST: GET /tailnet/{tailnet}/keys/{keyId}.

Input parameters:

- `keyId` (string, required): The key id.

### `tailscale_get_policy_file` (~76 tokens)

Get policy file

Get the tailnet's ACL / policy file (returned as JSON via the Accept header, not HuJSON). Tailscale REST: GET /tailnet/{tailnet}/acl.

Input parameters:

- `details` (boolean): If true, include metadata about the policy file (e.g. when and by whom it was last updated).

### `tailscale_list_dns_nameservers` (~42 tokens)

List DNS nameservers

List the global DNS nameservers configured for the tailnet. Tailscale REST: GET /tailnet/{tailnet}/dns/nameservers.

### `tailscale_get_dns_preferences` (~44 tokens)

Get DNS preferences

Get the tailnet's DNS preferences (e.g. whether MagicDNS is enabled). Tailscale REST: GET /tailnet/{tailnet}/dns/preferences.

### `tailscale_list_dns_searchpaths` (~44 tokens)

List DNS search paths

List the DNS search paths (search domains) configured for the tailnet. Tailscale REST: GET /tailnet/{tailnet}/dns/searchpaths.

### `tailscale_get_split_dns` (~48 tokens)

Get split DNS

Get the tailnet's split-DNS configuration — a map of domain → nameservers. Tailscale REST: GET /tailnet/{tailnet}/dns/split-dns.

### `tailscale_list_users` (~93 tokens)

List users

List users of the tailnet, optionally filtered by type, role or status. Tailscale REST: GET /tailnet/{tailnet}/users.

Input parameters:

- `role` (string): Filter by role, e.g. owner, admin, member, it-admin, network-admin, billing-admin, auditor.
- `status` (string): Filter by user status.
- `type` (string): Filter by user type.

### `tailscale_get_user` (~40 tokens)

Get user

Get a single user by id. Tailscale REST: GET /users/{userId}.

Input parameters:

- `userId` (string, required): The user id.

### `tailscale_list_webhooks` (~37 tokens)

List webhooks

List the webhook endpoints configured for the tailnet. Tailscale REST: GET /tailnet/{tailnet}/webhooks.

### `tailscale_get_tailnet_settings` (~44 tokens)

Get tailnet settings

Get the tailnet's settings (device approval, key expiry, posture, etc.). Tailscale REST: GET /tailnet/{tailnet}/settings.

### `tailscale_authorize_device` (~80 tokens)

Authorize device

Authorize or de-authorize a device (only relevant when device approval is enabled for the tailnet). Tailscale REST: POST /device/{deviceId}/authorized.

Input parameters:

- `authorized` (boolean, required): True to authorize the device into the tailnet, false to de-authorize it.
- `deviceId` (string, required): The device id.

### `tailscale_set_device_name` (~56 tokens)

Set device name

Set (rename) a device's name. Tailscale REST: POST /device/{deviceId}/name.

Input parameters:

- `deviceId` (string, required): The device id.
- `name` (string, required): The new device name.

### `tailscale_set_device_tags` (~80 tokens)

Set device tags

Set a device's ACL tags. REPLACES the device's existing tags. Tailscale REST: POST /device/{deviceId}/tags.

Input parameters:

- `deviceId` (string, required): The device id.
- `tags` (array, required): ACL tags to apply, e.g. ["tag:server"]. REPLACES the device's existing tags.

### `tailscale_expire_device_key` (~62 tokens)

Expire device key

Expire a device's node key, forcing it to re-authenticate — a security response to a compromised or lost device. Tailscale REST: POST /device/{deviceId}/expire.

Input parameters:

- `deviceId` (string, required): The device id.

### `tailscale_set_device_routes` (~102 tokens)

Set device routes

Set the subnet routes ENABLED for a device (from the routes it advertises). REPLACES the enabled set. Tailscale REST: POST /device/{deviceId}/routes.

Input parameters:

- `deviceId` (string, required): The device id.
- `routes` (array, required): The set of subnet routes (CIDRs) to ENABLE for this device, e.g. ["10.0.0.0/24"]. REPLACES the enabled set.

### `tailscale_create_auth_key` (~169 tokens)

Create auth key

Create a new auth key for the tailnet (used to register new devices). Tailscale REST: POST /tailnet/{tailnet}/keys.

Input parameters:

- `description` (string): A short description for the key.
- `ephemeral` (boolean): If true, devices registered with this key are ephemeral (removed shortly after going offline).
- `expirySeconds` (number): Key lifetime in seconds; 0 means no expiry (if allowed by tailnet policy).
- `preauthorized` (boolean): If true, devices registered with this key are pre-authorized (skip device approval).
- `reusable` (boolean): If true, the key can register multiple devices.
- `tags` (array): ACL tags to apply to devices created with this key, e.g. ["tag:ci"].

### `tailscale_delete_key` (~60 tokens)

Delete key

Delete (revoke) an auth key or API access token by id — a security response. Tailscale REST: DELETE /tailnet/{tailnet}/keys/{keyId}.

Input parameters:

- `keyId` (string, required): The key id to delete.

### `tailscale_delete_device` (~46 tokens)

Delete device

Delete a device, removing it from the tailnet. Tailscale REST: DELETE /device/{deviceId}.

Input parameters:

- `deviceId` (string, required): The device id to delete.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-tailscale/tailscale#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 70
- 2026-08-01: 18

## Links

- Remote endpoint: https://tailscale.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-tailscale/tailscale/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-tailscale/tailscale/changelog.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-tailscale/tailscale