
Chestnyi Znak MCP Server
io.github.woyaxniniPublished by GitHub account woyaxniniv0.1.1Updated Oct 24, 2026
MCP server for Chestnyi Znak — Russian product marking system. 10 tools: codes, documents, stocks.
Overview
A local MCP server that lets an assistant query Russia's Chestnyi Znak product labelling system for marking codes, documents, warehouse balances and company or,
- What you can do
- List and inspect documents for a product group, and read the marking codes inside a document or by filter criteria, including public info for a list of codes and product cards by GTIN. Check marking-code balances across all product groups and virtual warehouse balances for one group. Look up a company's registration status by INN and list withdrawal receipts for a product group.
- When to use it
- Useful when you work with Russian product marking compliance and want to look up documents, marking codes, balances or counterparty registration in natural language instead of the Chestnyi Znak web interface.
- Requirements
- Runs locally via npx, so Node.js is needed. Requires a Chestnyi Znak JWT token, supplied as a file path in CHZ_TOKEN_FILE; the token is obtained separately from your personal account and involves GOST cryptography. CHZ_ENV selects sandbox or prod and defaults to prod.
Installation
In SourceWeft
- Open Chestnyi Znak MCP Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
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
Balance & Reference
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:
Production:
CHZ_ENV defaults to "prod" if not set.
Important: the token file and the
CHZ_ENVvalue must match — a sandbox token won't work on the production endpoint and vice versa.
Environment Variables
Author & Support
Built by Oleg Alekseev — ERP/AI integration architect.
- 📧 [email protected] · [email protected]
- 💬 Telegram: @ale_oleg · Channel: @woyax_ai
- 💬 MAX: max.ru/id503610654564_biz
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.
Source: README.md at commit 52c24ab
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.