Polish MCP Servers
Related Servers
Alternatives to Polish MCP Servers
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceSearch official US government data from any MCP client: building permits from 10 city open-data portals, federal contract opportunities from SAM.gov with contracting-officer contacts, and the CMS NPI healthcare-provider registry. Open-source TypeScript server; data delivered via Apify's pay-per-result actors using your own Apify token.3MIT
- AlicenseAqualityBmaintenanceIndex of Panda Federation public-data MCP tools. Prefer a focused domain server (research / public-funding / leads / web-security); this mega-server is the compatibility surface.40331 PyPIMIT
- AlicenseAqualityCmaintenanceMCP server that exposes 14 fecklesspleb Apify Actors (job boards, Hacker News, SEO audit, metadata, web tools) as tools; runs bill per result to the caller's own Apify account.1068 npmMIT
- AlicenseAqualityBmaintenanceEnables AI assistants to use thousands of ready-made Apify Actors as tools to scrape and extract data from social media, search engines, maps, e-commerce sites, and arbitrary web pages. Can be used hosted via OAuth at mcp.apify.com or locally over stdio.10MIT
- AlicenseAqualityDmaintenanceMCP server that provides AI agents with Polish business data tools: identifier validation (NIP, PESEL, REGON, KRS, IBAN), VAT whitelist checks, EU VIES lookups, and NBP exchange rates.58 npmMIT
- AlicenseNot gradedqualityBmaintenanceExposes typed tools that forward requests to Apify actors for public-data lookups and scraping across sanctions, SEC filings, layoffs, licensing, SEO, jobs, permits, maps, social media, marketplace, and government data. It lets MCP clients run these data-collection workflows using their own Apify token.1MIT
TDQS
Scored across 17 tools
Each tool targets a clearly different official data source (SAOS judgments, KRS, REGON, CEIDG, PSE, ELI, ULDK, RPWDL, GUNB, CEPiK, MSiG, EIPA), and descriptions explicitly cross-reference siblings to steer selection. The only real overlaps are polish-court-judgments-saos / polish-legal-acts-eli versus polish-law-mcp-server (bulk vs single-record) and ukraine-prozorro-tenders versus cee-public-tenders (Ukraine subset), but the bulk-vs-interactive and country-scope hints resolve most of that.
All names use the same kebab-case, source-plus-registry pattern (e.g. polish-vehicle-registrations-cepik, polish-healthcare-facilities-rpwdl), which is readable and predictable. The only deviation is the prefix: most tools start with 'polish-' while cee-public-tenders, ukraine-prozorro-tenders and polish-law-mcp-server break the pattern slightly, and names describe sources rather than verb_noun actions.
17 tools is on the heavy side, but each corresponds to a genuinely separate public registry or feed, so none looks redundant filler. A single-record helper (polish-law-mcp-server) duplicates two bulk tools' domains, which is the only thing pushing it above a tighter scope.
Coverage of Polish public data is broad: legal acts and judgments, company registers (KRS, REGON, CEIDG, MSiG notices), procurement, energy, housing, vehicles/EV, parcels, healthcare and building permits. Remaining gaps are the main Polish procurement platform (e-Zamówienia/TED for Poland) and financial-statement data, but these are workaround-able and read-only query tools need no write lifecycle.