Skip to main content
Glama
kamilkaczmareksolutions

Polish MCP Servers

by kamilkaczmareksolutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Polish MCP Servers

No user-submitted related servers found.

    Related Servers

    • US Government Data

      CBLU2005
      A
      license
      A
      quality
      C
      maintenance
      Search 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.
      3
      MIT

    • @m8t-jacob/mcp-polish-biz

      M8T-Jacob
      A
      license
      A
      quality
      D
      maintenance
      MCP 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.
      5
      7 npm
      MIT

    • mcp-polska

      auto-mate-pl
      A
      license
      A
      quality
      C
      maintenance
      Gives Claude direct, keyless access to Polish public registries: it validates NIP checksums, checks a company's VAT status and bank account against the VAT whitelist, pulls KRS court-registry extracts, and fetches the correct NBP exchange rate for an invoice date. Runs locally as an MCP server for Claude Desktop, Claude Code, Cursor and other MCP clients.
      5
      MIT

    • eu-nordic-open-data-mcp

      itulo
      A
      license
      B
      quality
      C
      maintenance
      Unified 36-tool MCP server and 10-server suite for official EU and Finnish open data (TED tenders, PRH companies, EU sanctions, VIES VAT, ECB FX rates, ENISA EUVD CVEs, Fingrid grid, FMI weather, Digitraffic).
      36
      MIT

    • rejestr-io-mcp

      QuverLabs
      F
      license
      A
      quality
      D
      maintenance
      MCP 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
      -

    • polish-caselaw-mcp

      PawelHaracz
      A
      license
      A
      quality
      B
      maintenance
      MCP server for querying live Polish court case law (orzecznictwo) via the SAOS API, offering tools to search judgments, fetch full cases, find judgments citing specific statutory provisions, and check Constitutional Tribunal citations.
      7
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 14 tools

    Disambiguation4/5

    Domains are cleanly separated by source register (companies, permits, energy, prices, acts, tenders, EV, vehicles, procurement, parcels, healthcare, judgments), and the descriptions explicitly decouple the risky pairs (bulk ELI/SAOS vs. single-act/judgment lookup in polish-law-mcp-server; known-company REGON lookup vs. newly registered KRS companies). The residual overlap is mild: polish-law-mcp-server still re-exposes search/get semantics already offered by polish-legal-acts-eli and polish-court-judgments-saos, and polish-company-lookup-regon vs. polish-new-companies-krs will occasionally be misselected by a naive agent that doesn't parse the 'identity vs. changes feed' distinction.

    Naming Consistency4/5

    Names follow a stable kebab-case '<geography/topic>-<domain>-<source-register>' pattern (polish-vehicle-registrations-cepik, polish-court-judgments-saos, polish-eu-funds-tenders-baza-konkurencyjnosci), so the convention is readable and predictable. Deviations are minor but present: cee-public-tenders drops the geography prefix entirely, and polish-law-mcp-server names itself after the implementation actor rather than the data source, breaking the domain-source pattern.

    Tool Count5/5

    Fourteen tools for a multi-register public-data aggregator is well within a comfortable range: each tool maps to one official source with a distinct value proposition, and nothing looks like a thin wrapper kept only for symmetry. The shared contract (APIFY_TOKEN, maxItems, items/truncated envelope) also means the count adds breadth rather than cognitive overhead.

    Completeness4/5

    Coverage across Polish public registers is genuinely broad — company identity and KRS change feeds, procurement (Polish and CEE), construction permits, land/zoning, healthcare, courts, legislation, energy, housing and vehicle fleet. Gaps remain for the domain as implied: no KRS financial statements, no land-registry (księgi wieczyste) owner/mortgage data, no address geocoding or TERYT gazetteer tool, and no write/monitoring helper beyond the onlyNew stateKey convention, so some workflows dead-end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources