MCP Server for ProxyPin - Expose HTTP capture data to AI development tools
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"proxypin-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# ProxyPin MCP Server    [](https://lobehub.com/mcp/elonjask-proxypin-mcp) ProxyPin MCP Server is based on the Model Context Protocol (MCP). It works with the open source project [ProxyPin](https://github.com/wanghongenpin/proxypin) to expose your local capture history to MCP-capable clients. Docs: [English](README.md) | [中文](README_CN.md) ## Features - Read local ProxyPin history (HAR) - List/search/detail tools for captured requests - API structure analysis and code generation - Works with mainstream MCP clients (Windsurf / Cursor / Claude Desktop / Codex) ## Prerequisites 1. Install and open ProxyPin 2. In ProxyPin History settings, enable “Cache Date” (required) 3. Ensure some capture history exists 4. Node.js (for `npx`) and `uv` (launcher supports both `uvx` and `uv tool run`) ## Installation ### Run with npx ```bash npx -y proxypin-mcp@latest ``` The NPX bridge tries `uvx` first, then automatically falls back to `uv tool run`. ## Usage Add the following configuration to your MCP client configuration file: ```json { "mcpServers": { "proxypin": { "type": "stdio", "command": "npx", "args": ["-y", "proxypin-mcp@latest"] } } } ``` > [!TIP] > If your client does not support `type`, remove the field. ## Environment Variables | Variable | Description | Default | |---|---|---| | `PROXYPIN_DATA_DIR` | ProxyPin history directory | auto-detect | | `PROXYPIN_HAR_LIMIT` | max HAR files scanned | `50` | | `PROXYPIN_MAX_BODY_SIZE` | max body bytes kept | `102400` | ## Available Tools ### list_requests List recent captured requests. Parameters: - `limit` (int, optional, default 20) - `detail` (string: `summary` | `key` | `full`) - `domain` …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.