tailscale-mcp

Overview Schema Source Related Servers Discussions Admin

Share status

share_status

Read-onlyIdempotent

Inspect active Tailscale Serve/Funnel sessions on this node to view exposed URLs, ports, mount paths, and public exposure status.

Instructions

Report the active Tailscale Serve/Funnel sessions on this node: one entry per endpoint with its URL, serve port, mount path, proxied target, and a public flag that is true when Funnel exposes it to the open internet. publicExposure is true when anything is public.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "share_status"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`active`	Yes
`status`	No	Raw text status, only on CLIs without --json
`endpoints`	Yes
`tcpForwards`	No
`publicExposure`	Yes	True when any endpoint is exposed via Funnel; null if unknown (old CLI)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.4.0Oct 29, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "active": {
+      "type": "boolean"
+    },
+    "endpoints": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "foreground": {
+            "type": "boolean"
+          },
+          "host": {
+            "type": "string"
+          },
+          "httpsPort": {
+            "type": "number"
+          },
+          "path": {
+            "type": "string"
+          },
+          "public": {
+            "type": "boolean"
+          },
+          "scheme": {
+            "enum": [
+              "https",
+              "http"
+            ],
+            "type": "string"
+          },
+          "target": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "targetType": {
+            "enum": [
+              "proxy",
+              "path",
+              "text",
+              "redirect",
+              "unknown"
+            ],
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "url",
+          "host",
+          "httpsPort",
+          "scheme",
+          "path",
+          "target",
+          "targetType",
+          "public",
+          "foreground"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "publicExposure": {
+      "description": "True when any endpoint is exposed via Funnel; null if unknown (old CLI)",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "status": {
+      "description": "Raw text status, only on CLIs without --json",
+      "type": "string"
+    },
+    "tcpForwards": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "foreground": {
+            "type": "boolean"
+          },
+          "port": {
+            "type": "number"
+          },
+          "public": {
+            "type": "boolean"
+          },
+          "target": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "port",
+          "target",
+          "public",
+          "foreground"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "active",
+    "publicExposure",
+    "endpoints"
+  ],
+  "type": "object"
+}

First observedv0.1.0Jul 14, 2026

TDQS

A3.6/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful semantics the annotations cannot convey: results are node-scoped, one entry per endpoint, and 'public' means Funnel exposes the target to the open internet. It does not cover pagination, empty-state behavior, or error conditions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the verb and scope, no filler. Some content restates fields already exposed by the output schema, but the 'public'/'publicExposure' semantics earn their place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the field-by-field enumeration is partly redundant; the description could instead have spent that space on when-to-use versus siblings. Still, for a zero-parameter read tool it gives enough to call correctly and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4 and there is nothing the description could clarify about inputs. No parameter-related gap exists.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb and resource ('Report the active Tailscale Serve/Funnel sessions') plus a scope qualifier ('on this node') that implicitly separates it from tailnet_status. It does not explicitly name or contrast with any sibling, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the read-only 'Report' framing; there is no explicit 'use this when...' statement, no mention of the write siblings (share_port, stop_share), and no guidance on when tailnet_status would be the better call.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server