Skip to main content
Glama
deenesjakoruzh
kwp-lab

MCP Fetch With Proxy

by kwp-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

MCPフェッチ

カスタムHTTPプロキシを使用してWebコンテンツを取得するためのモデルコンテキストプロトコル（MCP）サーバー。これにより、Claude Desktop（または任意のMCPクライアント）はWebコンテンツを取得し、画像を適切に処理できるようになります。

このリポジトリは@smithery/mcp-fetchからフォークし、 node-fetch実装をライブラリnode-fetch-nativeに置き換えます。

サーバーは、 http_proxyおよびhttps_proxy環境変数が設定されている場合、デフォルトでそれらを使用してリクエストをプロキシサーバー経由でルーティングします。MCP_HTTP_PROXY環境変数を設定することで、別のプロキシサーバーを使用することMCP_HTTP_PROXYできます。

利用可能なツール

  • fetch : インターネットからURLを取得し、その内容をマークダウンとして抽出します。画像が見つかった場合は、そのURLがレスポンスに含まれます。

画像処理仕様:

記事コンテンツから画像の URL のみを抽出し、ツールの結果に追加します。

{
  "params": {
    "url": "https://www.example.com/articles/123"
  },
  "response": {
    "content": [
      {
        "type": "text",
        "text": "Contents of https://www.example.com/articles/123:\nHere is the article content\n\nImages found in article:\n- https://www.example.com/1.jpg.webp\n- https://www.example.com/2.jpg.webp\n- https://www.example.com/3.webp"
      }
    ]
  }
}

Related MCP server: crawl4ai-mcp

クイックスタート（ユーザー向け）

このツールを Claude Desktop で使用するには、Claude Desktop の構成 ( ~/Library/Application Support/Claude/claude_desktop_config.json ) に以下を追加するだけです。

{
  "tools": {
    "fetch": {
      "command": "npx",
      "args": ["-y", "@kwp-lab/mcp-fetch"],
      "env": {
        "MCP_HTTP_PROXY": "https://example.com:10890" // Optional, remove if not needed
      }
    }
  }
}

これにより、必要に応じてツールの最新バージョンが自動的にダウンロードされ、実行されます。

必要な設定

  1. クロードのアクセシビリティを有効にする:

    • システム設定を開く

    • 「プライバシーとセキュリティ」>「アクセシビリティ」へ移動

    • 「+」ボタンをクリック

    • アプリケーションフォルダからClaudeを追加します

    • クロードのトグルをオンにする

開発者向け

次のセクションは、ツールを開発または変更したい人向けです。

前提条件

  • Node.js 18歳以上

  • Claude Desktop ( https://claude.ai/desktopからインストール)

  • tsx ( npm install -g tsxでインストール)

インストール

Smithery経由でインストール

Smithery経由で Claude Desktop 用の MCP Fetch を自動的にインストールするには:

npx -y @smithery/cli install @kwp-lab/mcp-fetch --client claude

手動インストール

git clone https://github.com/kwp-lab/mcp-fetch.git
cd mcp-fetch
npm install
npm run build

構成

  1. Claude Desktop がインストールされ、実行されていることを確認してください。

  2. まだインストールしていない場合は、tsx をグローバルにインストールします。

    npm install -g tsx
# or
pnpm add -g tsx

  3. 次の場所にある Claude Desktop 設定を変更します。

~/Library/Application Support/Claude/claude_desktop_config.json

これは、Claude Desktop メニューから簡単に見つけることができます。

  1. クロードデスクトップを開く

  2. MacのメニューバーでClaudeをクリック

  3. 「設定」をクリック

  4. 「開発者」をクリック

MCP クライアントの構成に以下を追加します。

{
  "tools": {
    "fetch": {
      "args": ["tsx", "/path/to/mcp-fetch/index.ts"]
    }
  }
}

Available Tools

1 tool
fetchA

Retrieves URLs from the Internet and extracts their content as markdown. If images are found, their URLs will be included in the response.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYes
maxLengthNo
startIndexNo
rawNo

TDQS

A3.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions content extraction and image URL inclusion, but doesn't cover important aspects like error handling (e.g., invalid URLs, network failures), rate limits, authentication needs, privacy implications, or what happens when maxLength is exceeded. The description is insufficient for a tool that interacts with external resources.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is perfectly concise with two clear sentences that each add value. The first sentence establishes the primary function, and the second adds important behavioral detail about image handling. No wasted words or redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 4 parameters, no annotations, and no output schema, the description provides adequate basic functionality explanation but lacks sufficient detail about behavioral characteristics, error conditions, and output format. The absence of sibling tools reduces complexity, but the description should do more to compensate for the lack of structured metadata.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description doesn't mention any parameters directly, but with 0% schema description coverage, it doesn't compensate for the lack of parameter documentation. However, the tool has 4 parameters with clear schema definitions (url, maxLength, startIndex, raw), and the description's focus on the core functionality provides some context. The baseline would be lower if the schema were less informative.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with specific verbs ('retrieves', 'extracts') and resources ('URLs from the Internet', 'content as markdown'), and explicitly mentions handling of images. It distinguishes what the tool does without relying on the generic name 'fetch'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving and converting web content to markdown, but provides no explicit guidance on when to use this tool versus alternatives (though no sibling tools are listed). It lacks information about prerequisites, error conditions, or performance considerations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

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

  1. 1 tool update
    • First observedfetch
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.6/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools, making disambiguation perfect. The single tool has a clear and distinct purpose without any competing alternatives.

Naming Consistency5/5

The single tool name 'fetch' follows a simple verb pattern, and with only one tool, consistency is inherently perfect. There are no other tools to create naming conflicts or inconsistencies.

Tool Count2/5

A single tool is too few for most server purposes, as it limits functionality and flexibility. While it might suffice for basic fetching, it feels thin and under-scoped for a server named 'MCP Fetch With Proxy', which suggests broader capabilities.

Completeness2/5

The tool surface is severely incomplete; it only provides fetching and markdown extraction without supporting operations like configuration, error handling, or advanced proxy management. This leaves obvious gaps for a server with 'Proxy' in its name, such as setting or testing proxy settings.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches