Http Rquest

Created By
xxxbriana year ago
Overview

what is Http Rquest?

Http Rquest is a Model Context Protocol (MCP) server that enhances HTTP request capabilities for language models like Claude, enabling realistic browser emulation and advanced content handling.

how to use Http Rquest?

To use Http Rquest, install it via pip or run it using uv. Configure it for your application by adding the server settings in JSON format, and then utilize the provided HTTP request tools to interact with web resources.

key features of Http Rquest?

  • Complete support for various HTTP methods (GET, POST, etc.)
  • Accurate browser fingerprinting to bypass anti-bot measures
  • Automatic handling of large responses and conversion of HTML/PDF to Markdown
  • Support for multiple authentication methods
  • Secure connections using BoringSSL

use cases of Http Rquest?

  1. Interacting with web APIs while mimicking real browser behavior.
  2. Converting web content (HTML/PDF) into a format suitable for language models.
  3. Bypassing bot detection mechanisms for web scraping tasks.

FAQ from Http Rquest?

  • What is the purpose of Http Rquest?

Http Rquest is designed to facilitate advanced HTTP requests for language models, improving their ability to interact with web content.

  • How do I install Http Rquest?

You can install Http Rquest using pip with the command pip install mcp-rquest.

  • Can I use Http Rquest for web scraping?

Yes, Http Rquest is built to help bypass common anti-bot measures, making it suitable for web scraping.

Server Config

{
  "mcpServers": {
    "http-rquest": {
      "command": "uvx",
      "args": [
        "mcp-rquest"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
xxxbrian
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago