MXIK codes (Uzbekistan)

What MXIK codes (Uzbekistan) MCP server does

The MXIK codes (Uzbekistan) MCP server connects AI assistants to the national catalogue of goods and services published through tasnif.soliq.uz. It is based on the mxik typed JavaScript client and uses the public API behind that site. The project is unofficial and is not affiliated with Uzbekistan’s Tax Committee or with tasnif.soliq.uz.

The server is suited to agents that need to find a product or service classification code, inspect the details attached to a known code, or explore the catalogue hierarchy. Searches can use a general text query, while filters can target text, brand, code, or barcode. Certificate-number searches are also available.

How it works

The MCP package is run as a local command and communicates with an MCP-compatible assistant. Its documented launch command is:

claude mcp add mxik -- npx -y mxik-mcp

Requests are sent to the API associated with tasnif.soliq.uz. Results are returned as structured catalogue data rather than raw API envelopes. The underlying client supports Russian or Uzbek language selection, pagination, request timeouts, and abort signals. It can also lazily iterate through all pages when a search or filter produces more results than one page can contain.

The upstream API is not documented and can change. It may also reject requests from servers outside Uzbekistan. Test connectivity in the deployment environment before relying on the server, or configure the client’s base URL to use a proxy where appropriate.

Setup and configuration

Install and run the MCP package with npx -y mxik-mcp. The README specifically documents Claude and Cursor usage and links to additional client guidance. No environment variables are documented as required.

The underlying client uses https://tasnif.soliq.uz/api/cls-api by default. Client options include lang, pageSize, timeout, cache, baseURL, a custom fetch implementation, and additional request headers. Caching is disabled by default, but the client can use an in-memory cache or a compatible custom implementation. Successful responses and not-found results may be cached; errors are not.

Tools and capabilities

The available catalogue operations correspond to the client API and include:

• Search the catalogue using a text query.
• Filter by text, brand, MXIK code, or barcode.
• Retrieve details or a card for one code.
• Find codes associated with a certificate number.
• Search product subpositions without a brand.
• Browse the next level of the catalogue tree or all child entries.
• Read catalogue statistics, measurement units, and tax-benefit reference data.
• Process paginated results one page at a time or iterate through all results.
• Validate the 17-digit MXIK code format through the underlying library.

A missing code returns no result, and an unsuccessful match returns an empty page. HTTP failures and unsuccessful API responses use the client’s MxikError; timeouts, aborted requests, and network failures have separate error behavior.

Limitations and notes

The MXIK codes (Uzbekistan) MCP server depends on an unofficial, undocumented public API. Availability and response behavior can therefore change independently of the package. Network location is important because the catalogue may not respond to hosts outside Uzbekistan.

The source project is licensed under MIT. The README documents the MCP package and its Claude and Cursor usage, but it does not provide a complete list of agent-facing tool names or a separate MCP configuration schema. Treat the underlying catalogue as the source of classification data and verify important results when regulatory or tax decisions depend on them.