diadoc-mcp-ru
Related Servers
Alternatives to diadoc-mcp-ru
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceSBIS (Saby) API for AI assistants: documents and their workflow stages, electronic signature, certificates, employees and organizations. 45 methods, each with a read/write/destructive safety class.1851 PyPI6MIT
- AlicenseAqualityAmaintenanceChestny ZNAK (Russian mandatory product marking, GIS MT and SUZ) API for AI assistants: marking codes, emission orders, circulation documents and code checks. 33 methods, each with a read/write/destructive safety class.183MIT
- AlicenseAqualityAmaintenanceVK API for AI assistants: wall posts, communities, messages, market items, ads and stats. 373 methods in one catalog, each with a read/write/destructive safety class; the agent searches methods in plain language instead of receiving 373 tools.1870 PyPI3MIT

fynk MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI clients to run the full contract lifecycle on the fynk platform — drafting templates, finding and analyzing contracts, creating them from templates or uploaded PDFs, filling dynamic fields, managing parties and signatories, and moving contracts through review, signing and archiving. It acts with the connected user's own fynk permissions, with changes recorded in the document audit trail.12MIT- AlicenseAqualityDmaintenanceEnables AI assistants to manage document signing workflows via natural language, including creating envelopes, uploading documents, analyzing contracts, and verifying blockchain anchors.822 npm1MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage eSignature workflows, including creating signing tasks, tracking document status, and managing templates via natural language.142-
TDQS
Scored across 18 tools
There is meaningful overlap among the catalog discovery tools (list_sections, get_section, search_methods, map, describe_method) and between the catalog execution methods and raw-path execution methods (call_method vs get_raw, write_method vs write_raw). Descriptions do clarify the differences, but an agent could easily hesitate or misselect when deciding which discovery or execution tool to use.
The tools all share the diadoc_ prefix and mostly follow a verb_noun pattern (list_sections, add_cabinet, delete_method). A few deviations exist, such as diadoc_map (no verb) and diadoc_fetch_all, but overall the naming is predictable and readable.
18 tools is on the heavier side but each tool serves a distinct layer: catalog discovery, safe execution, destructive execution, raw fallback, pagination, and cabinet/auth management. The count is slightly over the ideal range but justified by the server's broad scope.
The tool surface covers the full lifecycle: credential checking, cabinet management, key rotation, catalog exploration, read/write/delete operations, raw endpoint access for uncataloged paths, and pagination. The raw execution tools guarantee that no API endpoint is unreachable, making the surface effectively complete for the stated purpose.