Skip to main content
Glama

hybridforgelab-distill-mcp: moved to bytestay-distill-mcp

This package has moved to bytestay-distill-mcp. Hybrid Forge Lab is now ByteStay.

This last version only installs bytestay-distill-mcp and forwards to it. It prints a one-line notice on stderr and gets no more updates.

Switch

Replace hybridforgelab-distill-mcp with bytestay-distill-mcp in your MCP client config:

"command": "uvx",
"args": ["--from", "bytestay-distill-mcp", "distill-mcp"]

Or with Claude Code:

claude mcp add distill --env RAPIDAPI_KEY=your-rapidapi-key -- uvx --from bytestay-distill-mcp distill-mcp

The environment variables are the same, so your keys keep working.

Related MCP server: cleanfetch

Available Tools

2 tools
fetch_markdownA
Read-onlyIdempotent

Fetch a web page and return its main content as Markdown, with title, author, date and language.

status is "ok" on success. Other values (robots_txt, opted_out, blocked, not_html, http_error, unreachable) explain why there is no content.

Inputs: url (required), max_chars, include_links, include_images, +1 more.

html_to_markdownA
Read-onlyIdempotent

Turn HTML you already have into clean Markdown (main content only). A noai directive in the HTML is honoured: the result then has no content.

Inputs: html (required), base_url, max_chars, include_links, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct inputs and purposes: fetch_markdown starts from a URL, while html_to_markdown converts HTML the caller already has. The descriptions make the boundary explicit, so an agent should not confuse them.

    Naming Consistency4/5

    Both names use snake_case and are readable, but they follow slightly different construction patterns: fetch_markdown is verb_object, while html_to_markdown is source_to_target. The deviation is minor and does not impede understanding.

    Tool Count4/5

    Two tools is on the low side generally, but for this narrowly focused markdown-extraction server each tool covers a necessary part of the workflow: fetching a URL and converting existing HTML. The set is well scoped without obvious filler.

    Completeness4/5

    The core operations for turning web content into Markdown are covered: URL fetching and HTML conversion. Minor possible gaps, such as batch fetching or raw HTML retrieval, are not essential for the apparent purpose and can be worked around.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers