modelcontextprotocol / modelcontextprotocol/servers

Fetch extension fails with "Unknown scheme for proxy URL URL('socks://127.0.0.1:2080/')"

Open
#767 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
90.5k
Forks
11.7k
Avg merge
2d 2h
Merged PRs (30d)
5

Description

Describe the bug
I installed https://github.com/block/goose/ cli and use ollama to manage a local LLM.
Adding fetch extension worked fine.
I tried both uvx mcp-server-fetch and uvx mcp-server-fetch --ignore-robots-txt to run extension.
Either way fetching any url ends up with Unknown scheme for proxy URL URL('socks://127.0.0.1:2080/'). This is somehow marked as "status":"success" in the tool result.

To Reproduce
Steps to reproduce the behavior:

  1. Install block/goose cli
  2. Set up any llm provider
  3. Install and add fetch extension
  4. Run goose and ask something like this: "read this doc - https://block.github.io/goose/docs/tutorials/custom-extensions/"

Logs

{"role":"assistant","created":1741517422,"content":[{"type":"text","text":""},{"type":"toolRequest","id":"call_7jc59c1n","toolCall":{"status":"success","value":{"name":"mcp_server_fetch__fetch","arguments":{"max_length":2048,"url":"https://block.github.io/goose/docs/tutorials/custom-extensions/"}}}}]}
{"role":"user","created":1741517422,"content":[{"type":"toolResponse","id":"call_7jc59c1n","toolResult":{"status":"success","value":[{"type":"text","text":"Unknown scheme for proxy URL URL('socks://127.0.0.1:2080/')"}]}}]}

Expected behavior
It should return the web page's contents upon a correct call. It shouldn't return status: success if the page's content isn't available.

Additional context
Sometimes it does work: https://github.com/block/goose/issues/1329 . But I'm yet to witness it myself.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The reported entry point is uvx mcp-server-fetch; first reproduce the fetch extension failure with the proxy URL socks://127.0.0.1:2080/ and inspect the logged tool result. Done means the requested page is fetched successfully, or failures report a non-success status instead of returning status: success.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
networking
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.