Fetch MCP Server with CSS selectors function

Created By
burnworksa year ago
Overview

What is Fetch MCP Server?

Fetch MCP Server is a Model Context Protocol server designed to fetch web content using CSS selectors, enabling LLMs to retrieve and process information from web pages by converting HTML to markdown for easier consumption.

How to use Fetch MCP Server?

To use the Fetch MCP Server, you can either install it via pip or use it with uv. After installation, you can run it as a script or configure it for specific applications by setting up commands in your environment.

Key features of Fetch MCP Server?

  • Fetches web content and converts it to markdown format.
  • Supports CSS selectors for targeted content extraction.
  • Allows customization of user-agent and proxy settings.
  • Provides debugging tools for server inspection.

Use cases of Fetch MCP Server?

  1. Extracting main article content from news websites.
  2. Focusing on specific sections of documentation pages.
  3. Targeting precise content from large web pages for data analysis.

FAQ from Fetch MCP Server?

  • Can I extract content from any website?

Yes, as long as the website allows it and you comply with its robots.txt file.

  • Is there a limit to the amount of content I can fetch?

Yes, you can specify a maximum length for the content returned.

  • How do I customize the server settings?

You can customize settings like user-agent and proxy by adding arguments in the configuration.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
burnworks
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago