Diavgis — Greek Public Procurement vs Polish Public Tenders
A side-by-side look at the Diavgis — Greek Public Procurement and Polish Public Tenders MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
P
Polish Public TendersSearch & Data ExtractionPolish public procurement for AI agents: BZP and TED tenders, awards, buyers and contractors.47FairAuth: api key requiredVerdict: choose Diavgis — Greek Public Procurement for search & data extraction work over a hosted endpoint; choose Polish Public Tenders for search & data extraction. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Diavgis — Greek Public Procurement when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
find_entity, search_tenders, expiring_contracts.
PChoose Polish Public Tenders when
- You need dedicated capabilities in the Search & Data Extraction domain.
- Its auth model fits you: API key required.
- You want tools like
search_tenders, get_company_public_tenders, get_company_eu_tenders.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | P Polish Public Tenders | |
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 49/100 · Fair | 47/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | Not declared | API key required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 10 | 5 |
| Full listing | View Diavgis — Greek Public Procurement | View Polish Public Tenders |
Tools & capabilities
Diavgis — Greek Public Procurement tools 10
find_entityResolve a buyer or supplier **name** to its ΑΦΜ — the first call when you only have a namesearch_tendersSearch acts across all three sources — by text, buyer, supplier, CPV, region, amount, dateexpiring_contractsContracts running **now** that expire within 0, 7, 30 or 180 daysget_actFull detail of one act by Διαύγεια ΑΔΑ or ΚΗΜΔΗΣ ΑΔΑΜget_entityProfile of a company or public body by 9-digit ΑΦΜ — name, role, spend/receiptsget_chainA reconstructed procurement lifecycle: the linked sequence tender → award → contract → paymentrank_entitiesTop buyers or suppliers, by spend or by countspend_by_cpvCommitted value by CPV division, optionally for one yearentity_counterpartiesWho an entity actually transacts with — a buyer's top suppliers, or the reverseget_quotaYour plan, calls used and remaining, and the rate limits — free, not counted against the quota
Polish Public Tenders tools 5
search_tendersOpen or awarded notices by industry (IT, construction, healthcare or CPV division), region, city, kind and value.get_company_public_tendersBZP contracts won and notices published by one company.get_company_eu_tendersTED (EU-threshold) contracts and notices for one company.get_company_eu_fundsEU funds, state aid and European Commission grants.search_companiesIdentify buyers and contractors (KRS, NIP, financials).
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Diavgis — Greek Public Procurement
{
"mcpServers": {
"diavgis-greek-public-procurement-2": {
"url": "https://api.diavgis.gr/ocds"
}
}
}
Polish Public Tenders
No confirmed install command for Polish Public Tenders yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Diavgis — Greek Public Procurement is categorized under Search & Data Extraction and uses a remote HTTP/SSE transport. Polish Public Tenders belongs to Search & Data Extraction and uses an install path we have not confirmed yet. Pick Diavgis — Greek Public Procurement for search & data extraction work and Polish Public Tenders for search & data extraction.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Polish Public Tenders has no confirmed install command yet — follow its own setup instructions.
Diavgis — Greek Public Procurement has no declared pricing — check the project's own site. Polish Public Tenders has no declared pricing — check the project's own site. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add diavgis-greek-public-procurement-2 and polish-public-tenders as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Diavgis — Greek Public Procurement has a quality signal of 49/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Polish Public Tenders has 47/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.