Tailscale MCP by usefulapi
REMOTE · TAILSCALE.USEFULAPI.IO
Read devices, users, keys, ACLs and DNS for a tailnet; manage devices, routes and auth keys.
Available components
Last scanned (6 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Cloud Infrastructure
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. 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
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 2 Nov 26 −62
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “check_users_keys_and_their_expiry” functional
- New prompt “find_devices_that_have_not_been_seen_lately” functional
- New prompt “rename_or_tag_devices_change_approval_or_subnet_routes” functional
- New prompt “respond_to_a_lost_device_or_leaked_key” functional
- New prompt “review_acls_dns_and_tailnet_settings” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.26.0 → 1.27.0 functional
- Server version: 1.25.0 → 1.26.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.0 → 1.21.3 functional
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.20.0 → 1.21.0 functional
- Server version: 1.19.0 → 1.20.0 functional
- Server version: 1.17.0 → 1.19.0 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 5 Nov 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 | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tailscale.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tailscale.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/tailscale/ |
| http (plaintext) | http://tailscale.usefulapi.io/mcp | Inconclusive | 302 | http://tailscale.usefulapi.io/mcp |
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 →
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.
| 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.
| 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}.
| 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}.
| 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.
| 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}.
| 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 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}.
| 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.
| 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 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 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}.
| 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.
| 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.
| 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 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 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.
| 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.
| 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 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.
| 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.
| 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.
| 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.
How do I install the Tailscale MCP by usefulapi server?
Tailscale MCP by usefulapi is a hosted endpoint at https://tailscale.usefulapi.io/mcp, 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 · tailscale.usefulapi.io
claude mcp add --transport http io-usefulapi-tailscale 'https://tailscale.usefulapi.io/mcp'
What is the Tailscale MCP by usefulapi server?
Tailscale MCP by usefulapi is listed in the public MCP registry as io.usefulapi/tailscale. Read devices, users, keys, ACLs and DNS for a tailnet; manage devices, routes and auth keys. This page covers its hosted endpoint (https://tailscale.usefulapi.io/mcp).
Is the Tailscale MCP by usefulapi server safe to use?
Tailscale MCP by usefulapi scores 18 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 Tailscale MCP by usefulapi server expose?
Tailscale MCP by usefulapi exposes 22 tools: tailscale_list_devices, tailscale_get_device, tailscale_list_device_routes, tailscale_list_keys, tailscale_get_key, and 17 more. Their descriptions and schemas cost roughly 1,451 tokens of context every time the server is loaded.
Does the Tailscale MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Tailscale MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Tailscale MCP by usefulapi server still maintained?
Tailscale MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Tailscale MCP by usefulapi server?
VerifyMCP ran 4 checks on Tailscale MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Tailscale MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.