# RevSheller > RevSheller runs on Cloudflare's edge and does two things. HTTP tunnels expose a local web server at a public https URL, for webhook testing, sharing a dev server, demos and mobile testing (registered accounts only). The shell relay is a hosted reverse and forward shell listener: create a session, run one payload on a machine you are authorized to test, and get an interactive shell in the browser or over an authenticated WebSocket, with no listener, VPS, or port forwarding to run yourself. Status: free beta. All features are unlocked for every registered account. During the beta, each account gets 2 tunnels at a time, 10 GiB of tunnel traffic a month, and up to 8 hours per tunnel; per-plan tunnel limits after the beta are on https://revsheller.com/pricing#tunnel-limits. Paid plans (Pro and Pro Plus) are planned for after the beta and are not final: Pro is planned at $3/mo or $12/yr, Pro Plus at $5/mo or $48/yr, and Free is a limited tier (1 session, 5 minute idle timeout) for trying it out. Beta users will get a launch discount when paid plans start. Agent, API, and MCP access is free during the beta and planned as Pro Plus only afterwards. An MCP server for AI agents is live at https://revsheller.com/mcp. ## Intended use For authorized security testing only: your own systems, CTFs, training labs, and engagements with explicit written permission. This applies equally to AI agents and automation; the account holder is responsible for what an agent connects to. Do not use RevSheller against systems you do not own or have permission to test. Report misuse at /abuse. ## Docs - [Tunnel documentation](https://revsheller.com/api-docs#tunnels): client quickstart and options, REST endpoints, MCP tools, limits, the visitor warning page, and the cookie caveat - [API documentation](https://revsheller.com/api-docs): endpoints, auth, WebSocket protocol, and an "For AI agents" section - [About](https://revsheller.com/about): what it is, how it works, limitations - [Pricing](https://revsheller.com/pricing): free beta and planned plans - [Terms of Service](https://revsheller.com/terms) - [Feedback](https://revsheller.com/feedback): report a bug or request a feature - [Report abuse](https://revsheller.com/abuse) - [Privacy Policy](https://revsheller.com/privacy) ## Guides - [Guides index](https://revsheller.com/guides/): all practical guides, for tunnels and for CTFs and labs - [Expose localhost and share a dev server](https://revsheller.com/guides/expose-localhost-share-dev-server): a public https URL for a local server, Host headers for Vite and webpack, WebSockets, phones - [Test Stripe webhooks locally](https://revsheller.com/guides/test-stripe-webhooks-locally): point a Stripe or GitHub webhook at your laptop and verify signatures on the raw body - [Give localhost a public https URL](https://revsheller.com/guides/localhost-public-url): what tunnels do, the beta limits, and what they do not cover - [Catch a reverse shell without a VPS](https://revsheller.com/guides/reverse-shell-listener-without-vps): create a session, pick a payload and connect, with no VPS or port forwarding - [Hosted listener for TryHackMe and HackTheBox](https://revsheller.com/guides/tryhackme-hackthebox-listener): what works from lab networks, what to do when the target has no internet, and the limits - [Give Claude shell access to lab targets via MCP](https://revsheller.com/guides/ai-agent-shell-mcp): connect Claude Code, Claude Desktop or another MCP client with an API key - [Callbacks behind NAT, CGNAT or campus Wi-Fi](https://revsheller.com/guides/listener-behind-nat-cgnat): why port forwarding fails and how a hosted listener over port 443 avoids it - [revsheller vs nc -lvnp](https://revsheller.com/guides/netcat-listener-alternative): an honest comparison with a local netcat listener, including when plain nc is better - [Windows PowerShell listener with ConPTY](https://revsheller.com/guides/windows-reverse-shell-listener-powershell): the pure-PowerShell client, what ConPTY adds and its limits ## API in brief Base URL: https://revsheller.com/api. Authenticate with `Authorization: Bearer rsh_...` (API key, created while signed in on /account). - `POST /api/session` creates a session (reverse by default; `{"mode":"forward","targetHost":"...","targetPort":N}` for forward). Returns `session.id`, `operatorSecret`, `targetSecret`, `payloads`, `operatorUrl`. - `GET /api/session/{id}` with `Authorization: Bearer op_...` returns session state. - `DELETE /api/session/{id}` with `Authorization: Bearer op_...` tears the session down. - `POST /api/payload/generate` generates a payload for a session (`type`, `slug`, `token`, optional `variant`, `encoding`). - Operator shell I/O: WebSocket to `operatorUrl` (`wss://{id}.revsheller.com/ws/operator`) with the header `Sec-WebSocket-Protocol: token.op_...`. There is no HTTP operator endpoint. - `GET /api/config` returns `beta` and `billingEnabled`. ## MCP server Remote MCP over Streamable HTTP (stateless, JSON): `POST https://revsheller.com/mcp` with `Authorization: Bearer rsh_...`. Setup guide: https://revsheller.com/api-docs#mcp - Claude Code: `claude mcp add --transport http revsheller https://revsheller.com/mcp --header "Authorization: Bearer rsh_..."` - Claude Desktop: `npx -y mcp-remote@0.16.7 https://revsheller.com/mcp --header "Authorization: Bearer ${RSH_KEY}"` Tools: `create_session`, `get_target_command`, `session_status`, `send_input`, `read_output`, `run_command`, `list_sessions`, `close_session`. Workflow: create_session, run the returned target command on a machine you are authorized to test, poll session_status until targetConnected, then run_command. Only sessions created by the same account are reachable. Free during the beta (max 5 concurrent sessions); Pro Plus after. Run one run_command at a time per session; output buffers are 256 KiB and can reset after hibernation. Shell I/O is relayed live and is not stored. ## HTTP tunnels Expose a local web server at a public https URL: `(curl -fsSL https://revsheller.com/tn.sh || wget -qO- https://revsheller.com/tn.sh) | RSH_API_KEY=rsh_... sh -s -- http 3000` (PowerShell: `$env:RSH_API_KEY="rsh_..."; & ([scriptblock]::Create((irm https://revsheller.com/tn.ps1))) http 3000`). The script downloads a small native client (macOS, Linux, Windows; no runtime needed) checked against a pinned SHA-256. With Node.js 22+, `curl -fsSL https://revsheller.com/tn | node - http 3000` also works. Needs an API key from https://revsheller.com/account. Manage tunnels at https://revsheller.com/tunnels. - REST: `POST /api/tunnels` (optional `{"name"}` for a reserved name), `GET /api/tunnels`, `DELETE /api/tunnels/:id`, `GET|POST /api/tunnel-names`, `DELETE /api/tunnel-names/:name`. - MCP tools: `tunnel_create` (port, name?) returns `url` and a `connect_command` for the user to run with their own key (`--tunnel ` attaches to the created tunnel); `tunnel_list`; `tunnel_delete`. No key or secret is ever returned. - Visitors' browsers see a one-time warning page; non-HTML clients and `X-RevSheller-Skip-Warning: 1` skip it. Apps receive `X-Forwarded-For`. No phishing, malware or C2; reported tunnels are suspended.