[Discovery] mcp/fetch - Web Content Fetching
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, python
- Domain
- backend, devops, documentation
Research direction
Start with the upstream mcp/fetch source and the repository's fetch.dockerfile, then review the transport, Docker, and dependency notes in this issue. Determine the scope of the tool documentation, HADOLint check, and possible Rust rewrite; the work is done when those tracking items have clear outcomes.
Written by the indexing model from the issue text.
Description
Project Association
This issue tracks the mcp/fetch MCP server in the core profile.
Server Details
- Name: fetch
- Source: https://github.com/modelcontextprotocol/servers/tree/main/src/fetch
- Docker Hub: https://hub.docker.com/r/mcp/fetch
- Category: web
- Language: Python
Transport Status
- Current: stdio only (upstream)
- Implementation: HTTP-wrapped via supergateway
- Docker Image:
fetch-mcp:http(custom build)
Tools Provided
fetch: Fetches a URL and returns content as markdown- Parameters: url (required), max_length, start_index, raw
Docker Status
- Official image:
mcp/fetch - Custom wrapper:
fetch.dockerfile(extends base with supergateway) - HADOLint: Not checked
Notes
- Python-based server using UV for dependency management
- Required extending base image (not multi-stage) due to UV symlink issues
- Works well with Traefik multi-layer routing
Tracking
- Document all tools comprehensively
- HADOLint compliance check
- Consider Rust rewrite
- Dominant language
- Just
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aRustyDev/mcp
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
category/workflow phase/discovery transport/http-streamed type/research
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
category/workflow phase/discovery transport/http-streamed type/research
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
category/docs phase/discovery transport/http-streamed type/research
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
category/workflow phase/discovery transport/http-streamed type/research
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Similar issues
-
Change output crossing a compactsize boundary leaves the fee slightly below the requested feerateOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bitcoindevkit/bdk_wallet#578 ·
Maintainers usually reply within 8 days
-
Hydraulic gas_pressure omits the reference-density offset, breaking roundtrips and the pressure joinOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
ethereum/execution-apis#915 ·
Maintainers usually reply within 1 day
-
enhancement via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
pingdotgg/t3code#14816 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
OpenConext/OpenConext-access#1015 ·
Maintainers usually reply within 1 day