mcp-server-scraper
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scrape_urlA | Extract clean, readable text content from a URL using Mozilla Readability. Returns title, excerpt, and main content. Best for articles, docs, and blog posts. |
| extract_linksA | Extract all links from a page with their href and anchor text. Resolves relative URLs. Skips anchors and javascript: links. |
| extract_metadataB | Extract page metadata: title, description, Open Graph tags (og:title, og:description, og:image), canonical URL, and favicon. |
| search_pageA | Search for a query string within the page text. Returns matching lines (one per line). Use for finding mentions of a term. |
| scrape_multipleA | Batch scrape multiple URLs. Returns title and excerpt for each. Failures are reported per URL without failing the whole batch. |
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 5 tools
Each tool has a clearly distinct purpose with no overlap: extract_links focuses on hyperlinks, extract_metadata on page metadata, scrape_multiple on batch title/excerpt extraction, scrape_url on full content extraction, and search_page on text search. The descriptions make it easy to differentiate them, preventing misselection.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., extract_links, scrape_url, search_page). The naming is predictable and readable throughout, with no deviations in style or convention.
With 5 tools, this server is well-scoped for web scraping purposes. Each tool earns its place by covering distinct aspects of scraping (links, metadata, batch processing, content extraction, and search), avoiding bloat while providing comprehensive functionality.
The tool set covers core web scraping workflows effectively, including extraction, metadata, batch operations, and search. A minor gap exists in lacking explicit update or delete operations, but these are not typical for scraping tasks, and agents can work around this with the provided tools.