io.usefulapi/tailscale

REMOTE · TAILSCALE.USEFULAPI.IO · SCANNED AUG 3

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

Available components

70 70 Trust /100

Trust breakdown (6 categories)

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 →

Endpoint Security78

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
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. View diagnostics → Pass
HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability77

AI-judged instruction clarity (excellent).Pass
Tool/resource definitions use about 1451 tokens (~65/item across 22 items; 22 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management3

Stability observed for 1 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

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · tailscale.usefulapi.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.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
    }
  }
}

# add to OpenClaw

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

# ~/.hermes/config.yaml

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

// mcp.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 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.

3 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
2 Aug 26 +52
- Authorization: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- 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 functional
1 Aug 26 18

First indexed and scored.

Show 1 earlier entry Hide earlier entries

Diagnostics

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 3 Aug 2026 · Probed https://tailscale.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=usefulapi.io	CN=WE1,O=Google Trust Services,C=US	1 Aug 2026	30 Oct 2026	ECDSA 256	ECDSA-SHA256	488e436f5b48bf6c1363342a4716e721
SANs: usefulapi.io, tailscale.usefulapi.io, *.tailscale.usefulapi.io
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

DNSSEC insecure

Validation of tailscale.usefulapi.io. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
io.	present	57355	8	Verified
usefulapi.io.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result	Enforced and verified
Enforced	On tool calls
HTTP status	200

WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://tailscale.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"

Bearer realm="OAuth", resource_metadata="https://tailscale.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"

Protected resource metadata

Document	https://tailscale.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved	Yes
Resource	https://tailscale.usefulapi.io/mcp
Authorisation server	https://tailscale.usefulapi.io

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://tailscale.usefulapi.io/mcp	Verified	200
http (plaintext)	http://tailscale.usefulapi.io/mcp	Inconclusive	401

MCP tools — 22 exposed · ~1,451 tokens

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.

Tool Tokens

tailscale_authorize_device Authorize device ~80

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

Input Output Examples

Name	Type	Req	Description
authorized	boolean	yes	True to authorize the device into the tailnet, false to de-authorize it.
deviceId	string	yes	The device id.

No output schema declared.

No examples provided.

tailscale_create_auth_key Create auth key ~169

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

Input Output Examples

Name	Type	Req	Description
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"].

No output schema declared.

No examples provided.

tailscale_delete_device Delete device ~46

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

Input Output Examples

Name	Type	Req	Description
deviceId	string	yes	The device id to delete.

No output schema declared.

No examples provided.

tailscale_delete_key Delete key ~60

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

Input Output Examples

Name	Type	Req	Description
keyId	string	yes	The key id to delete.

No output schema declared.

No examples provided.

tailscale_expire_device_key Expire device key ~62

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 Output Examples

Name	Type	Req	Description
deviceId	string	yes	The device id.

No output schema declared.

No examples provided.

tailscale_get_device Get device ~70

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

Input Output Examples

Name	Type	Req	Description
deviceId	string	yes	The device id.
fields	string	—	Field set — 'all' returns all fields incl. posture attributes and routes; 'default' is the standard subset.

No output schema declared.

No examples provided.

tailscale_get_dns_preferences Get DNS preferences ~44

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

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tailscale_get_key Get key ~60

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

Input Output Examples

Name	Type	Req	Description
keyId	string	yes	The key id.

No output schema declared.

No examples provided.

tailscale_get_policy_file Get policy file ~76

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

Input Output Examples

Name	Type	Req	Description
details	boolean	—	If true, include metadata about the policy file (e.g. when and by whom it was last updated).

No output schema declared.

No examples provided.

tailscale_get_split_dns Get split DNS ~48

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

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tailscale_get_tailnet_settings Get tailnet settings ~44

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

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tailscale_get_user Get user ~40

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

Input Output Examples

Name	Type	Req	Description
userId	string	yes	The user id.

No output schema declared.

No examples provided.

tailscale_list_device_routes List device routes ~49

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

Input Output Examples

Name	Type	Req	Description
deviceId	string	yes	The device id.

No output schema declared.

No examples provided.

tailscale_list_devices List devices ~76

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

Input Output Examples

Name	Type	Req	Description
fields	string	—	Field set — 'all' returns all fields incl. posture attributes and routes; 'default' is the standard subset.

No output schema declared.

No examples provided.

tailscale_list_dns_nameservers List DNS nameservers ~42

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

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tailscale_list_dns_searchpaths List DNS search paths ~44

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

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tailscale_list_keys List keys ~73

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

Input Output Examples

Name	Type	Req	Description
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.

No output schema declared.

No examples provided.

tailscale_list_users List users ~93

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

Input Output Examples

Name	Type	Req	Description
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.

No output schema declared.

No examples provided.

tailscale_list_webhooks List webhooks ~37

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

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tailscale_set_device_name Set device name ~56

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

Input Output Examples

Name	Type	Req	Description
deviceId	string	yes	The device id.
name	string	yes	The new device name.

No output schema declared.

No examples provided.

tailscale_set_device_routes Set device routes ~102

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

Input Output Examples

Name	Type	Req	Description
deviceId	string	yes	The device id.
routes	array	yes	The set of subnet routes (CIDRs) to ENABLE for this device, e.g. ["10.0.0.0/24"]. REPLACES the enabled set.

No output schema declared.

No examples provided.

tailscale_set_device_tags Set device tags ~80

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

Input Output Examples

Name	Type	Req	Description
deviceId	string	yes	The device id.
tags	array	yes	ACL tags to apply, e.g. ["tag:server"]. REPLACES the device's existing tags.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

1 Aug 3 Aug