Skip to main content
Glama
sposer

mcp-fetch

by sposer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_FETCH_PORTNoPort for HTTP transport mode8000
MCP_FETCH_CACHE_DIRNoDirectory for storing cache files./.mcp-fetch-cache
MCP_FETCH_TRANSPORTNoTransport mode: stdio or http
MCP_FETCH_TTL_SECONDSNoTime-to-live for cached items in seconds1800
MCP_FETCH_MAX_CACHE_BYTES_TOTALNoMaximum total cache size in bytes (512 MiB)536870912
MCP_FETCH_MAX_SINGLE_TRANSFER_BYTESNoMaximum size for a single transfer in bytes (200 MiB)209715200
MCP_FETCH_WAIT_CHUNK_TIMEOUT_SECONDSNoTimeout for waiting on chunk data in seconds30

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tasks
{
  "list": {},
  "cancel": {},
  "requests": {
    "tools": {
      "call": {}
    },
    "prompts": {
      "get": {}
    },
    "resources": {
      "read": {}
    }
  }
}
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
fetch_pageA

Fetch/Crawl a dynamic web page and convert to Markdown (supports JavaScript).

Use this tool to:

  1. Crawl/Scrape content from modern web pages (React, Vue, etc.)

  2. Get full page content after JavaScript rendering

  3. Download large page content via chunked streaming

Protocol:

  1. Start: Provide url (required) → returns transfer_id + first chunk

  2. Continue: Provide transfer_id + offset → returns next chunk

Args:

  • url: Target http(s) URL (required for phase 1)

  • to_markdown: Convert HTML to Markdown (default: True)

  • wait_selector: CSS selector to wait for before capturing content

  • Optional: headers, query, timeout_ms, max_scrolls, min/max_delay_ms, proxy/pool, user_agent, chunk_bytes

  • Cursor: transfer_id, offset (for phase 2)

Returns:

  • Chunk: chunk_text or chunk_base64, next_offset, done, truncated

  • Meta: transfer_id, status, headers, final_url, content_type, elapsed_ms

  • Size: available_bytes, total_bytes

http_requestA

Perform a generic HTTP request (GET, POST, PUT, DELETE, etc) for APIs or raw data.

Use this tool when:

  1. You need to call a REST API (JSON/XML)

  2. You need to use HTTP methods other than GET (POST, PUT, DELETE)

  3. You want to download a raw file without rendering (PDF, Image, etc)

Note: For GET requests to renderable web pages, prefer fetch_page which handles dynamic content and JavaScript.

Protocol:

  1. Start: Provide url (required) → returns transfer_id + first chunk

  2. Continue: Provide transfer_id + offset → returns next chunk

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: fetch_page is for scraping dynamic web pages with JavaScript rendering and converting to Markdown, while http_request is for generic HTTP requests to APIs or raw files. The descriptions explicitly note when to use each tool, eliminating any overlap or confusion.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern (fetch_page and http_request) with clear, descriptive names that match their functions. There are no deviations or mixed conventions in the naming style.

Tool Count3/5

With only 2 tools, the server feels thin for a general-purpose HTTP fetching domain, as it might lack coverage for specialized scenarios like WebSocket handling or advanced caching. However, the tools cover core use cases (dynamic page scraping and generic HTTP requests), making it borderline but functional.

Completeness4/5

The tool set covers essential HTTP operations for web scraping and API interactions, with clear guidance on when to use each tool. Minor gaps exist, such as no dedicated tools for WebSocket connections or batch request handling, but agents can likely work around these using the provided tools.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources