Diavgis — Greek Public Procurement vs Fetch

In-depth architectural comparison of the Diavgis — Greek Public Procurement and Fetch 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 Diavgis — Greek Public Procurement when:

• You need dedicated capabilities in the Search & Data Extraction domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: find_entity, search_tenders, expiring_contracts.

Explore Diavgis — Greek Public Procurement Details

Choose Fetch 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).
• Primary tools included: create_entities, create_relations, add_observations.

Explore Fetch Details

Feature & Specification Comparison

Specification	Diavgis — Greek Public Procurement Search & Data Extraction	Fetch VerifiedSearch & Data Extraction
Summary	Search Greek public procurement: tenders, awards, contracts, payments, buyers and suppliers.	Web content fetching and conversion for efficient LLM usage.
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": {
    "diavgis-greek-public-procurement-2": {
      "url": "https://api.diavgis.gr/ocds"
    }
  }
}

{
  "mcpServers": {
    "fetch": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-memory"
      ]
    }
  }
}

Related MCP Server Comparisons