Skip to content
Back to search

reqable-mcp

MCP server for Reqable local capture data

Safety scan

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

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/elonjask--reqable-mcp/badge.svg)](/listings/elonjask--reqable-mcp)

HTML

<a href="/listings/elonjask--reqable-mcp"><img src="/api/listings/elonjask--reqable-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Run via npx (recommended)

npx -y reqable-mcp@latest

Local development

uv run reqable-mcp

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.

README.md · README · 115 lines

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

  1. # Reqable MCP Server
  2. ![NPM Version](https://img.shields.io/npm/v/reqable-mcp.svg) ![PyPI Version](https://img.shields.io/pypi/v/reqable-mcp.svg) ![GitHub License](https://img.shields.io/github/license/ElonJask/reqable-mcp.svg)
  3. Reqable MCP Server exposes local Reqable capture traffic to MCP clients (Windsurf/Cursor/Claude/Codex).
  4. Default architecture is local-only:
  5. 1. Reqable posts HAR(JSON) to `http://127.0.0.1:18765/report`.
  6. 2. Optional incremental WebSocket events can be posted to `http://127.0.0.1:18765/ws/events`.
  7. 3. `reqable-mcp` normalizes and stores requests/messages in local SQLite.
  8. 4. MCP tools query local data only (no cloud relay by default).
  9. Docs: [English](README.md) | [中文](README_CN.md)
  10. ## Features
  11. - Local-first, privacy-first ingest path.
  12. - Real-time ingest via Reqable Report Server.
  13. - HAR file import fallback for missed sessions.
  14. - HTTP request query/search/domain stats/API analysis.
  15. - WebSocket session/message parsing for HAR entries carrying message-frame extensions.
  16. - Cross-platform runtime (macOS / Linux / Windows with Python 3.10+).
  17. ## Prerequisites
  18. 1. Install and open Reqable.
  19. 2. Configure Reqable Report Server to post to `http://127.0.0.1:18765/report`.
  20. 3. Ensure Node.js (for `npx`) and `uv` (for `uvx`) are available.
  21. ## Installation
  22. ### Run via npx (recommended)
  23. ```bash
  24. npx -y reqable-mcp@latest
  25. ```
  26. ### Local development
  27. ```bash
  28. uv run reqable-mcp
  29. ```
  30. ## MCP Client Configuration
  31. ```json
  32. {
  33. "mcpServers": {
  34. "reqable": {
  35. "command": "npx",
  36. "args": ["-y", "reqable-mcp@latest"]
  37. }
  38. }
  39. }
  40. ```
  41. ## Reqable Report Server Setup
  42. Use these values in Reqable "Add Report Server":
  43. 1. Name: `reqable-mcp-local`
  44. 2. Match rule: `*` (or your target domains)
  45. 3. Server URL: `http://127.0.0.1:18765/report`
  46. 4. Compression: `None` (or keep consistent with your receiver)
  47. After saving, generate traffic and call `ingest_status` to verify incoming payload count.
  48. Important note: `reqable-mcp` still uses HTTP-only ingest transport (no native `ws://` listener), but now supports two HTTP ingest paths: `/report` for HAR/session payload and `/ws/events` for incremental WebSocket events. WebSocket capture works when Reqable payload includes frame data (for example `_webSocketMessages` or event frame objects). Raw entry JSON and raw message JSON are preserved and exposed by WebSocket tools. HAR export/import remains the fallback when live pushes miss frames.
  49. ## Available Tools
  50. - `ingest_status`: ingest server state and counters
  51. - `import_har`: import HAR from file path
  52. - `list_requests`: list recent HTTP/WebSocket handshake requests with filters
  53. - `get_request`: fetch request details by ID (`full` includes `raw_entry`)
  54. - `search_requests`: keyword search in HTTP URL/body/raw uploaded entry (`raw` / `raw_entry`)
  55. - `list_websocket_sessions`: list captured WebSocket sessions
  56. - `list_active_websocket_sessions`: list recently active WebSocket sessions by latest captured frames
  57. - `get_websocket_session`: fetch WebSocket session details and messages by ID (including `raw_entry` and message `raw`)
  58. - `tail_websocket_messages`: incremental fetch by `request_id` + `after_seq` cursor
  59. - `search_websocket_messages`: precise WebSocket message search by keyword, direction, type, opcode, close code, domain, and request ID
  60. - `analyze_websocket_session`: summarize directions, message types, JSON shapes, and close events for a session
  61. - `export_websocket_session_raw`: export the raw uploaded WebSocket entry and raw frame list
  62. - `health_report`: ingest status + WebSocket data quality report
  63. - `repair_websocket_messages`: backfill missing fields from raw frames (supports dry-run)
  64. - `get_domains`: domain-level request statistics
  65. - `analyze_api`: infer API shapes for a domain
  66. - `generate_code`: generate sample client code from captured HTTP request
  67. ## Environment Variables
  68. | Variable | Description | Default |
  69. |---|---|---|
  70. | `REQABLE_INGEST_HOST` | Report receiver host | `127.0.0.1` |
  71. | `REQABLE_INGEST_PORT` | Report receiver port | `18765` |
  72. | `REQABLE_INGEST_PATH` | Report receiver path | `/report` |
  73. | `REQABLE_WS_EVENTS_PATH` | Incremental WebSocket event receiver path | `/ws/events` |
  74. | `REQABLE_DATA_DIR` | Local data directory | platform app data dir |
  75. | `REQABLE_DB_PATH` | SQLite file path | `${REQABLE_DATA_DIR}/requests.db` |
  76. | `REQABLE_MAX_BODY_SIZE` | Max persisted body bytes per request/message | `102400` |
  77. | `REQABLE_MAX_REPORT_SIZE` | Max accepted report payload bytes | `10485760` |
  78. | `REQABLE_MAX_IMPORT_FILE_SIZE` | Max HAR import file bytes | `104857600` |
  79. | `REQABLE_RETENTION_DAYS` | Local retention window | `7` |
  80. | `REQABLE_INGEST_TOKEN` | Optional local auth token | unset |
  81. ## Privacy and Data Retention
  82. - Data stays on local machine in default mode.
  83. - Retention cleanup is applied to local DB records, including WebSocket messages.
  84. - If ingest server is offline, Reqable failed report push is not retried.
  85. ## License
  86. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

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