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 public HTTP/HTTPS URLs for local ports using only the stock SSH client, with no daemon installation or signup required. ## Core Features & Use Cases - Zero-Install Tunneling: Uses the built-in SSH client to connect to a.pinggy.io and receive a public pinggy.link URL for any local port. - Access Control: Gates 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 demoing dev servers with one-shot passwords. - Use Case: You need Stripe to POST webhook events to your laptop during local testing. The Skill starts a capture server on port 18080, opens a token-gated Pinggy tunnel, parses the public URL from the log, and hands it back for you to register with Stripe. ## Quick Start Ask the agent to expose local port 8000 to the internet with a Pinggy tunnel and give you the public URL.