UseScraper MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| USESCRAPER_API_KEY | Yes | Your UseScraper API key |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scrapeC | Scrape content from a webpage using UseScraper API |
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
Only one tool exists, so there is no possibility of confusion with other tools.
With a single tool, naming is trivially consistent.
A single tool for web scraping is borderline; it might suffice for basic use but feels thin for a full-featured scraper server.
The single scrape tool covers the core functionality, but lacks additional features like selecting specific elements or handling different output formats, which are common in web scraping APIs.