Skip to main content
Glama
aelaguiz

URL Fetch MCP

by aelaguiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
fetch_urlC

Fetch content from a URL and return it as text.

This tool allows Claude to retrieve content from any accessible web URL.
The content is returned as text, making it suitable for HTML, plain text,
and other text-based content types.
fetch_imageC

Fetch an image from a URL and return it as an image.

This tool allows Claude to retrieve images from any accessible web URL.
The image is returned in a format that Claude can display.
fetch_jsonA

Fetch JSON from a URL, parse it, and return it formatted.

This tool allows Claude to retrieve and parse JSON data from any accessible web URL.
The JSON is prettified for better readability.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

TDQS

A3.5/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: fetch_image retrieves images, fetch_json retrieves and parses JSON, and fetch_url retrieves general text content. The descriptions reinforce these distinctions, making it easy for an agent to select the right tool based on the expected response format.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with 'fetch_' prefix and descriptive suffixes (image, json, url). This predictable naming scheme enhances usability and reduces cognitive load for agents.

Tool Count4/5

Three tools is a reasonable count for a URL fetching server, covering the main content types (images, JSON, text). It's slightly lean but well-scoped; adding tools for other formats like XML or binary data could improve completeness without being excessive.

Completeness4/5

The tools cover the core use cases for fetching web content: images, JSON, and general text. A minor gap exists for other structured data formats like XML or raw binary files, but agents can work around this by using fetch_url for text-based alternatives or requesting enhancements.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources