Unofficial MCP server for the DIDOX e-document platform (Uzbekistan): read documents, profiles and catalogs from any MCP client
Server has 14 tools with consistent naming (verb_noun pattern: didox_list_*, didox_get_*, didox_create_*, didox_update_*, didox_delete_*). All tools have descriptions (10 - 200 chars, within baseline). Input schemas are present with type definitions and parameter descriptions. However, output schemas are NOT documented, responses are shaped in code but not declared in tool definitions. Error handling is minimal; no recovery guidance or actionable error messages. Descriptions lack dependency hints and prerequisites. No tool annotations (readOnlyHint/destructiveHint) despite clear risk levels. Composition is sound (single responsibility per tool), but some tools accept generic 'payload' objects without schema constraints.
Company/entrepreneur details by TIN or PINFL: names, bank account, MFO, director, OKED, VAT status.
Create a new DIDOX document as an UNSIGNED DRAFT (does NOT sign or send). doctype is the document-type code (e.g. "002" invoice/ЭСФ, "005" act); payload is the doctype-specific document JSON (see DIDOX property-document schemas). Returns the API response, including the new document's id. To then sign/send it the user acts in DIDOX or via E-IMZO — out of scope here.
Delete an UNSIGNED DRAFT document by id. Only drafts can be deleted; signed/sent documents cannot.
Document counts grouped by status code (same filters as the list tool). Remember that status codes are document-type-specific.
Full details of one document by its DIDOX id (json body, parties, signature info). Returns found=false when the document does not exist.
Output schemas not documented. Tools return dict[str, Any] with no declared structure. LLMs cannot plan downstream calls or extract fields reliably.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Tools marked READ_ONLY, WRITE, DESTRUCTIVE in comments but not in schema. Clients cannot infer safety properties.
Generic 'payload' parameter in didox_create_document and didox_update_draft lacks schema constraints. Accepts any object; no validation of doctype-specific structure. LLMs cannot infer required fields.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 56 | <=2025-11-25 | v2 |
Download the printable PDF of a document to a temporary file and return its path and size. Set as_base64=true to additionally inline the content (only honored for files under 100 KB to keep responses small).
Own company profile (requisites, bank, director, VAT fields). is_seller=true returns the seller-context VAT fields.
Bank classifier (bankId + name).
Districts classifier.
List DIDOX documents. owner=0 incoming, owner=1 outgoing. Optional filters: status (single code or comma-separated, e.g. "1" or "0,2"; codes are document-type-specific), doctype (e.g. "002" invoice, "005" act), partner (partner TIN), date_from/date_to (document creation date, yyyy-mm-dd). Returns per-document summaries with both numeric status and a human-readable label.
Measure units (localized via Accept-Language).
Regions classifier.
Update an existing UNSIGNED DRAFT document. Recommended flow: fetch the document with didox_get_document, edit its json body, then resend the FULL payload here. doctype is the document-type code.
VAT registration status of a taxpayer by TIN/PINFL, optionally as of a date (yyyy-mm-dd). Adds a human-readable label for the status code.
No error handling guidance. Tools return None or generic dicts on failure (e.g., didox_get_document returns {found: false}). No recovery hints or actionable error messages.
Catalog tools (didox_list_banks, didox_list_regions, didox_list_districts) have minimal descriptions (<60 chars). No guidance on when to call them or what structure they return.