{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-poland-krs","slug":"poland-krs","name":"Poland KRS","type":"mcp","url":"https://github.com/pkolawa/krs-poland-mcp-server","page_url":"https://unfragile.ai/poland-krs","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-poland-krs__cap_0","uri":"capability://tool.use.integration.polish.business.entity.lookup.via.krs.api.integration","name":"polish business entity lookup via krs api integration","description":"Queries the Polish National Court Register (KRS) API to retrieve authoritative business entity data including company names, registration numbers, legal status, and organizational details. The MCP server acts as a standardized interface layer that translates client requests into KRS API calls, handling authentication, rate limiting, and response parsing to expose entity information through a unified protocol.","intents":["Look up a Polish company's official registration details and legal status","Verify if a business entity exists in the KRS registry","Retrieve company identification numbers and official names for compliance checks","Integrate Polish business data into due diligence or KYC workflows"],"best_for":["Polish fintech and compliance teams building KYC/AML systems","International businesses conducting due diligence on Polish counterparts","LLM agents requiring authoritative business entity verification","Developers building Polish business intelligence tools"],"limitations":["Dependent on KRS API availability and uptime — no local caching mechanism documented","Query latency varies with KRS API response times (typically 500ms-2s per request)","Limited to Polish legal entities only — no cross-border entity lookup","No bulk query optimization — each entity lookup requires a separate API call"],"requires":["Network connectivity to KRS API endpoints","MCP client implementation (Claude Desktop, custom MCP runner, or compatible tool)","No explicit API key requirement documented (KRS appears to be public access)"],"input_types":["text (company name or registration number)","structured queries (entity identifiers)"],"output_types":["structured data (JSON entity records)","text (formatted business information)"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-poland-krs__cap_1","uri":"capability://tool.use.integration.mcp.based.tool.registration.for.krs.queries","name":"mcp-based tool registration for krs queries","description":"Implements the Model Context Protocol (MCP) server specification to register KRS lookup as a callable tool that AI agents can discover and invoke. The server exposes tool schemas (name, description, input parameters) that conform to MCP's tool-calling standard, allowing compatible clients to understand available KRS operations and construct properly-formatted requests without hardcoding API details.","intents":["Enable Claude and other MCP clients to discover available KRS lookup operations","Allow AI agents to autonomously decide when and how to query KRS data","Provide structured tool schemas that guide LLM function calling with proper parameter validation","Integrate KRS lookups into multi-step agent workflows without manual API orchestration"],"best_for":["AI agent developers building autonomous business verification workflows","Teams using Claude with MCP for Polish business intelligence tasks","Builders creating AI-powered compliance and due diligence systems","Developers integrating multiple data sources through MCP protocol"],"limitations":["Requires MCP-compatible client — not usable with standard REST API clients or curl","Tool schema complexity depends on KRS API parameter support — may require schema updates if KRS API changes","No built-in error recovery or retry logic documented — relies on client-side handling","Single-tool server design — no batching or multi-operation transactions"],"requires":["MCP client implementation (Claude Desktop, Cline, or custom MCP runner)","Node.js runtime (assumed from GitHub repo structure)","Understanding of MCP protocol and tool-calling conventions"],"input_types":["structured tool parameters (entity name, registration number, search filters)"],"output_types":["tool execution results (structured entity data)","error messages with diagnostic context"],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-poland-krs__cap_2","uri":"capability://data.processing.analysis.entity.data.normalization.and.schema.mapping","name":"entity data normalization and schema mapping","description":"Transforms raw KRS API responses into normalized, structured data formats suitable for downstream processing. The server parses KRS API JSON responses and maps fields to consistent schemas, handling variations in data representation, null values, and optional fields to ensure predictable output structure for client applications and AI agents consuming the data.","intents":["Standardize KRS entity data into consistent JSON schemas for downstream processing","Handle missing or optional fields gracefully without breaking client parsing logic","Map KRS API field names to human-readable or application-specific field names","Ensure data type consistency (dates, numbers, strings) across all entity records"],"best_for":["Data pipeline builders integrating KRS data into data warehouses","Teams building business intelligence dashboards from KRS data","Developers creating normalized entity databases from multiple sources","AI systems requiring consistent input formats for entity analysis"],"limitations":["Schema mapping is static — changes to KRS API response format require code updates","No schema versioning documented — clients may break if KRS API evolves","Limited field transformation capabilities — complex business logic must be handled downstream","No data validation or constraint checking beyond basic type coercion"],"requires":["KRS API response format knowledge (schema must be maintained in code)","JSON parsing and transformation library (likely built-in Node.js JSON support)"],"input_types":["raw JSON (KRS API responses)"],"output_types":["normalized JSON (standardized entity schemas)","structured data (consistent field types and names)"],"categories":["data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-poland-krs__cap_3","uri":"capability://data.processing.analysis.polish.legal.entity.type.classification.and.metadata.extraction","name":"polish legal entity type classification and metadata extraction","description":"Extracts and classifies entity type information from KRS records (e.g., spółka z ograniczoną odpowiedzialnością, spółka akcyjna, fundacja, stowarzyszenie) and provides structured metadata about legal entity characteristics. The server parses KRS entity type codes or descriptions and maps them to standardized classifications, enabling downstream systems to understand entity legal structure without manual interpretation.","intents":["Determine the legal structure of a Polish business entity for compliance classification","Filter entities by type (e.g., find only limited liability companies vs. sole proprietorships)","Extract entity governance and liability information from KRS type data","Classify entities for regulatory reporting or risk assessment workflows"],"best_for":["Compliance and regulatory teams assessing Polish business entity types","Risk assessment systems requiring entity structure classification","AI agents performing entity categorization for business intelligence","Teams building Polish business data analytics platforms"],"limitations":["Classification depends on KRS data completeness — some entities may have incomplete type information","Polish-specific entity types may not map cleanly to international business classifications","No historical entity type tracking — cannot determine if entity type changed over time","Limited metadata extraction — only type information, not detailed governance structures"],"requires":["Knowledge of Polish legal entity types and their KRS representations","Mapping tables or enums for entity type classification (must be maintained in code)"],"input_types":["KRS entity records (containing type codes or descriptions)"],"output_types":["structured entity type metadata (classification, legal structure, liability type)","text (human-readable entity type descriptions)"],"categories":["data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-poland-krs__cap_4","uri":"capability://search.retrieval.krs.search.and.filtering.with.query.parameter.handling","name":"krs search and filtering with query parameter handling","description":"Accepts structured search parameters (company name, registration number, location, entity type filters) and constructs appropriate KRS API queries with proper parameter encoding and validation. The server translates client-provided search criteria into KRS API-compatible query strings, handling special characters, Polish diacritics, and parameter combinations to enable flexible entity searches without exposing raw API complexity.","intents":["Search for Polish companies by name with fuzzy or exact matching","Look up entities by KRS registration number (REGON or KRS number)","Filter entities by location, entity type, or other KRS-supported criteria","Construct complex multi-parameter searches for advanced business intelligence queries"],"best_for":["Business intelligence teams building Polish company search interfaces","Compliance systems requiring flexible entity lookup capabilities","AI agents performing autonomous business entity discovery","Developers building Polish business data aggregation tools"],"limitations":["Search capabilities limited to KRS API supported parameters — no custom filtering logic","Polish diacritics handling depends on KRS API encoding support — may require client-side normalization","No full-text search optimization — KRS API may not support advanced search syntax","Search result pagination not documented — may return limited result sets per query"],"requires":["Understanding of KRS API query parameter format and supported search fields","URL encoding and parameter validation library (likely built-in Node.js support)"],"input_types":["text (company name, search terms)","structured parameters (registration numbers, filters, search options)"],"output_types":["search results (entity records matching criteria)","structured result sets (paginated or ranked results)"],"categories":["search-retrieval","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":29,"verified":false,"data_access_risk":"high","permissions":["Network connectivity to KRS API endpoints","MCP client implementation (Claude Desktop, custom MCP runner, or compatible tool)","No explicit API key requirement documented (KRS appears to be public access)","MCP client implementation (Claude Desktop, Cline, or custom MCP runner)","Node.js runtime (assumed from GitHub repo structure)","Understanding of MCP protocol and tool-calling conventions","KRS API response format knowledge (schema must be maintained in code)","JSON parsing and transformation library (likely built-in Node.js JSON support)","Knowledge of Polish legal entity types and their KRS representations","Mapping tables or enums for entity type classification (must be maintained in code)"],"failure_modes":["Dependent on KRS API availability and uptime — no local caching mechanism documented","Query latency varies with KRS API response times (typically 500ms-2s per request)","Limited to Polish legal entities only — no cross-border entity lookup","No bulk query optimization — each entity lookup requires a separate API call","Requires MCP-compatible client — not usable with standard REST API clients or curl","Tool schema complexity depends on KRS API parameter support — may require schema updates if KRS API changes","No built-in error recovery or retry logic documented — relies on client-side handling","Single-tool server design — no batching or multi-operation transactions","Schema mapping is static — changes to KRS API response format require code updates","No schema versioning documented — clients may break if KRS API evolves","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.35,"ecosystem":0.39999999999999997,"match_graph":0.25,"freshness":0.6,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-06-17T09:51:04.047Z","last_scraped_at":"2026-05-03T14:00:15.503Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=poland-krs","compare_url":"https://unfragile.ai/compare?artifact=poland-krs"}},"signature":"Hne2d3HHkylFh8nyG+ClWxuTRSwzOiPCQbchL2tKqkDBEdg9/vZD4JAeHSpKtNZzUrgeVfYhnHw+X8Xs/Uj5CQ==","signedAt":"2026-06-19T22:33:35.907Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/poland-krs","artifact":"https://unfragile.ai/poland-krs","verify":"https://unfragile.ai/api/v1/verify?slug=poland-krs","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}