Skrape MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SKRAPE_API_KEY | Yes | Your API key from skrape.ai |
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 |
|---|---|
| get_markdownC | Get markdown content from a webpage using skrape.ai |
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 confusion between tools. The tool's purpose is clearly defined as retrieving markdown content from webpages, making it distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'get_markdown' follows a clear verb_noun pattern, which would be consistent if more tools were added.
A single tool is too few for a server named 'Skrape MCP Server', which suggests a broader scraping or data extraction purpose. This minimal toolset limits functionality and feels incomplete for the implied scope, as it only handles markdown retrieval without other common scraping operations.
The server is severely incomplete for a scraping domain. It lacks basic operations such as fetching HTML, extracting specific elements, handling different content types, or managing sessions. With only one tool for markdown, agents will face dead ends when trying to perform typical scraping tasks.