XFetch Mcp

Created By
xfetchaia year ago
Fetch on steroids. Allow to retrieve content from any web pages, including those protected by Cloudflare and other security systems.
Overview

What is Xfetch MCP?

Xfetch MCP is an enhanced Model Context Protocol server designed for advanced web content fetching, enabling LLMs to retrieve and process content from various web pages, including those protected by security systems like Cloudflare.

How to use Xfetch MCP?

To use Xfetch MCP, install it via pip or uv, and then utilize the xfetch tool to fetch web content by providing the URL and optional parameters for rendering and content extraction.

Key features of Xfetch MCP?

  • Bypass protection systems to access content from secured websites.
  • JavaScript rendering for dynamic content fetching.
  • CSS selectors for precise content extraction.
  • Dynamic content loading to ensure all content is fetched.
  • Automatic HTML to markdown conversion for easier processing.
  • Chunked reading for long pages.

Use cases of Xfetch MCP?

  1. Fetching content from news articles behind paywalls.
  2. Extracting specific data from e-commerce sites.
  3. Retrieving dynamic content from single-page applications.

FAQ from Xfetch MCP?

  • Can Xfetch MCP fetch content from any website?

Yes, it can fetch content from most websites, including those with security measures.

  • Is there a free version of Xfetch MCP?

Yes, there is a free tier available for limited usage.

  • How do I handle dynamic content?

You can enable JavaScript rendering and set a timeout for dynamic content loading.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
xfetchai
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