MCP server for Reqable local capture data
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":"reqable-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.
# Reqable MCP Server    Reqable MCP Server exposes local Reqable capture traffic to MCP clients (Windsurf/Cursor/Claude/Codex). Default architecture is local-only: 1. Reqable posts HAR(JSON) to `http://127.0.0.1:18765/report`. 2. Optional incremental WebSocket events can be posted to `http://127.0.0.1:18765/ws/events`. 3. `reqable-mcp` normalizes and stores requests/messages in local SQLite. 4. MCP tools query local data only (no cloud relay by default). Docs: [English](README.md) | [中文](README_CN.md) ## Features - Local-first, privacy-first ingest path. - Real-time ingest via Reqable Report Server. - HAR file import fallback for missed sessions. - HTTP request query/search/domain stats/API analysis. - WebSocket session/message parsing for HAR entries carrying message-frame extensions. - Cross-platform runtime (macOS / Linux / Windows with Python 3.10+). ## Prerequisites 1. Install and open Reqable. 2. Configure Reqable Report Server to post to `http://127.0.0.1:18765/report`. 3. Ensure Node.js (for `npx`) and `uv` (for `uvx`) are available. ## Installation ### Run via npx (recommended) ```bash npx -y reqable-mcp@latest ``` ### Local development ```bash uv run reqable-mcp ``` ## MCP Client Configuration ```json { "mcpServers": { "reqable": { "command": "npx", "args": ["-y", "reqable-mcp@latest"] } } } ``` ## Reqable Report Server Setup Use these values in Reqable "Add Report Server": 1. Name: `reqable-mcp-local` 2. Match rule: `*` (or your target domains) 3. Server URL: `http://127.0.0.1:18765/report` 4. Compression: `None` (or keep consistent with your receiver) After saving, generate traffic and call `ingest_status` to verify incoming payload count. Important note: `reqable-mcp` still uses HTTP-only ingest transport (no…
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.