Scrapling Fetch MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Name | Description |
|---|---|
| s_fetch_pageA | Fetches a complete web page with pagination support. Retrieves content from websites with bot-detection avoidance. For best performance, start with 'basic' mode (fastest), then only escalate to 'stealth' or 'max-stealth' modes if basic mode fails. Content is returned as 'METADATA: {json}\n\n[content]' where metadata includes length information and truncation status. |
| s_fetch_patternA | Extracts content matching regex patterns from web pages. Retrieves specific content from websites with bot-detection avoidance. For best performance, start with 'basic' mode (fastest), then only escalate to 'stealth' or 'max-stealth' modes if basic mode fails. Returns matched content as 'METADATA: {json}\n\n[content]' where metadata includes match statistics and truncation information. Each matched content chunk is delimited with '॥๛॥' and prefixed with '[Position: start-end]' indicating its byte position in the original document, allowing targeted follow-up requests with s-fetch-page using specific start_index values. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: s_fetch_page retrieves entire web pages with pagination support, while s_fetch_pattern extracts specific content matching regex patterns. Their descriptions explicitly differentiate them, with no overlap in functionality that would cause confusion.
Both tools follow a consistent 's_fetch_' prefix pattern with descriptive suffixes ('page' and 'pattern'), maintaining perfect naming consistency. The snake_case convention is applied uniformly across both tool names.
With only 2 tools, the server feels somewhat thin for a web scraping domain that typically requires more operations like navigation, form handling, or session management. While the tools are well-designed, the limited count may restrict agent capabilities for complex scraping tasks.
The tools cover the core web scraping operations of fetching pages and extracting patterns with bot-detection avoidance. However, there are notable gaps for a complete scraping workflow, such as no tools for navigating between pages, handling authentication, managing sessions, or interacting with dynamic content beyond basic fetching.