Website Scraper MCP Server
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 |
|---|---|
| scrape-to-markdownD | – |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'scrape-to-markdown' stands alone with no other tools to confuse it with.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'scrape-to-markdown' follows a clear verb-noun pattern, and there are no other tools to deviate from this pattern.
A single tool for a 'Website Scraper MCP Server' is too few for the apparent scope, as scraping typically involves multiple operations like configuring, parsing, or handling errors. This minimal set feels incomplete and thin for the domain.
The tool set is severely incomplete for a scraping server. It lacks essential operations such as fetching URLs, handling different content types, error management, or data extraction beyond markdown. This single tool creates significant gaps that will cause agent failures in real-world scraping tasks.