What problem does it solve? Local development servers, webhook receivers, and MCP endpoints are unreachable from the public internet, blocking webhook callbacks, remote demos, and cross-machine integrations. This Skill creates a public HTTPS URL for any local port using only the stock SSH client, with no daemon or binary installation required. ## Core Features & Use Cases - Zero-Install SSH Tunnels: Connect to a.pinggy.io over SSH port 443 to get a public pinggy.link URL for any local port, with no signup on the free tier. - Access Control Flags: Gate tunnels with HTTP Basic auth, bearer tokens, IP whitelists, CORS headers, and forced HTTPS via username keywords. - Ready-Made Recipes: Includes end-to-end patterns for receiving webhook callbacks, exposing MCP servers over HTTP, sharing local LLM endpoints (Ollama/vLLM), and password-protected dev server demos. - Use Case: You need Stripe to POST webhook events to your laptop during local testing. Start the capture server, launch a bearer-token-gated Pinggy tunnel, parse the public URL from the log, and hand it to Stripe. ## Quick Start Ask the agent to expose local port 8000 to the internet with a Pinggy tunnel and return the public HTTPS URL.
