Fetch

Created By
zcaceresa year ago
Overview

what is Fetch?

Fetch is an MCP server designed to fetch web content in various formats, including HTML, JSON, plain text, and Markdown.

how to use Fetch?

To use Fetch, clone the repository, install dependencies, and run the server using npm start. You can also integrate it with a desktop app by configuring the server settings.

key features of Fetch?

  • Fetches web content using modern fetch API
  • Supports custom headers for requests
  • Provides content in multiple formats: HTML, JSON, plain text, and Markdown
  • Uses JSDOM for HTML parsing and text extraction
  • Uses TurndownService for HTML to Markdown conversion

use cases of Fetch?

  1. Fetching and displaying web content in a desktop application.
  2. Converting web pages to Markdown for documentation purposes.
  3. Extracting JSON data from APIs for further processing.

FAQ from Fetch?

  • What formats can Fetch return?

Fetch can return content in HTML, JSON, plain text, and Markdown formats.

  • Is there a persistent storage option?

No, Fetch is designed to fetch and transform web content on demand without persistent resources.

  • How do I integrate Fetch with my application?

You can integrate Fetch by adding the server configuration to your app's settings.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
zcaceres
Star
-
Language
-
License
-
Category

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