simap MCP Server
Related Servers
Alternatives to simap MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server providing read access to Swiss public procurement data via the official simap.ch API, covering all cantons and the Confederation with intraday updates. It enables searching tenders, awards, construction codes, and procurement offices through natural language queries.951 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceProvides access to Swiss public procurement tenders and awards data, queryable via natural language through the Pipeworx gateway.187 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search and retrieve public procurement notices from 17 sources across Germany, the EU, and the UK, with filtering by country, CPV code, deadline, and contract value, plus full tender details and source freshness checks.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search and retrieve Poland's official public procurement notices from the e-Zamówienia/BZP bulletin without any API key, covering the latest published contract notices as well as filtering by keyword, CPV code, date range, or contracting authority.20 npmMIT
- AlicenseBqualityCmaintenanceProvides AI models with access to Ukrainian government procurement data from Prozorro, enabling search and retrieval of tender information by organization, date range, and other criteria.15 npm12ISC
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search and retrieve Portuguese public-procurement tender announcements and awarded contracts from IMPIC's open-data publication, filtering by keyword, CPV code, buyer, supplier, amount, and date range, and to pull full detail records including NIFs, procedure types, and official notice links.243 npmMIT
TDQS
Scored across 14 tools
Each tool has a clear resource+action focus: tender search/details/history, reference-code lookups (CPV, BKP, NPK, OAG), and hierarchy browsing are well separated. The search_X_codes vs browse_X_tree split is intentionally distinct (keyword lookup vs hierarchy traversal). The only mild overlap is search_proc_offices vs list_institutions, both returning publishing entities, but descriptions differentiate them by scope.
Consistent snake_case verb_noun pattern throughout: search_*, get_*, list_*, browse_*. The parallel naming across the four code systems (search_cpv_codes/browse_cpv_tree, etc.) is highly predictable and reinforces the schema.
14 tools is well within a healthy range for a search-oriented procurement portal. The 4x2 code-system symmetry (search + browse for each of CPV/BKP/NPK/OAG) is justified by the distinct classification domains rather than redundancy.
Covers the core read path: find tenders, get details, view publication/award history, resolve reference codes and hierarchies, list cantons and institutions. As a read-only public-portal mirror this is near-complete; minor gaps like no direct fetch of attachments/documents or saved-search management are workable around.