@yawlabs/tailscale-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 0 of 5 tools tried
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @yawlabs/tailscale-mcp@0.23.4
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
5 tools that take no input and look read-only were called once with nothing. 0 returned a result.
tailscale_status | No usable answer tool reported an error: Error: No Tailscale credentials configured. Set TAILSCALE_API_KEY, or set both TAILSCALE_OAUTH_CLIENT_ID and TAILSCALE_OAUTH_CLIENT_SECR |
tailscale_list_devices | No usable answer tool reported an error: Error: No Tailscale credentials configured. Set TAILSCALE_API_KEY, or set both TAILSCALE_OAUTH_CLIENT_ID and TAILSCALE_OAUTH_CLIENT_SECR |
tailscale_get_acl | No usable answer tool reported an error: Error: No Tailscale credentials configured. Set TAILSCALE_API_KEY, or set both TAILSCALE_OAUTH_CLIENT_ID and TAILSCALE_OAUTH_CLIENT_SECR |
tailscale_get_nameservers | No usable answer tool reported an error: Error: No Tailscale credentials configured. Set TAILSCALE_API_KEY, or set both TAILSCALE_OAUTH_CLIENT_ID and TAILSCALE_OAUTH_CLIENT_SECR |
tailscale_get_search_paths | No usable answer tool reported an error: Error: No Tailscale credentials configured. Set TAILSCALE_API_KEY, or set both TAILSCALE_OAUTH_CLIENT_ID and TAILSCALE_OAUTH_CLIENT_SECR |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
1 tool with commands in capitals or very long text
- Gives the agent orders in
tailscale_update_acl:rve formatting, comments, and trailing commas (HuJSON). You MUST pass the ETag from tailscale_get_acl to prevent overwriting concurrent changes, or `ts-default` for
Common and usually harmless: it is how many makers stress how a tool should be used.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
tailscale_tool_groups toolName
Explain which of this server's tools are available and why. Call this FIRST when a Tailscale tool you expected is missing, instead of assuming the capability does not exist -- tools can be withheld by configuration, and the fix is usually one environment variable. Pass `toolName` to ask about one specific tool (e.g. 'tailscale_delete_device'): the answer distinguishes 'no such tool exists' -- where you should find another approach -- from 'it exists but its group is not loaded' and 'it exists and loaded but writes are withheld there', both of which the operator can enable and neither of which you should work around. With no arguments it lists every group with its availability and, where something is withheld, the exact environment change that would restore it. Always available regardless of filters.
tailscale_status
Check that the Tailscale API connection is working. Returns your tailnet name, device count, and confirms authentication is valid. Use this to verify setup.
tailscale_list_devices fields, filters
List all devices in your tailnet with their status, IP addresses, OS, and last seen time. 'lastSeen' is omitted while a device is connected (connectedToControl: true) and for devices that have never been online -- on a connected device a missing lastSeen means online now, not never seen.
tailscale_get_device deviceId, fields
Get detailed information about a specific device by its ID. Returns the default field subset unless fields: 'all'. 'lastSeen' is omitted while a device is connected (connectedToControl: true) and for devices that have never been online -- on a connected device a missing lastSeen means online now, not never seen.
tailscale_authorize_device deviceId
Authorize a device that is pending authorization.
93 more tools
tailscale_deauthorize_device deviceId
Deauthorize a device, immediately removing its access to the tailnet. The device will need to be re-authorized to reconnect.
tailscale_delete_device deviceId
Permanently remove a device from the tailnet. This is irreversible -- the device must re-authenticate to rejoin.
tailscale_rename_device deviceId, name
Set the name of a device in the tailnet, or reset it to its OS hostname.
tailscale_expire_device deviceId
Expire a device's key, forcing it to re-authenticate.
tailscale_get_device_routes deviceId
Get the subnet routes a device advertises and which are enabled.
tailscale_set_device_routes deviceId, routes
Set the enabled subnet routes for a device. Replaces all currently enabled routes -- pass the full list of routes you want enabled.
tailscale_get_device_posture_attributes deviceId
Get all posture attributes for a device, including custom and system-managed attributes.
tailscale_set_device_posture_attribute deviceId, attributeKey, value, expiry, comment
Set a custom posture attribute on a device. Creates or updates the attribute. Attribute keys must start with 'custom:'. Useful for compliance tracking, JIT access, and custom security policies.
tailscale_delete_device_posture_attribute deviceId, attributeKey
Delete a custom posture attribute from a device. This is irreversible.
tailscale_set_device_tags deviceId, tags
Set ACL tags on a device. Replaces all existing tags -- pass the full list of tags you want applied.
tailscale_set_device_ip deviceId, ipv4
Set the Tailscale IPv4 address for a device.
tailscale_update_device_key deviceId, keyExpiryDisabled
Update a device's key settings, such as disabling key expiry. Useful for servers that should never need to re-authenticate.
tailscale_set_devices_authorized deviceIds, authorized
Authorize or deauthorize multiple devices in one call. Each device's POST runs in parallel; per-device errors are returned alongside the successes so a partial failure doesn't lose the work that succeeded. On partial failure the call still returns success (ok) with data: { authorized, succeeded, failed } -- inspect data.failed for the per-device errors. POSTs are never retried, so on a large batch a rate-limited device lands in data.failed with status 429: re-call with just those ids, or set TAILSCALE_MAX_CONCURRENT to cap requests in flight. Common use: authorize a batch of newly-enrolled CI hosts, or deauthorize a group of devices flagged by a security review.tailscale_batch_update_posture_attributes nodes, comment
Batch update custom posture attributes across multiple devices. Each attribute key must start with 'custom:'. Uses JSON Merge Patch semantics -- pass null as the attribute config to delete.
tailscale_get_acl
Get the current ACL policy for your tailnet. Returns the raw policy text with original formatting preserved, including comments and trailing commas (HuJSON). Also returns an ETag -- you must pass it to tailscale_update_acl to safely update the policy.
tailscale_update_acl policy, etag
Update the ACL policy for your tailnet. Accepts the full policy as a string to preserve formatting, comments, and trailing commas (HuJSON). You MUST pass the ETag from tailscale_get_acl to prevent overwriting concurrent changes, or `ts-default` for the first write to a tailnet nobody has edited yet. Always get the current ACL first, make targeted edits to the text, and pass the full modified text back.
tailscale_validate_acl policy
Validate an ACL policy without applying it. Returns any errors found, or confirms the policy is valid.
tailscale_preview_acl policy, type, previewFor
Preview the ACL rules that would apply to a specific user or IP address if a proposed policy were applied.
tailscale_diff_acl_access policy, principals, maxPrincipals
Answer 'who loses access?' before applying an ACL change. Compares the CURRENT policy against a proposed one and reports, per user, which destinations they gain and lose. Run this before tailscale_update_acl -- validate_acl only checks syntax and the policy's own tests block, so a policy with no tests validates clean while revoking everyone. LIMITS, all reported in the response rather than left to be discovered. It compares USER principals only, so a revocation that runs through a tag or group can show a clean diff, and an empty result is never proof a change is safe. Posture DEFINITION changes ARE detected: posture names are resolved to their rules, so tightening `posture:corp` shows as a change -- except when a preview omits the definitions map, where it falls back to comparing names. It costs two preview requests per user, so it checks the first 25 by default and stops starting new users after 60 seconds (a user whose previews are already in flight still finishes); either way it sets `truncated`, reports how many were skipped, and says which limit stopped it. Users whose preview fails are listed in `failed` and excluded from the compared count -- a failure is never reported as lost access, and if nothing could be compared the call fails rather than returning an empty diff.
tailscale_get_nameservers
Get the DNS nameservers configured for your tailnet.
tailscale_set_nameservers dns
Set the DNS nameservers for your tailnet. Replaces all existing nameservers. Removing every nameserver may also change MagicDNS: the API reference says it is switched off, while Tailscale's current MagicDNS docs say a nameserver is no longer required -- check `magicDNS` in the response.
tailscale_get_search_paths
Get the DNS search paths configured for your tailnet.
tailscale_set_search_paths searchPaths
Set the DNS search paths for your tailnet. Replaces all existing search paths.
tailscale_get_split_dns
Get the split DNS configuration for your tailnet.
tailscale_set_split_dns splitDns
Set split DNS configuration. Maps domains to specific nameservers. Replaces the entire split DNS configuration: a domain you leave out is removed, and an empty object clears every domain. Per the API reference, setting a domain to null clears that domain's nameservers.
tailscale_get_dns_preferences
Get DNS preferences for your tailnet, including whether MagicDNS is enabled.
tailscale_set_dns_preferences magicDNS
Set DNS preferences for your tailnet, such as enabling or disabling MagicDNS. The API reference says enabling can fail when the tailnet has no nameservers; if it does, add one with tailscale_set_nameservers first.
tailscale_update_split_dns splitDns
Partially update split DNS configuration. Merges the provided domains with the existing config -- only the specified domains are changed, others are untouched. To remove a domain, set it to null: that is the idiom the API reference documents. An empty array is also accepted and forwarded as-is -- it is what Tailscale's Terraform provider sends.
tailscale_get_dns_configuration
Get the unified DNS configuration for your tailnet, including nameservers, search paths, split DNS, and MagicDNS preference in a single call.
tailscale_set_dns_configuration dns, searchPaths, splitDns, magicDNS
Set the unified DNS configuration for your tailnet in a single call. Replaces all DNS settings (nameservers, search paths, split DNS, MagicDNS preference). This is a replace-all endpoint: pass every top-level field you want to keep, because a field you omit may be cleared rather than left alone.
tailscale_list_keys all
List keys in your tailnet: auth keys, API access tokens, OAuth clients and federated identities. Without 'all', what comes back depends on the credential this server runs on -- a user-owned API key sees only that user's keys (including the API access token the server itself is using, keyType 'api'); an OAuth-client token sees the tailnet's OAuth clients; a federated-identity token sees its federated identities. Set 'all' to true for the tailnet-wide list (needs the matching :read scopes; only 'all:read' and 'all' return every API access token).
tailscale_get_key keyId
Get details for a specific key (auth key, API access token, OAuth client, or federated identity). A revoked or expired key is still returned, with `invalid: true`.
tailscale_create_key keyType, description, reusable, ephemeral, preauthorized, expirySeconds, tags, scopes, issuer, subject, audience, customClaimRules
Create a new key in your tailnet. Supports auth keys (for adding devices), OAuth clients (for programmatic API access), and federated identities (for OIDC-based CI/CD access). Returns the key value -- save it immediately, as it cannot be retrieved again.
SECURITY: the response body contains a long-lived credential verbatim. MCP clients commonly persist tool responses to logs and conversation transcripts; treat this response as sensitive (do not commit it, avoid re-sharing it in unrelated chat history).
Examples:
- Auth key: {keyType:'auth', reusable:true, tags:['tag:ci']}
- OAuth client: {keyType:'client', scopes:['devices:core:read','dns:read']}
- Federated (GitHub Actions): {keyType:'federated', scopes:['devices:core:read'], issuer:'https://token.actions.githubusercontent.com', subject:'repo:my-org/my-repo:*'}tailscale_delete_key keyId
Delete a key (auth key, API access token, OAuth client, or federated identity). This is irreversible. For auth keys, devices already authenticated are unaffected but no new devices can use it. For OAuth clients and federated identities, any integrations using them lose access immediately. API access tokens are deletable here too: if keyId is the token this server authenticates with -- it shows up in tailscale_list_keys under API-key auth -- the server revokes its own credential and every later call fails with 401 until it is reconfigured.
tailscale_update_key keyId, description, scopes, tags, issuer, subject, audience, customClaimRules
Update an existing key. Supported fields depend on the key type: all key types accept 'description'; OAuth clients and federated identities additionally accept 'scopes' and 'tags'; federated identities additionally accept 'issuer', 'subject', 'audience', and 'customClaimRules'. For auth keys, pass only 'description' -- the Tailscale API will reject other fields.
tailscale_create_oauth_app name, redirectUris, scopes, allowedNodeAttributes
Create an OAuth App for device provisioning (Tailscale alpha). Lets a third-party application enroll a device into your tailnet via the authorization-code flow, after a user consents. Returns the app's client secret -- save it immediately, it cannot be retrieved again. SECURITY: the response body contains a long-lived credential verbatim. MCP clients commonly persist tool responses to logs and conversation transcripts; treat this response as sensitive. Use scope 'auth_keys:create:once' (one auth key per authorization, no refresh token) -- the scope Tailscale's device-provisioning guide documents. The API reference's example shows 'auth_keys:create'; this tool does not restrict the value. Distinct from tailscale_create_key with keyType='client', which mints a machine-to-machine OAuth client instead.
tailscale_get_oauth_app appId
Get an OAuth App's configuration (name, redirect URIs, scopes) by its app ID. Use this to verify an app was registered as intended. The client secret is not returned -- it is only available at creation time.
tailscale_list_oauth_apps
List the OAuth Apps registered in your tailnet (Tailscale alpha). Returns an `oauthApps` array describing each app (id, name, redirect URIs, scopes). Client secrets are NOT included -- a secret is only returned once, by tailscale_create_oauth_app at creation time. This is how you recover the id of an app you did not record; pass that id to tailscale_delete_oauth_app to revoke it.
tailscale_delete_oauth_app appId
Delete an OAuth App (Tailscale alpha). This is irreversible: the app's client secret stops working immediately and any integration using it loses its device-enrollment path, so no further device can be authorized through it. Devices already enrolled stay in the tailnet, exactly as they do when the auth key that added them is deleted. Use tailscale_list_oauth_apps to find the id.
tailscale_list_users type, role
List all users in your tailnet.
tailscale_get_user userId
Get details for a specific user.
tailscale_approve_user userId
Approve a pending user, granting them access to the tailnet.
tailscale_suspend_user userId
Suspend a user, immediately revoking their access to the tailnet. Their devices will be disconnected. Can be reversed with tailscale_restore_user.
tailscale_restore_user userId
Restore a previously suspended user, re-granting them access to the tailnet.
tailscale_update_user_role userId, role
Update a user's role in the tailnet.
tailscale_delete_user userId
Delete a user from the tailnet. This is irreversible -- the user and all their devices will be removed.
tailscale_get_tailnet_settings
Get your tailnet settings (device approval, key expiry, HTTPS certificates, etc.).
tailscale_update_tailnet_settings devicesApprovalOn, devicesAutoUpdatesOn, devicesKeyDurationDays, usersApprovalOn, usersRoleAllowedToJoinExternalTailnets, networkFlowLoggingOn, regionalRoutingOn, postureIdentityCollectionOn, httpsEnabled, aclsExternallyManagedOn, aclsExternalLink
Update tailnet settings (device approval, auto-updates, key expiry, HTTPS certificates, network flow logging, regional routing, posture identity collection).
tailscale_get_contacts
Get the tailnet contact information (security, support, admin emails).
tailscale_set_contacts account, support, security
Update tailnet contact information. Each provided contact type (account/support/security) is PATCHed in parallel; per-type errors are returned alongside the successes so a partial failure doesn't lose the work that succeeded. On partial failure the response is data: { applied, failed } -- inspect data.failed for per-type error details.tailscale_resend_contact_verification contactType
Resend the verification email for a tailnet contact.
tailscale_list_org_tailnets organization, limit, cursor
List the tailnets in your organization, including API-only tailnets created via the API. Paginated: returns at most `limit` results (Tailscale defaults to 100) plus a `cursor`. Pass that cursor back to fetch the next page; an empty cursor in the response means you have reached the end. Requires OAuth authentication.
tailscale_create_org_tailnet displayName, organization
Create a new API-only tailnet in your organization. Returns the tailnet (id, displayName, orgId, dnsName, createdAt) AND a freshly-minted OAuth client for it. SECURITY: the response body contains that OAuth client's secret verbatim, and it cannot be retrieved again. MCP clients commonly persist tool responses to logs and conversation transcripts; treat this response as sensitive. Requires an OAuth client with the 'tailnets' scope -- an API key will not work. To then operate on the new tailnet, set TAILSCALE_OAUTH_TAILNET to its id and use an OAuth client with the 'all' scope. Organizations are limited to 10 tailnets including the original unless Tailscale sales has raised the limit. The response may include `alreadyExists: true`; Tailscale's spec ALSO documents a 400 for a name already in use and neither has been observed, so after a timeout call tailscale_list_org_tailnets before retrying rather than assuming either.
tailscale_delete_tailnet tailnet, confirmTailnet
Permanently delete a tailnet. This is IRREVERSIBLE and removes every device, user, ACL, and key in it. By default it acts on the tailnet the current credentials point at (TAILSCALE_TAILNET, or TAILSCALE_OAUTH_TAILNET when targeting an API-only tailnet). Pass `tailnet` to name a different one -- e.g. an id returned by tailscale_list_org_tailnets -- which requires credentials scoped to reach it; UNVERIFIED against a live tailnet, so expect a 403/404 if your token cannot. You must always pass `confirmTailnet` matching the effective target exactly; the call is refused locally otherwise. That check is a typo guard, not an authorization gate: when you also pass `tailnet` you are supplying both halves of the comparison, so it proves only that they agree -- it is a genuine second look only on the omit-`tailnet` path, where the value has to match the operator's environment. Restricting who may delete at all is TAILSCALE_READONLY / TAILSCALE_TOOLS, which drop this tool from the server entirely. Intended for tearing down API-only tailnets created by tailscale_create_org_tailnet.
tailscale_list_webhooks
List all webhooks configured for your tailnet.
tailscale_get_webhook webhookId
Get details for a specific webhook.
tailscale_create_webhook endpointUrl, providerType, subscriptions
Create a new webhook. The response includes the webhook's signing secret -- this is the only opportunity to capture it; save it immediately. Set providerType when the endpoint is a Slack, Mattermost, Google Chat or Discord incoming-webhook URL, so the events arrive in the format that provider renders. SECURITY: the response body contains the secret verbatim. MCP clients commonly persist tool responses to logs and conversation transcripts; treat this response as sensitive.
tailscale_update_webhook webhookId, endpointUrl, subscriptions
Update an existing webhook's endpoint URL and/or subscriptions.
tailscale_delete_webhook webhookId
Delete a webhook. This is irreversible -- the webhook secret cannot be recovered.
tailscale_rotate_webhook_secret webhookId
Rotate a webhook's secret. Returns the new secret -- save it immediately, as it cannot be retrieved again. The old secret is immediately invalidated. SECURITY: the response body contains the secret verbatim. MCP clients commonly persist tool responses to logs and conversation transcripts; treat this response as sensitive.
tailscale_test_webhook webhookId
Send a test event to a webhook endpoint to verify it is configured correctly and receiving events.
tailscale_list_posture_integrations
List all device posture integrations configured for your tailnet.
tailscale_get_posture_integration integrationId
Get details for a specific device posture integration.
tailscale_create_posture_integration provider, clientId, clientSecret, tenantId, cloudId
Create a new device posture integration.
tailscale_update_posture_integration integrationId, clientId, clientSecret, tenantId, cloudId
Update an existing posture integration's credentials or configuration.
tailscale_delete_posture_integration integrationId
Delete a posture integration. This is irreversible.
tailscale_get_audit_log start, end, actor, target, event
Get the tailnet audit/configuration log. Shows who changed what and when -- useful for troubleshooting and compliance. Optional actor, target and event filters narrow the query server-side, so a targeted question doesn't have to pull the whole window.
tailscale_get_network_flow_logs start, end
Get network traffic flow logs showing connections between devices. Shows source/destination nodes, timestamps, and traffic metadata -- useful for security monitoring and debugging connectivity.
tailscale_list_device_invites deviceId
List all device invites for a specific device.
tailscale_create_device_invite deviceId, multiUse, allowExitNode, email
Create a device share invitation that allows an external user to access a specific device in your tailnet.
tailscale_get_device_invite inviteId
Get details for a specific device invite.
tailscale_delete_device_invite inviteId
Delete a device invite. This is irreversible -- the invite link will stop working.
tailscale_accept_device_invite invite
Accept a device share invitation using the invite URL or code.
tailscale_list_user_invites
List the open (not yet accepted) user invites for your tailnet. Accepted invites are not returned.
tailscale_create_user_invite email, role
Create a new user invite that allows someone to join your tailnet.
tailscale_get_user_invite inviteId
Get details for a specific user invite.
tailscale_delete_user_invite inviteId
Delete a user invite. This is irreversible -- the invite link will stop working.
tailscale_resend_device_invite inviteId
Resend a device invite email.
tailscale_resend_user_invite inviteId
Resend a user invite email.
tailscale_list_services
List all Tailscale Services in your tailnet. Services provide stable MagicDNS names and virtual IPs, decoupled from individual devices. Note: this MCP has no create-service tool. The API documents its Service PUT as create-or-update, but tailscale_update_service sends only the fields you pass, so do not use it to create one. Use the update/delete/approval tools here once the service exists.
tailscale_get_service serviceName
Get details for a specific Tailscale Service, including its MagicDNS name, virtual IP, and configuration.
tailscale_update_service serviceName, ports, tags, autoApproveHosts
Update a Tailscale Service's configuration.
tailscale_delete_service serviceName
Delete a Tailscale Service. This is irreversible -- the service's MagicDNS name and virtual IP will be released.
tailscale_list_service_hosts serviceName
List devices hosting a specific Tailscale Service.
tailscale_get_service_device_approval serviceName, deviceId
Get the approval status of a specific device for a Tailscale Service.
tailscale_set_service_device_approval serviceName, deviceId, approved
Approve or reject a device to host a Tailscale Service.
tailscale_list_log_stream_configs
List all log streaming configurations for your tailnet. Fetches both 'configuration' (audit) and 'network' (flow) log stream configs. Log streaming sends logs to external destinations like Axiom, Datadog, Splunk, Elasticsearch, or S3.
tailscale_get_log_stream_config logType
Get the log streaming configuration for a specific log type.
tailscale_set_log_stream_config logType, destinationType, url, token, user, uploadPeriodMinutes, compressionFormat, s3Bucket, s3Region, s3KeyPrefix, s3AuthenticationType, s3AccessKeyId, s3SecretAccessKey, s3RoleArn
Set the log streaming configuration for a specific log type. Configures where logs are sent (e.g. Axiom, Datadog, Splunk, Elasticsearch, S3). Per-destination required fields: - splunk / elastic / panther / cribl / datadog / axiom: url + token (user optional) - s3: s3Bucket + s3Region + s3AuthenticationType, plus either (s3AccessKeyId + s3SecretAccessKey) for 'accesskey' auth or s3RoleArn for 'rolearn' auth. Call tailscale_create_aws_external_id first when using 'rolearn'.
tailscale_delete_log_stream_config logType
Delete a log streaming configuration. Logs will stop being sent to the configured destination.
tailscale_get_log_stream_status logType
Get the status of log streaming for a specific log type. Shows whether logs are being delivered successfully.
tailscale_create_aws_external_id reusable
Create or get the AWS external ID Tailscale presents when assuming your IAM role for S3 log streaming. Put it in the role trust policy's sts:ExternalId condition, then check it with tailscale_validate_aws_trust_policy.
tailscale_validate_aws_trust_policy externalId, roleArn
Validate that an AWS IAM role trust policy is correctly configured with the Tailscale external ID. Use this after setting up the IAM role for S3 log streaming.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=20.11.0 |
| Source | github.com/YawLabs/tailscale-mcp |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-K//yA/hAKHx7tPgMU6A2eduGllydPGsymWXeg398R+qf6jmg+JzF7yf9XB3eYhDRKxmAUnZrxfrtrO0nrRsDAQ== |
Versions reported
| Version | Run | Result | Tools |
|---|---|---|---|
| 0.23.4 | 2026-11-16 | Starts with no setup | 98 |
| 0.23.2 | 2026-11-12 | Starts with no setup | 98 |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40yawlabs/tailscale-mcp)
New version out? Ask for a fresh report.