BidSkim vs Fetcher MCP

In-depth architectural comparison of the BidSkim and Fetcher MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose BidSkim when:

• You need dedicated capabilities in the Search & Data Extraction domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: OAuth 2.0 (Paid Service).

Explore BidSkim Details

Choose Fetcher MCP when:

• You need dedicated capabilities in the Search & Data Extraction domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• You have access to required keys: NODE_ENV.
• Primary tools included: JavaScript execution via Playwright headless Chromium, Intelligent main content extraction using Readability algorithm, Supports Markdown and HTML output formats.

Explore Fetcher MCP Details

Feature & Specification Comparison

Specification	BidSkim Search & Data Extraction	Fetcher MCP jae-jae Search & Data Extraction
Summary	UK procurement intelligence: 8 read-only tools for live tender search (keyword, CPV, region, value, deadline), semantic search, contract-renewal intelligence (expiry dates, incumbent suppliers, buyer contacts), buyer and supplier profiles, and the caller's saved pipeline. Covers Find a Tender, Contracts Finder, PCS and Sell2Wales, deduplicated to one record per opportunity.	MCP server for fetching web page content using Playwright headless browser, supporting Javascript rendering and intelligent content extraction, and outputting Markdown or HTML format.
Category & Scope

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "bidskim": {
      "url": "https://bidskim.com/mcp"
    }
  }
}

{
  "mcpServers": {
    "jae-jae-fetcher-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "fetcher-mcp"
      ],
      "env": {
        "NODE_ENV": "YOUR_NODE_ENV_HERE"
      }
    }
  }
}

Related MCP Server Comparisons