Contents

Documentation

NetPeek documentation

Product documentation for NetPeek on iPhone: Packet Tunnel capture, HTTPS inspection, rewrite, replay, and MCP.

NetPeek is a local network debugger on iPhone. It captures HTTP and HTTPS device-wide through a Packet Tunnel, decrypts TLS with a device-local root CA after explicit trust, and rewrites traffic without changing the app under test. Capture data stays on the device unless you enable a local MCP service and hand its token to a client you trust.

Capture is a local VPN configuration. There is no computer requirement for capture, HTTPS inspection, rewrite, scripts, or replay.

What this documentation covers

iPhone pages cover on-device capture, the MITM host list, Simple and Expert rewrite, scripts, replay, MCP, and rule sharing.

  • On-device capture — start the Packet Tunnel, read Recent Requests, filter, favorite, and export.
  • HTTPS inspection — install the CA profile, enable full trust, and add MITM hosts.
  • Rewrite and mock — Simple mode or the expert DSL: headers, bodies, mock, block, redirect, Map Local.
  • Scripts and constants — JavaScript in the tunnel when a rule is not enough.
  • Replay — edit and resend a captured request.
  • MCP — off-by-default Bearer-authenticated local service for trusted desktop clients.
  • Sharing rules — share, import, and push-update rewrite rules.

iPhone surfaces

SurfaceRole
Start CaptureLocal VPN capture; Recent Requests list.
HTTPS / MITM listOn-device CA profile, full trust, host decrypt/exclude.
RewriteSimple intents and expert DSL (headers, body, mock, block, redirect, Map Local).
Scripts / ConstantsJavaScript in the tunnel; reusable values.
ReplayEdit and resend a captured request.
MCPOff-by-default Bearer-authenticated local service for desktop clients.
SharingShare, import, and push-update rewrite rules.
  1. Tap Start Capture, allow the VPN, install and fully trust the CA profile, add MITM hosts, then open Recent Requests.
  2. Rewrite traffic with Simple mode or the expert DSL; use scripts only when a rule is not enough.
  3. Enable MCP only when a trusted client on the same LAN or USB link needs read access.