Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"tailscale-mcp-echo": {
"args": [
"mcp-remote",
"https://ts-mcp-echo.yourtailnetname.ts.net/mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Create an identiy aware MCP server that runs inside your private Tailscale network (Tailnet). This example leverages identity headers that are passed through to applications running behind tailscale serve.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'mcp-remote' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
mcp-remote exposed to OS command injection via untrusted MCP server connections
mcp-remote is exposed to OS command injection when connecting to untrusted MCP servers due to crafted input from the authorization_endpoint response URL
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in security / devops
MCP server for using the GitLab API
An evil MCP server used for redteam testing
Proof primitive for AI agents on MultiversX. Anchor file hashes on-chain as verifiable proofs.
Enhanced MCP server for GitLab: group projects listing and activity tracking
MCP Security Weekly
Get CVE alerts and security updates for Tailscale Mcp Echo and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Create an identiy aware MCP server that runs inside your private Tailscale network (Tailnet). This example leverages identity headers that are passed through to applications running behind tailscale serve.
Using this as starting point you can create MCP servers that are identity aware (with access to the logged in user's email) and can access internal APIs or services on thier behalf.
.env file in the root of this project with the following format: TS_AUTHKEY=tskey-auth-...docker compose up to start the server.This will spin up two containers. The MCP server and a Tailscale container running tailscale serve as a proxy to your tailnet.
If you have an MCP Client that supports direct access to Streaming HTTP MCP servers, then you should be able to connect to the server by pointing it to https://ts-mcp-echo.yourtailnetname.ts.net/mcp.
Claude desktop does not currently support remote MCP servers (only stdio), but you can use the mcp-remote tool (or any other proxy) to connect to it.
Install mcp-remote with npm install -g mcp-remote
Add the following configuration to your claude_desktop_config.json file:
{
"mcpServers": {
"tailscale-remote-echo-example": {
"command": "npx",
"args": [
"mcp-remote",
"https://ts-mcp-echo.yourtailnetname.ts.net/mcp"
]
}
}
}
You can find your tailnet name by visiting the Tailscale admin console DNS page.
Restart Claude Desktop.
You should now see a new MCP server called tailscale-remote-echo-example with a greet tool.
Ask Claude Who am I logged into my tailnet as? allow the tool, and wait for the response!