Skip to main content
Glama
mcp-webfetch

mcp-webfetch

by Mahgal

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_WEBFETCH_FORCE_STDIONoSet to 1 to force the built-in minimal JSON-RPC-over-stdio fallback implementation instead of using the official MCP Python SDK.

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
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
fetch_urlA

Fetch a web page and return its content as clean Markdown (title, headings, paragraphs and links preserved). Times out after 10s and rejects non-HTML or oversized responses.

extract_linksA

Fetch a web page and return the de-duplicated list of http/https links it contains, as a JSON array.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 2 tools

Disambiguation4/5

The two tools differ mainly in output shape: fetch_url returns Markdown while extract_links returns a JSON link array. There is mild overlap because fetch_url explicitly preserves links, so an agent could plausibly get links via either tool, but the descriptions make the intended split reasonably clear.

Naming Consistency5/5

Both names follow a strict verb_noun snake_case pattern (fetch_url, extract_links) with no stylistic deviation. The convention is predictable and immediately readable.

Tool Count3/5

Two tools is thin for a general-purpose web-fetch server; a single narrow utility would be fine, but this surface leaves little room for variation in fetch behavior. It is not bloated, just minimal.

Completeness3/5

The core fetch-and-parse loop is covered, but notable gaps exist: no raw HTML/JSON fetch, no custom headers or method options, and no main-content/text-only extraction. Agents hitting non-HTML endpoints or auth-gated pages have no path forward.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues