F
licenseA
qualityC
maintenanceMCP server for searching and retrieving contracts from the Polish Central Register of Contracts (CRU) via its API.
2
-
ezd-puw-mcp
by gacabartosz
Related Servers
Alternatives to ezd-puw-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for DigiSign.cz digital signature API — create, send, and manage digital signature envelopes.151MIT
- FlicenseAqualityCmaintenanceMCP server providing access to Polish business registers (KRS, CRBR) via the rejestr.io API, enabling search, retrieval of organizations, beneficial owners, financial documents, and more.12-
- AlicenseAqualityBmaintenanceUnified MCP server for Polish legal data, enabling search and retrieval across case law, legislation, company register, tax rulings, public procurement, and EU sources through four aggregated tools.4170 PyPI1Apache 2.0
- FlicenseBqualityCmaintenanceSingle-tenant MCP server for Polish KSeF e-invoice workflows, supporting local stdio testing, draft management, and invoice submission with safety gates.23-
- AlicenseNot gradedqualityFmaintenanceMCP server providing access to Polish law statutes, provisions, case law, and EU law integrations, enabling natural language legal research, citation validation, and cross-referencing.30 npm7Apache 2.0
TDQS
C2.6/5.0
Scored across 91 tools
Disambiguation1/5
Many tools are semantic duplicates exposed through different API versions, e.g. ezd_pracownik_add vs ezd_api1_create_worker, ezd_dokument_register vs ezd_api3_register_document, and ezd_koszulka_transfer vs ezd_api1_transfer_case. An agent cannot reliably tell which endpoint to choose without deep knowledge of undocumented API1/API3 differences.
Naming Consistency2/5
Some groups use ezd_<domain>_<verb> such as ezd_koszulka_create and ezd_pracownik_add, while API1/API3 groups reverse the pattern to ezd_api3_<verb>_<noun>. Similar actions are inconsistently named create/add/register/update across the set, making the overall naming pattern hard to predict.
Tool Count1/5
91 tools is far beyond the 50+ threshold for an extreme mismatch. Even for a broad system like EZD PUW, this endpoint dump creates excessive agent-facing surface and should be split into focused servers or reduced to higher-level workflow operations.
Completeness4/5
The set covers a broad DMS lifecycle: workers, cases, documents, addressees, correspondence, ePUAP, e-Doreczenia, RWA folders, forms, blockchain, and migrations. Minor gaps exist, such as no addressee update/delete and no general document search/delete, but agents can usually work around them.
Maintenance
ActivityInactive
ResponsivenessNo issues