tenderkit
Related Servers
Alternatives to tenderkit
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables searching and analyzing Polish public procurement tenders from BZP and TED, including filtering, tender details and timelines, offers and contract values, buyer/contractor profiles, CPV code lookup, and regional statistics, with optional AI-summary endpoints.121-
- FlicenseAqualityDmaintenanceMCP server for searching and retrieving contracts from the Polish Central Register of Contracts (CRU) via its API.2-
- AlicenseNot gradedqualityDmaintenanceFind, analyze, and score Polish public tenders (BZP): parsed requirements, deadlines, certificates, and bid-fit scoring against your company profile.8 npmMIT
- AlicenseAqualityCmaintenanceSearch 800 000+ Polish public tenders (BZP + TED) from Claude Desktop, Cursor, Continue. Provides 8 tools for tender search, buyer/contractor profiles by NIP, market statistics, plus a glossary of 90+ Polish public procurement terms.48103 npm4MIT

vartoofficial
AlicenseNot gradedqualityDmaintenanceMCP server for Ukrainian public procurement (Prozorro) that exposes tools to search tenders, retrieve tender details and cards, list and read tender documents.ISC- AlicenseAqualityBmaintenanceZero-dependency MCP stdio bridge for Portugal & EU official registries (IMPIC Portal BASE public contracts & tenders, NIPC, Diário da República DRE, TED, EU FSF) with pay-per-call USDC & MiCA EURC settlement.47MIT
TDQS
Scored across 13 tools
Most tools have clearly distinct purposes: refresh lifecycle, notice search/read, award search, profile management, and document handling are well separated. A few boundaries are slightly fuzzy, especially search_notices vs start_refresh for optional refreshes, and search_results vs procedure_results when looking for award data, but the descriptions generally resolve them.
The set is predominantly snake_case verb_noun naming (start_refresh, search_notices, get_notice, list_documents, save_profile). The main deviations are noun-first names like refresh_status and procedure_results, which are readable but break the otherwise consistent verb_noun pattern.
Thirteen tools is well-scoped for a server covering refresh jobs, profiles, notice/award search, and document retrieval. Each tool maps to a distinct part of the workflow, with no obvious filler tools.
Core workflows are covered: durable refresh start/status/resume, notice and award search, procedure-level results, document listing/fetching/reading, and profile save/delete. Minor gaps remain, notably no tool to list or inspect existing profiles and no explicit refresh cancellation, but agents can work around these in most workflows.