Back to Browse

Chestnyi Znak MCP Server

Developer ToolsModerate7.3MCP RegistryLocal
Free

Server data from the Official MCP Registry

MCP server for Chestnyi Znak — Russian product marking system. 10 tools: codes, documents, stocks.

About

MCP server for Chestnyi Znak — Russian product marking system. 10 tools: codes, documents, stocks.

Security Report

7.3
Moderate7.3Low Risk

Valid MCP server (7 strong, 3 medium validity signals). 3 known CVEs in dependencies (0 critical, 3 high severity) Package registry verified. Imported from the Official MCP Registry. Trust signals: trusted author (4/4 approved).

10 files analyzed · 4 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Chestnyi Znak API token. Obtain in your personal cabinet at markirovka.crpt.ru. IMPORTANT: token expires every 8–10 hours and must be refreshed.Required

Environment variable: CHZ_TOKEN

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-woyaxnini-chestnyi-znak": {
      "env": {
        "CHZ_TOKEN": "your-chz-token-here"
      },
      "args": [
        "-y",
        "@woyax/mcp-chestnyi-znak"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

@woyax/mcp-chestnyi-znak

License: MIT + Commons Clause

MCP server for Chestnyi Znak (Честный Знак) — Russia's national product labelling system (True API).

Enables AI assistants (Claude, Cursor, etc.) to query marking codes, documents, warehouse balances, and participant data directly via natural language.

First MCP server for Chestnyi Znak True API.


Tools (10 total)

Documents & Marking Codes

ToolDescription
chz_doc_listList documents for a product group
chz_doc_infoGet details of a specific document by ID
chz_doc_cis_listList marking codes included in a document
chz_cis_searchSearch marking codes by filter criteria
chz_cis_infoGet public info for a list of CIS codes
chz_product_infoGet product card by GTIN

Balance & Reference

ToolDescription
chz_balance_allBalance of marking codes across all product groups
chz_warehouse_balanceVirtual warehouse balance for a product group
chz_participant_checkCheck company registration status by INN
chz_receipt_listList withdrawal receipts for a product group

Development of new tools is ongoing.


Getting a Token

This server requires a JWT token from your Chestnyi Znak personal account. Token acquisition involves GOST cryptography (КриптоПро + УКЭП) and is outside the scope of this package.

Token retrieval can be automated — using a local КриптоПро script, a signing microservice, USB-over-IP with a hardware token, or a cloud HSM. It can also be done manually via the Chestnyi Znak web interface. The right approach depends on your infrastructure, OS, certificate type, and security requirements. Because the options and constraints vary significantly from case to case, this is treated as a separate integration task. We handle this kind of setup as well — feel free to reach out.

Token lifetime: ~8–12 hours. Update the file when it expires — the server picks it up automatically without restart.


Installation & Configuration

Claude Desktop

Add to your claude_desktop_config.json:

Sandbox:

{
  "mcpServers": {
    "chestnyi-znak": {
      "command": "npx",
      "args": ["-y", "@woyax/mcp-chestnyi-znak"],
      "env": {
        "CHZ_TOKEN_FILE": "/path/to/your/token",
        "CHZ_ENV": "sandbox"
      }
    }
  }
}

Production:

{
  "mcpServers": {
    "chestnyi-znak": {
      "command": "npx",
      "args": ["-y", "@woyax/mcp-chestnyi-znak"],
      "env": {
        "CHZ_TOKEN_FILE": "/path/to/your/token"
      }
    }
  }
}

CHZ_ENV defaults to "prod" if not set.

Important: the token file and the CHZ_ENV value must match — a sandbox token won't work on the production endpoint and vice versa.


Environment Variables

VariableRequiredDefaultDescription
CHZ_TOKEN_FILEYesAbsolute path to file containing the JWT token
CHZ_ENVNoprodContour: sandbox or prod

Author & Support

Built by Oleg Alekseev — ERP/AI integration architect.

Need help integrating AI agents with your ERP, CRM, or Chestnyi Znak? Custom MCP servers, n8n workflows, AI automation — contact me.


License

MIT + Commons Clause © Oleg Alekseev

Free to use for personal and corporate purposes. Selling as a hosted service requires author's permission. See LICENSE for details.

Reviews

No reviews yet

Be the first to review this server!