Scrapiq MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCRAPIQ_ENDPOINT | Yes | The URL of the Scrapiq extraction endpoint (e.g., http://localhost:8001/v1/extract). |
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 |
|---|---|
| scrapiq_extractA | Extract a web page into clean, structured content for LLM/RAG pipelines via the Scrapiq API. Strips boilerplate, navigation, ads, and scripts. Returns title, content, links, and metadata. |
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 or overlap. The tool's purpose is clearly described.
With a single tool, there is no pattern to contradict. The name 'scrapiq_extract' follows a predictable brand + verb format.
A single tool feels thin for a server branded as 'Scrapiq'. While it can perform the core extraction task, the count is borderline and could benefit from additional operations like batch extraction.
The one tool adequately covers the primary function of extracting and cleaning web content. Minor gaps exist, such as no support for batch URLs or custom extraction rules, but there are no dead ends for the stated purpose.