mult-fetch-mcp-server

Created By
lmcc-deva year ago
A versatile MCP-compliant web content fetching tool that supports multiple modes (browser/node), formats (HTML/JSON/Markdown/Text), and intelligent proxy detection, with bilingual interface (English/Chinese).
Overview

What is Mult Fetch Mcp Server?

Mult Fetch Mcp Server is a versatile MCP-compliant web content fetching tool that supports multiple modes (browser/node), formats (HTML/JSON/Markdown/Text), and intelligent proxy detection, with a bilingual interface (English/Chinese).

How to use Mult Fetch Mcp Server?

To use the server, install it via npm or Smithery, configure it according to your environment, and then run it to fetch web content using various commands.

Key features of Mult Fetch Mcp Server?

  • Supports multiple fetching modes: browser and Node.js.
  • Fetches content in various formats: HTML, JSON, Markdown, and plain text.
  • Intelligent proxy detection and bilingual support.
  • Modular design for easy maintenance and extension.

Use cases of Mult Fetch Mcp Server?

  1. Web scraping for data extraction.
  2. Fetching content for AI assistants.
  3. Integrating with applications that require web content.

FAQ from Mult Fetch Mcp Server?

  • Can I use it without installation?

Yes! You can run it directly using npx without installation.

  • Is it available in multiple languages?

Yes! It supports both English and Chinese.

  • How do I configure proxy settings?

You can specify proxy settings in the request parameters or use environment variables.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
lmcc-dev
Star
2
Language
TypeScript
License
MIT license

Recommend Servers

View All
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.

8 hours ago