A
licenseA
qualityA
maintenanceMCP server for the Yango Delivery B2B API, enabling price estimation, express-courier claim creation and confirmation, courier tracking, and recipient tracking links through natural language.
13
81 npm
MIT
mcp-yandex-dostavka
by A1-x-Tech
Related Servers
Alternatives to mcp-yandex-dostavka
No user-submitted related servers found.
Related Servers
- AlicenseDqualityDmaintenanceMCP server for Yandex Delivery API, allowing AI assistants to manage deliveries, track couriers, and handle orders.21MIT
- AlicenseAqualityCmaintenanceMCP server for Yandex Eats Vendor Management API, enabling AI agents to manage partner operations like orders, busy mode, menu import, and feedback.112 npmMIT
- AlicenseAqualityAmaintenanceMCP server for Yandex Merchants API enabling management of product offers (prices, discounts, hide/show) via natural language from AI assistants like Claude and Cursor.1370 npmMIT
- FlicenseNot gradedqualityCmaintenanceMCP server for interacting with Yandex Cloud AI Studio, enabling chat, text generation, image generation, speech recognition/synthesis, embeddings, classification, search indexes, and AI agent creation with function calling.-
- AlicenseAqualityFmaintenanceMCP server for Yandex GPT API enabling text generation, embeddings, classification, summarization, and tokenization.858 npmMIT
TDQS
A4.1/5.0
Scored across 16 tools
Disambiguation5/5
All tools are cleanly separated by domain prefix (express_ vs platform_) and each tool has a distinct purpose: price estimation, claim management, tracking, offers, and order management. No two tools overlap in function; even similar ones like get_claim and search_claims are clearly different (single item vs list).
Naming Consistency4/5
The prefix convention (express_ and platform_) is consistent, and most tools follow a verb_noun pattern (check_price, create_claim, accept_claim, cancel_claim, list_pickup_points, create_offers). However, a few tools are noun phrases without an explicit verb (express_performer_position, express_tracking_links, platform_request_history), creating minor inconsistency. Still, overall naming is predictable and readable.
Tool Count4/5
With 16 tools, the server is slightly over the typical 3–15 range, but the number is justified by covering two distinct delivery contours (express and platform) plus a raw fallback. Each tool serves a clear workflow step, so the count feels appropriate rather than bloated.
Completeness4/5
Core lifecycles are covered for both express (price check, create, get, accept, cancel info/cancel, search, tracking) and platform (list points, create offers, confirm, get, history, cancel). Minor gaps such as dedicated tools for specific edge operations (e.g., proof-of-delivery) are mitigated by the raw_request fallback, but those operations are not first-class tools. This is a solid, nearly complete surface.
Maintenance
ActivityMaintained
ResponsivenessNo issues