In-depth architectural comparison of the MCP Server and Diavgis — Greek Public Procurement 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.
At a Glance & Executive Verdict
MCP Server
Search & Data Extraction · Local stdio
Quality: 56/100 (Good) | Auth: API Key required
Diavgis — Greek Public Procurement
Search & Data Extraction · Remote HTTP/SSE
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose MCP Server if you need specialized Search & Data Extraction tools running via a local process. Choose Diavgis — Greek Public Procurement if your workspace requires Search & Data Extraction integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose MCP Server when:
You need dedicated capabilities in the Search & Data Extraction domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: ATLAS_API_BASE, ATLAS_API_KEY, ATLAS_TIMEOUT_MS, ATLAS_MAX_RETRIES.
Search 800 000+ Polish public tenders (BZP + TED). Profiles of procuring entities and contractors by NIP, market statistics by CPV/province, 90+ term procurement glossary.
Search Greek public procurement: tenders, awards, contracts, payments, buyers and suppliers.
Search public procurement tenders from BZP (Biuletyn Zamówień Publicznych) and TED (Tenders Electronic Daily) via Atlas Przetargów. Returns a list with titles, buyers, locations, CPV codes, estimated values and deadlines. Use for queries like 'aktywne przetargi budowlane w Warszawie', 'zamówienia IT powyżej 500k PLN', 'co kupuje ZUS'.
get_tender
Retrieve detailed information about a specific Polish public tender by its ID. Returns buyer, location, deadlines, estimated value, CPV codes, contractor (if awarded), notice type and a content excerpt. Optionally includes AI-generated summary points (requires ATLAS_API_KEY).
get_buyer
Fetch a profile of a Polish public procuring entity (zamawiający) by its NIP (tax ID). Returns name, location, statistics, recent tenders, and top winning contractors. Use for due diligence on who buys what and from whom.
get_contractor
Fetch a profile of a Polish tender contractor by its NIP. Returns name, location, total wins, total value and top buyers they win tenders from.
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).
MCP Server is categorized under Search & Data Extraction and uses a local stdio subprocess. In contrast, Diavgis — Greek Public Procurement belongs to Search & Data Extraction using remote streaming HTTP/SSE transport. Select MCP Server when you need capabilities focused on search & data extraction and Diavgis — Greek Public Procurement when you require tools for search & data extraction.
Search Polish public procurement entities (buyers / zamawiający) or contractors (wykonawcy) by name. Returns a list with NIP, location and volume. Useful to find the NIP for get_buyer / get_contractor tools.
get_category_stats
Retrieve aggregate statistics for a CPV category: count, average/median value, average number of offers, average deadline period. Based on historical BZP+TED data. Useful for market sizing and competitive benchmarking.
get_province_stats
Retrieve aggregate tender statistics by Polish province (all 16 voivodeships) or drill down to a specific city (top buyers, top CPV categories). Without arguments returns the full province ranking.
search_cpv
Look up CPV (Common Procurement Vocabulary — EU procurement category) codes by Polish keyword. Use this before search_tenders to find the right CPV filter. Returns code, name, division, and historical tender count.
Diavgis — Greek Public Procurement Tools (10)
find_entity
Resolve a buyer or supplier **name** to its ΑΦΜ — the first call when you only have a name
search_tenders
Search acts across all three sources — by text, buyer, supplier, CPV, region, amount, date
expiring_contracts
Contracts running **now** that expire within 0, 7, 30 or 180 days
get_act
Full detail of one act by Διαύγεια ΑΔΑ or ΚΗΜΔΗΣ ΑΔΑΜ
get_entity
Profile of a company or public body by 9-digit ΑΦΜ — name, role, spend/receipts
get_chain
A reconstructed procurement lifecycle: the linked sequence tender → award → contract → payment
rank_entities
Top buyers or suppliers, by spend or by count
spend_by_cpv
Committed value by CPV division, optionally for one year
entity_counterparties
Who an entity actually transacts with — a buyer's top suppliers, or the reverse
get_quota
Your plan, calls used and remaining, and the rate limits — free, not counted against the quota