Skip to content
Back to search

proxypin

SkillWorks with Claude CodeGitHub

Open source free capture HTTP(S) traffic software ProxyPin, supporting full platform systems

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/wanghongenpin/proxypin with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/wanghongenpin/proxypin'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/wanghongenpin--proxypin/badge.svg)](/listings/wanghongenpin--proxypin)

HTML

<a href="/listings/wanghongenpin--proxypin"><img src="/api/listings/wanghongenpin--proxypin/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 85 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # ProxyPin MCP Skill
  2. ProxyPin's MCP service exposes captured traffic to AI assistants (Claude Code, Cursor, Codex, Gemini CLI, etc.), so agents can analyze flows, create/edit debugging rules, and replay requests. This skill teaches agents how to use those tools correctly.
  3. ## Connection
  4. - **HTTP** (the user-facing transport): the desktop app listens on `http://127.0.0.1:9127/mcp` (loopback, no auth). Register it with e.g. `claude mcp add proxypin_desktop -s user --transport http "http://127.0.0.1:9127/mcp"`. If port 9127 is already in use the app picks a random free port — use the URL shown in the settings panel rather than hand-copying. No extra bridge process is started, so launching the AI client does not launch ProxyPin.
  5. Prerequisites: desktop ProxyPin is running and the MCP service is enabled. By default tools read the **live capture buffer** (already-captured traffic — ask the user to trigger the request first), but they can also read **saved history sessions** (the History tab): call `list_histories`, then pass `history_id`. The proxy itself does not need to be capturing to analyze a saved session.
  6. ## Tool surface
  7. The service always exposes the full tool set (like Proxyman — there is no read-only mode):
  8. - **Read-only tools**: `get_proxy_status`, `list_histories`, `list_flows`, `search_flows`, `get_flow_detail`, `get_flow_body`, `get_flow_messages`, `get_ssl_proxying_list`, `export_flow_curl`.
  9. - **Write tools**: rule writes (breakpoint / block / map-local / rewrite / script), host filter, replay, system proxy, favorites, clear session, code generation.
  10. Confirm reachability with `get_proxy_status` first; then get the rule index from `list_rules` (every `remove_*` / `update_*` tool takes `index`).
  11. ## Recommended workflow
  12. 1. **Overview**: `list_flows(limit: 20)` for the latest traffic; for aggregates (host/method/status) pull a batch once and count locally — don't call `get_flow_detail` per flow.
  13. - **Saved history**: to analyze an earlier session, call `list_histories` to get its `id`, then pass `history_id` to `list_flows` / `search_flows` / `get_flow_detail` / `get_flow_body` / `export_flow_curl` / `replay_flow` / `generate_code`. The same flow `id` is used; `history_id` only selects the session. WebSocket frames are not saved in history (`get_flow_messages` returns `available:false`).
  14. 2. **Locate**:
  15. - Filter by URL/host/method/status: `list_flows(host:, method:, keyword:, status_from:, status_to:)` (`keyword` matches the full URL; `host` is a substring).
  16. - **Search inside bodies**: `search_flows(keyword: "error 500")` — only searches bodies; binary and >2MB bodies are skipped.
  17. 3. **Drill in**: `get_flow_detail(id:)` for headers (redacted by default) + a truncated body preview; page large bodies with `get_flow_body(id:, side:, offset:, limit:)`; WebSocket frames via `get_flow_messages`.
  18. 4. **Reproduce / change**:
  19. - Get the index with `list_rules`; `update_*` only changes the fields you pass, `remove_*` deletes, `create_*` adds.
  20. - Debug a single request: `replay_flow(id:)` to replay; `send_request(curl:)` to fire a new one.
  21. - Export code: `export_flow_curl(id:)` / `generate_code(id:, language:)` (curl/fetch/python).
  22. 5. **Clean up**: disable or delete temporary rules you created, so they don't affect real traffic.
  23. ## Rewrite rules — the most used feature
  24. Rewrite (重写) is ProxyPin's primary debugging rule type. MCP exposes it through generic tools plus the redirect helpers:
  25. - **List / detail**: `list_rules` → `rewrites` category for indices; `get_rewrite_detail(index)` returns the full rule (type, url, enabled, method) and its operations.
  26. - **Create**: `create_rewrite(url, type?, name?, method?, enabled?, operations)` — `type` ∈ `requestUpdate` / `responseUpdate` / `requestReplace` / `responseReplace` (omit to infer from the ops). `operations` is a list; each op has `op` plus fields:
  27. - header / body edits: `addHeader`, `updateHeader`, `removeHeader`, `updateBody` → fields `key`, `value`, `use_regex`
  28. - query params (request only): `addQueryParam`, `updateQueryParam`, `removeQueryParam` → `key`, `value`, `use_regex`
  29. - full replace: `replaceRequestLine` (`method`, `path`, `query`); `replaceRequestHeader` / `replaceResponseHeader` (`headers`); `replaceRequestBody` / `replaceResponseBody` (`body`, `body_type`); `replaceResponseStatus` (`status_code`)
  30. - **Update**: `update_rewrite(index, url?, name?, method?, enabled?, operations?)` — passing `operations` replaces the whole list.
  31. - **Redirect** (map remote): `create_redirect(url, target_url)` / `update_redirect(index, ...)`.
  32. - **Remove / toggle**: `remove_rewrite_rule(index)` deletes a rule; `remove_rewrite_rule(enabled: false)` disables rewriting globally.
  33. Type constraints: one rule = one type. `requestUpdate` may combine header + body + query ops; `responseUpdate` only header/body ops; `requestReplace` / `responseReplace` only their replace ops. Don't mix request and response ops in one rule — create two rules.
  34. Common patterns:
  35. - "Make X point to Y" → `create_redirect` / `update_redirect` with a `target_url`.
  36. - "Inject a debug header / edit a body value" → `create_rewrite` with `addHeader` / `updateBody`, verify with `replay_flow`.
  37. ## Scripts
  38. ProxyPin lets you run JavaScript on matching request/response:
  39. - Read a script before editing it: `get_script_detail(index)` returns name, urls, enabled, remoteUrl and the full JS body; `list_rules` → `scripts` gives the indices.
  40. - Create: `create_script(urls, name?, script?, remote_url?, enabled?)` — omit `script` to use the starter template; `get_script_template` returns it.
  41. - Update: `update_script(index, urls?, script?, name?, enabled?, remote_url?)` — only the fields you pass change.
  42. - Remove / toggle: `remove_script(index)` or `remove_script(enabled: false)`.
  43. Remote scripts (`remote_url`) are fetched from a URL at runtime; `get_script_detail` returns the fetched/cached body.
  44. ## Host filter
  45. Control which hosts are captured:
  46. - `list_hosts` — patterns + enabled state for whitelist/blacklist.
  47. - `add_host(list: whitelist|blacklist, pattern)` / `remove_host(list, pattern)` — `*` is a wildcard, e.g. `*.example.com`.
  48. - `set_hosts_enabled(list, enabled)`.
  49. Semantics: when the whitelist is enabled, only whitelisted hosts are captured; when the blacklist is enabled, blacklisted hosts are skipped.
  50. ## Privacy & security
  51. - Redaction is on by default for `Authorization` / `Cookie` / `Set-Cookie`. Do **not** talk users into disabling redaction to grab production secrets — if a value is truly needed, have the user confirm it in the ProxyPin UI.
  52. - Binary bodies return only `mimeType/size/sha256`, never inline content.
  53. - `clear_session` is destructive — confirm with the user before calling.
  54. ## Boundaries
  55. - MCP operates only on rules ProxyPin supports: breakpoints, blocks, map-local, rewrites/redirects, JS scripts. Don't invent anything.
  56. - The **live** capture buffer keeps the most recent 1000 flows; older ones are dropped. If `get_flow_detail` on the live buffer returns `Flow not found`, either ask the user to re-trigger the request or look in `list_histories` — captured sessions are persisted and do not expire that way.
  57. - `history_id` is a stable id (the session's filename timestamp), not a list index. The in-memory history cache is a small LRU: evicted sessions are re-read from disk automatically, so a flow "not found" from history only happens if the session file itself was deleted.
  58. - Tool results are JSON text — `jsonDecode` before reading fields.
README.md · README · 50 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # ProxyPin
  2. English | [中文](README_CN.md)
  3. ## Open source free traffic capture HTTP(S),Support Windows、Mac、Android、IOS、Linux Full platform system
  4. You can use it to intercept, inspect & rewrite HTTP(S) traffic, Support capturing Flutter app traffic, ProxyPin is based on Flutter develop, and the UI is beautiful
  5. and easy to use.
  6. ## Features
  7. * Mobile scan code connection: no need to manually configure WiFi proxy, including configuration synchronization. All terminals can scan codes to connect and forward traffic to each other.
  8. * Domain name filtering: Only intercept the traffic you need, and do not intercept other traffic to avoid interference with other applications.
  9. * Search: Search requests according to keywords, response types and other conditions
  10. * Script: Support writing JavaScript scripts to process requests or responses.
  11. * Request Rewrite: Support redirection, support replacement of request or response message, and can also modify request or response according to the increase.
  12. * Request Mapping: Do not request remote services, use local configuration or scripts for response
  13. * Request Decryption: Configure AES decryption key to automatically decrypt HTTP message body
  14. * Request Blocking: Support blocking requests according to URL, and do not send requests to the server.
  15. * History: Automatically save the captured traffic data for easy backtracking and viewing. Support HAR format export and import.
  16. * Others: Favorites, toolbox, common encoding tools, as well as QR codes, regular expressions, etc.
  17. **Mac will prompt untrusted developers when first opened, you need to go to System Preferences-Security & Privacy-Allow any source.**
  18. ## Sponsors
  19. If ProxyPin is helpful to you, you are welcome to support us in the following ways to help the project develop in the long term:
  20. * [Buy Me A Coffee](https://buymeacoffee.com/proxypin)
  21. * [AFDIAN](https://afdian.com/a/proxypin)
  22. * Submit feedback and suggestions to help us improve
  23. * Contribute code or documentation to the project
  24. **Your support will be used for project maintenance, feature development, and user experience optimization. Thank you very much!**
  25. ## Downloads
  26. Github Releases: https://github.com/wanghongenpin/proxypin/releases
  27. iOS App Store:https://apps.apple.com/app/proxypin/id6450932949
  28. Android Google Play:https://play.google.com/store/apps/details?id=com.network.proxy
  29. TG: https://t.me/proxypin_en
  30. **We will continue to improve the features and experience, as well as optimize the UI.**
  31. <img alt="image" width="580px" height="420px" src="https://github.com/user-attachments/assets/6c1345ab-c95c-415d-ac59-470c764b59a2">.<img alt="image" height="500px" src="https://github.com/user-attachments/assets/3c5572b0-a9e5-497c-8b42-f935e836c164">
  32. ### Powered by
  33. [![JetBrains logo.](https://resources.jetbrains.com/storage/products/company/brand/logos/jetbrains.svg)](https://jb.gg/OpenSource)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.