chestny-znak-mcp

Chestny ZNAK (GIS MT) and SUZ via MCP

Installs the server crpt-mcp from the package chestny-znak-mcp-ru: 33 methods for marking codes, emission orders, documents and authenticity verification.

Honestly about the catalog source

CRPT documentation opens only after logging in with a qualified electronic signature (KEP); there is no public spec (/api/v3/true-api/swagger.json returns 401). The paths in the catalog are taken from open SDKs and marked verified: false. This is a reconnaissance map: the paths are reliable, but the verbs and parameters must be confirmed on a live environment. The server shows this status in describe_method, so the agent will not pass off a guess as a fact.

Installation

{
  "mcpServers": {
    "crpt": {
      "command": "uvx",
      "args": ["--from", "chestny-znak-mcp-ru", "crpt-mcp"],
      "env": { "CRPT_TOKEN": "<токен ГИС МТ>" }
    }
  }
}

Where to get a token

GET /api/v3/true-api/auth/key returns random data.
Data is signed with a KEP (CryptoPro) on the user's machine.
POST /api/v3/true-api/auth/simpleSignIn exchanges the signature for a token.

The token lives for about 10 hours. Signing happens outside the server: the private key does not reach here and must not. Never ask a person for the certificate itself or the password to the key container.

Typical tasks

Verify marking codes in a batch before acceptance.
View the status of an order for code emission in SUZ.
Upload codes belonging to a participant in circulation.
View the product route by GTIN.

About this skill

Honestly about the catalog source

Installation

Where to get a token

Typical tasks