Skip to main content
Glama
zcaceres

Fetch MCP Server

by zcaceres

fetch_html

Retrieve website HTML content directly from URLs for web scraping, data extraction, or content analysis purposes.

Instructions

Fetch a website and return its unmodified contents as HTML

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL of the website to fetch
headersNoOptional headers to include in the request
max_lengthNoMaximum number of characters to return (default: 5000)
start_indexNoStart content from this character index (default: 0)

Implementation Reference

  • Core handler function that fetches HTML content using _fetch, applies length limits, and formats the response for MCP.
    static async html(requestPayload: RequestPayload) {
      try {
        const response = await this._fetch(requestPayload);
        let html = await response.text();
        
        // Apply length limits
        html = this.applyLengthLimits(
          html, 
          requestPayload.max_length ?? 5000, 
          requestPayload.start_index ?? 0
        );
        
        return { content: [{ type: "text", text: html }], isError: false };
      } catch (error) {
        return {
          content: [{ type: "text", text: (error as Error).message }],
          isError: true,
        };
      }
    }
  • src/index.ts:31-55 (registration)
    Tool registration in ListToolsRequest handler, defining name, description, and input schema.
      name: "fetch_html",
      description: "Fetch a website and return its unmodified contents as HTML",
      inputSchema: {
        type: "object",
        properties: {
          url: {
            type: "string",
            description: "URL of the website to fetch",
          },
          headers: {
            type: "object",
            description: "Optional headers to include in the request",
          },
          max_length: {
            type: "number",
            description: `Maximum number of characters to return (default: ${downloadLimit})`,
          },
          start_index: {
            type: "number",
            description: "Start content from this character index (default: 0)",
          },
        },
        required: ["url"],
      },
    },
  • Dispatch logic in CallToolRequest handler that invokes Fetcher.html for 'fetch_html' tool calls.
    if (request.params.name === "fetch_html") {
      const fetchResult = await Fetcher.html(validatedArgs);
      return fetchResult;
    }
  • Zod schema used to validate input arguments for fetch_html and other tools.
    export const RequestPayloadSchema = z.object({
      url: z.string().url(),
      headers: z.record(z.string()).optional(),
      max_length: z.number().int().min(0).optional().default(downloadLimit),
      start_index: z.number().int().min(0).optional().default(0),
    });
  • Private helper method for performing the actual fetch request with security checks and error handling.
    private static async _fetch({
      url,
      headers,
    }: RequestPayload): Promise<Response> {
      try {
        if (is_ip_private(url)) {
          throw new Error(
            `Fetcher blocked an attempt to fetch a private IP ${url}. This is to prevent a security vulnerability where a local MCP could fetch privileged local IPs and exfiltrate data.`,
          );
        }
        const response = await fetch(url, {
          headers: {
            "User-Agent":
              "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36",
            ...headers,
          },
        });
    
        if (!response.ok) {
          throw new Error(`HTTP error: ${response.status}`);
        }
        return response;
      } catch (e: unknown) {
        if (e instanceof Error) {
          throw new Error(`Failed to fetch ${url}: ${e.message}`);
        } else {
          throw new Error(`Failed to fetch ${url}: Unknown error`);
        }
      }
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that content is 'unmodified' and returned 'as HTML', which is helpful, but lacks critical details like error handling, timeout behavior, authentication needs, rate limits, or whether it follows redirects. For a fetch operation with potential network issues, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core functionality ('fetch a website') and specifies the output ('unmodified contents as HTML'). Every word earns its place with zero waste or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (network operation with 4 parameters) and lack of annotations and output schema, the description is incomplete. It doesn't address error cases, performance characteristics, or what happens with malformed HTML. For a fetch tool that could encounter various real-world issues, more context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description doesn't add any meaningful parameter semantics beyond what's in the schema (e.g., it doesn't explain how 'max_length' interacts with HTML structure or whether 'headers' can override defaults). Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('fetch') and resource ('website'), and indicates the output format ('HTML'). It distinguishes from sibling tools by specifying 'unmodified contents as HTML' rather than JSON, markdown, or text formats. However, it doesn't explicitly contrast with siblings beyond the output format.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like fetch_json, fetch_markdown, or fetch_txt. It doesn't mention scenarios where HTML output is preferred over other formats, nor does it discuss any prerequisites or constraints for usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zcaceres/fetch-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server