Browse / MCP servers
dondai1234/master-fetch
MCP server for web fetching with Cloudflare bypass, Trafilatura extraction, and smart routing. Free, self-hosted, no API keys.
- MCP
- local-first
Works.Tested on 2026-10-28. From the README alone, on Linux with Haiku.
What we checked
Does it run from the README?Yes. Running in 9:44 on a clean Linux box.The run
Tested Oct 28, 2026, rev 86d1b13.
Does it do what the README says?1 of 1 claims held up.Evidence
“smart_fetch fetches a URL over HTTP and returns its content”
Expected page content returned. Got This domain is for use in documentation examples.
Which checks were skipped?1 check skipped.Reasons
Skipped checks count as neither passes nor failures.
Examples: 1 skipped
- Repository's documented offline test suite (CI command) runs: command exited with code 1: te-packages/pytest_asyncio/plugin.py:300: PytestDeprecationWarning: The configuration option "asyncio_default_fixture_loop_scope" is unset. The event loop scope for asynchronous fixtures will default to the "fixture" caching scope. Future versions of pytest-asyncio will default the loop scope for asynchronous fixtures to "function" scope. Set the default fixture loop scope explicitly in order to avoid unexpected behavior in the future. Valid fixture loop scopes are: "function", "class", "module", "package", "session" warnings.warn(PytestDeprecationWarning(_DEFAULT_FIXTURE_LOOP_SCOPE_UNSET))
Which setups did we try?Works with Haiku. Unverified with Luna.Setups
Linux / Haiku: works, Oct 28, rev 86d1b13. Linux / Luna: unverified, Oct 28, rev 86d1b13.
Needs keys, a login or a browser?No.Details
None seen
Is it safe to run?Made outbound HTTPS connections: yes (hosts not recorded) by hound, testsWhat we saw
Review signals across current setups: connection review. 6 static matches retained as context.
Repository processes attempted these non-loopback connections; proxies can hide the final hostname. 9 distinct locations. 17 attributed processes.
Reviewed as expected for a test run: attempted writes that failed, so nothing was written.
Full event, path and process lists for each observed setup:
A quiet run is not a safety guarantee.
Is it maintained?Slow · 0 commits in 90 days · 0 merged PRs in 90 days · 7 open issues · 5 open PRsActivity
slow: last commit 96 days ago; 0 commits and 0 merged PRs in 90 days; 7 open issues, 5 open PRs; 17 of 44 recent threads got a maintainer reply, median first reply 2.5h; latest release 2026-07-24
Can I show this on my README?Copy the badge.Badge
The run
Oct 28 · rev 86d1b13Independent test, not endorsed by the project.