clean-markdown-mcp
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 | Fetch any web page and return its main content as clean, readable Markdown. Strips out navigation, ads, cookie banners, scripts, and other boilerplate. Ideal for feeding article or documentation content to an LLM. |
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 a single tool, there is no possibility of confusion or overlap. The tool's purpose is clear and distinct by definition.
The tool name 'scrape_url' follows a clear verb_noun pattern, which is consistent with common MCP naming conventions. With only one tool, the pattern is trivially consistent.
The server has only 1 tool, which is below the typical 3-15 range. However, it is appropriately scoped for a highly focused purpose: fetching and converting web pages to clean markdown. The single tool fully covers the server's stated function.
The domain is 'clean-markdown', and the single tool provides a complete lifecycle: it fetches any web page and returns clean markdown, covering all necessary functionality. There are no obvious gaps for the stated purpose.