redup.mcp-web-parser
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| service___port | No | Port for the MCP server. Default: 8000 | |
| McpWebParser___default_proxy | No | Optional egress proxy URL for Crawl4AI IP substitution. | |
| McpWebParser___upstream_token | No | Optional token for the upstream service. | |
| McpWebParser___upstream_base_url | Yes | The base URL of the Crawl4AI upstream service. Required, no default. |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| parse_pageA | Read an HTML web page and return cleaned markdown as JSON. WHEN TO USE: HTML articles, docs, wiki, blog posts, /abs pages. WHEN NOT TO USE: PDF, DOCX, XLSX, ZIP, images, or other file downloads — call fetch_binary instead. If this tool returns is_binary=true, switch to fetch_binary (do not retry parse_page in a loop). Returns JSON fields: success, url, status_code, markdown, error_message, links_internal, links_external, truncated, used_proxy, content_type, is_binary, binary_kind, hint. |
| fetch_binaryA | Download a binary file and return metadata + base64 bytes as JSON. WHEN TO USE: the URL itself is a file download — pdf, docx/xlsx/pptx, odt/epub, zip/tar/gz/7z/rar, png/jpeg/gif/webp, or similar. Also use when parse_page returned is_binary=true / hint to call fetch_binary. WHEN NOT TO USE: normal HTML pages (example.com, wiki, /abs, blogs) — use parse_page. Never switch to this tool only because parse_page failed on an HTML URL (anti-bot, timeout, empty markdown). Download only: no text extraction, no OCR, no unzip. Bytes live only in
JSON Returns JSON: success, url, status_code, media_type, kind, size, filename, truncated, error_message, used_proxy, content_base64. |
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 2 tools
The two tools are cleanly separated: parse_page handles HTML pages and returns markdown, while fetch_binary handles file downloads and returns metadata plus bytes. They also include when-to-use and when-not-to-use guidance, plus a clear fallback path when parse_page detects binary content.
Both tools use the verb_noun pattern: parse_page and fetch_binary. Naming is regular, consistent, and immediately communicates what each tool does.
Two tools is lower than the typical 3-15 range, but it maps exactly to the server's intended scope: HTML parsing and binary fetching. The set is slightly thin but not excessive or insufficient for such a narrow purpose.
The tool set covers the main web resource categories: HTML pages are parsed to markdown, and binaries are downloaded with metadata and bytes. The is_binary fallback closes the biggest edge case, so there are no obvious dead ends.