Skip to main content
Glama
ClearFetch - Unblocked Web & Anti-Bot MCP Server

ClearFetch - Unblocked Web & Anti-Bot MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CLEARFETCH_API_KEYYesYour ClearFetch Live API Key from https://clearfetch.dev/dashboard
CLEARFETCH_API_URLNoClearFetch API Gateway URLhttps://api.clearfetch.dev

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
read_urlA

Read any URL as clean, token-optimized Markdown. Reliably bypasses Cloudflare Turnstile, DataDome, PerimeterX, and anti-bot systems where other scrapers fail with 403 Forbidden.

extract_structured_dataA

Extract strongly-typed JSON matching a strict schema from any webpage, even behind heavy anti-bot protections.

search_and_readA

Search the live web and return clean Markdown content bundles of top results in a single step for AI agent context / RAG.

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 3 tools

Disambiguation5/5

Each tool has a distinct input signature and output shape: read_url takes a URL and returns Markdown, extract_structured_data takes a URL plus schema and returns typed JSON, and search_and_read takes a query and returns bundled results. An agent can pick unambiguously based on whether it has a URL or a query and whether it needs Markdown or schema-conforming JSON.

Naming Consistency5/5

All three names are snake_case and lead with a clear verb (read_, extract_, search_) followed by the object of the action. The pattern is predictable and consistent throughout.

Tool Count4/5

Three tools is on the lean side, but each maps to a genuinely different workflow (raw fetch, schema extraction, discovery+fetch) and none feels redundant. A focused anti-bot fetching server can justify a minimal surface, though one or two more convenience tools would not be out of place.

Completeness4/5

The fetch/extract/search triad covers the core content-acquisition lifecycle for agent context and RAG. The main gap is batch or multi-URL reading (and any crawl/site-traversal capability), which agents must work around by calling the tools repeatedly.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues