MCP server fetches URL through a real Chromium browser, returns main content as clean Markdown
An MCP server that fetches a URL and returns the main content as clean Markdown. Uses plain HTTP when possible and real Chromium when needed. Most MCP web-fetch tools either: use plain HTTP, which fails on JS-required pages and gets blocked by Cloudflare bot detection on many sites; or use a real browser but return raw HTML or accessibility-tree snapshots, which are noisy and token-heavy when you…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
An MCP server that fetches a URL and returns the main content as clean Markdown. Uses plain HTTP when possible and real Chromium when needed. Most MCP web-fetch tools either: use plain HTTP, which fails on JS-required pages and gets blocked by Cloudflare bot detection on many sites; or use a real browser but return raw HTML or accessibility-tree snapshots, which are noisy and token-heavy when you just want to read the article. This server uses a three-tier strategy, using the fastest approach…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.