Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Yango Delivery MCP

NPM · MCP-YANGO-DELIVERY

MCP server for the Yango Delivery claims B2B API: price checks, delivery claims, courier tracking.

Available components

0 this week 78 Trust /100

Last scanned (12 hours ago)

Scores higher than 59% of npm servers

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2644 tokens (~203/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Nov 26 +1
    • Stability: 0.97 → pass security
    • Package version: 1.0.0 → 1.2.1 functional
  • 17 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 5 Nov 26 −3
    • Stability: pass → 0.80 functional
  • 1 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 −15
    • Known CVEs: fail → unverified ▼ security
    • Malware scan: pass → unverified ▼ security
    • Dependency health: 0.85 → unverified ▼ functional
    • Package version: 1.1.0 → 1.2.1 functional
    • Package version: 1.1.0 → 1.2.0 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/mcp-yango-delivery@1.2.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~2,331 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
accept_claim ~140

Confirms a claim after successful estimation (status ready_for_approval) and starts the courier search — from this point the delivery is actually ordered. The priced offer inside a claim expires ~10 minutes after estimation, so accept promptly. version comes from get_claim. 409 errors: inappropriate_status (wrong claim status), old_version (stale version — re-read the claim), offer_expired (re-create the claim), state_mismatch.

NameTypeReqDescription
claim_idstringyesClaim id (claim_id, 32–64 characters) from the create_claim or search_claims response.
versionintegeryesClaim version from the latest get_claim response.

No output schema declared.

No examples provided.

cancel_claim ~132

Cancels a claim (including an already accepted one). Get the terms with get_cancel_info first and pass its cancel_state: with paid the cancellation fee is charged. version comes from get_claim. 409 errors: old_version, inappropriate_status, free_cancel_is_unavailable.

NameTypeReqDescription
cancel_statestringyesCancellation mode from get_cancel_info: free — no charge, paid — a fee applies.
claim_idstringyesClaim id (claim_id, 32–64 characters) from the create_claim or search_claims response.
versionintegeryesClaim version from the latest get_claim response.

No output schema declared.

No examples provided.

check_price ~183

Preliminary delivery cost estimate WITHOUT creating a claim — the pricing method for countries outside Russia. Returns price (a decimal STRING, not a number!), currency_rules {code, sign, template}, distance_meters, eta (minutes) and zone_id. Route points take [longitude, latitude] coordinates and/or a full address string. Typical errors: 400 address_not_found (address not recognized), 409 estimating.cant_construct_route (no route between the points), 409 estimating.requirement_unavailable.

NameTypeReqDescription
itemsarrayyesItems / cargo places.
requirementsobject–Delivery requirements (class, body type, extra options).
route_pointsarrayyesRoute points: coordinates and/or an address (at least one of the two per point).
skip_door_to_doorboolean–true — disable door-to-door delivery (default false).

No output schema declared.

No examples provided.

create_claim ~459

Creates a delivery claim. IMPORTANT: the claim is NOT dispatched immediately — it goes through estimation (status: new → estimating → ready_for_approval) and must then be confirmed with accept_claim, or pass auto_accept=true. Returns id (claim_id), status, version, route_points, pricing, created_ts. Verify success via get_claim: estimation errors can arrive as an error_messages array inside a 200 response. request_id makes the call idempotent: a retry with the same request_id returns the same claim, not a duplicate.

NameTypeReqDescription
auto_acceptboolean–true — confirm the claim automatically after successful estimation (no accept_claim needed).
callback_propertiesobject–Webhook for claim status changes.
client_requirementsobject–Delivery requirements. Optional per the docs, but always passing taxi_class is safest.
commentstring–Comment for the courier (up to 7000 characters).
duestring–Desired courier arrival time (ISO-8601), e.g. 2026-08-10T12:00:00+05:00.
emergency_contactobject–Contact to reach if there is a problem with the delivery.
itemsarrayyesItems to deliver.
optional_returnboolean–true — the courier does not return items to the sender when hand-over fails.
request_idstring–Idempotency token (1–128 characters, a query parameter). A UUID is generated automatically when omitted.
route_pointsarrayyesRoute points (at least 2): a source and a destination at minimum.
same_day_dataobject–Same-day delivery settings: {delivery_interval: {from, to}} (a non-Russia feature).
shipping_documentstring–Accompanying shipping document reference.
skip_actboolean–true — do not generate a handover act.
skip_client_notifyboolean–true — do not send SMS/push notifications to the recipient.
skip_door_to_doorboolean–true — no door-to-door: hand over at the entrance.
skip_emergency_notifyboolean–true — do not notify the emergency contact.

No output schema declared.

No examples provided.

get_cancel_info ~87

Cancellation terms for a claim — call BEFORE cancel_claim. Returns cancel_state: free (free of charge), paid (a fee applies — price/price_with_vat and currency are returned) or unavailable (the claim can no longer be cancelled).

NameTypeReqDescription
claim_idstringyesClaim id (claim_id, 32–64 characters) from the create_claim or search_claims response.

No output schema declared.

No examples provided.

get_claim ~220

Full claim information: status, version (needed for accept/cancel), items, route_points (with visit status), pricing {offer, final_price, currency}, performer_info (courier name, vehicle, transport type), eta, created_ts/updated_ts. Known statuses: new, estimating, estimating_failed, ready_for_approval, accepted, performer_lookup, performer_draft, performer_found, performer_not_found, pickup_arrived, ready_for_pickup_confirmation, pickuped, delivery_arrived, ready_for_delivery_confirmation, delivered, delivered_finish, pay_waiting, returning, return_arrived, ready_for_return_confirmation, returned, returned_finish, failed, cancelled, cancelled_with_payment, cancelled_by_taxi, cancelled_with_items_on_hands. CAUTION: estimation errors can arrive as an error_messages array [{code, message}] inside a successful 200 response — check both the HTTP error and this field.

NameTypeReqDescription
claim_idstringyesClaim id (claim_id, 32–64 characters) from the create_claim or search_claims response.

No output schema declared.

No examples provided.

get_confirmation_code ~86

Pickup/delivery confirmation code for the current point of the claim (when a code applies). Returns code (string) and attempts (remaining code entry attempts). 404 — claim not found or issuing a confirmation code via the API is prohibited.

NameTypeReqDescription
claim_idstringyesClaim id (claim_id, 32–64 characters) from the create_claim or search_claims response.

No output schema declared.

No examples provided.

get_courier_phone ~134

Temporary forwarded phone number to call the courier of an active claim: phone (e.g. "+79099999998"), ext (extension, e.g. "0163") and ttl_seconds (how long the number stays operational). Errors: 400 invalid_point_phone; 404 — claim or courier not found; 409 inappropriate_status (the order is already completed).

NameTypeReqDescription
claim_idstringyesClaim id (claim_id, 32–64 characters) from the create_claim or search_claims response.
point_idinteger–Route point the contact person calls from (int64 point id).

No output schema declared.

No examples provided.

get_performer_position ~108

Current courier geoposition for an active claim: position {lat, lon, timestamp (unix), accuracy, speed (m/s), direction (0–360°, clockwise from north)} and route_points with sharing_link. Errors: 404 — claim or courier position not found, 409 — the claim is not active or no courier is assigned.

NameTypeReqDescription
claim_idstringyesClaim id (claim_id, 32–64 characters) from the create_claim or search_claims response.

No output schema declared.

No examples provided.

get_points_eta ~133

Expected arrival times per route point plus the current courier position. Works only while the claim is active and a courier is assigned. Returns route_points [{id, address, type, visit_order, visit_status (pending|arrived|visited|skipped), visited_at {expected, expected_waiting_time_sec, actual}}] and performer_position. Errors: 404 not_found; 409 — the claim is inactive, has no courier, or the courier position is unknown.

NameTypeReqDescription
claim_idstringyesClaim id (claim_id, 32–64 characters) from the create_claim or search_claims response.

No output schema declared.

No examples provided.

get_tracking_links ~87

Public courier tracking links — safe to share with the recipient. Returns route_points [{id, type, visit_order, sharing_link}]; sharing_link is available only for type=destination points. 409 errors: inappropriate_status, unknown_tracking_links.

NameTypeReqDescription
claim_idstringyesClaim id (claim_id, 32–64 characters) from the create_claim or search_claims response.

No output schema declared.

No examples provided.

raw_request ~207

Escape hatch: a direct call to any method of the Yango Delivery claims B2B API — for endpoints without a dedicated tool (tariffs, delivery-methods, claims/proof-of-delivery/info, claims/edit, claims/apply-changes, claims/return, claims/bulk_info, claims/journal, …). Paths are relative to the API root, e.g. "b2b/cargo/integration/v2/tariffs". query becomes the query string, body is sent as JSON. CAUTION: this tool can perform state-changing operations; 5xx/network errors are retried only for GETs.

NameTypeReqDescription
bodyobject–JSON request body.
methodstring–HTTP method; defaults to POST.
pathstringyesRelative API path, e.g. "b2b/cargo/integration/v2/claims/bulk_info".
queryobject–Query-string parameters, e.g. {"claim_id": "..."}.

No output schema declared.

No examples provided.

search_claims ~355

Search claims by filters with pagination (sorted by creation date). Returns claims (each shaped like get_claim) and a cursor for the next page. Pagination: either offset/limit, or cursor-based — pass the cursor from the previous response (other filters are then not needed).

NameTypeReqDescription
claim_idstring–Filter by claim id.
created_fromstring–Created no earlier than (ISO-8601).
created_tostring–Created no later than (ISO-8601).
cursorstring–Cursor from the previous response — an alternative to offset/limit.
due_fromstring–Courier arrival no earlier than (ISO-8601).
due_tostring–Courier arrival no later than (ISO-8601).
external_order_idstring–Filter by the external order id.
limitinteger–How many claims to return (up to 1000).
offsetinteger–Offset for offset/limit pagination (default 0).
phonestring–Filter by a phone number from the claim contacts.
statestring–Status group: active, finished or delayed claims.
statusstring–Filter by status. Known statuses: new, estimating, estimating_failed, ready_for_approval, accepted, performer_lookup, performer_draft, performer_found, performer_not_found, pickup_arrived, ready_for_…

No output schema declared.

No examples provided.

Install

How do I install the Yango Delivery MCP server?

Yango Delivery MCP runs locally as an npm package, launched with npx -y mcp-yango-delivery. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · mcp-yango-delivery

# add to Claude Code
claude mcp add a1-x-tech-mcp-yango-delivery -- npx -y mcp-yango-delivery
Common questions

What is the Yango Delivery MCP server?

Yango Delivery MCP is listed in the public MCP registry as io.github.A1-x-Tech/mcp-yango-delivery. MCP server for the Yango Delivery claims B2B API: price checks, delivery claims, courier tracking. This page covers its npm package (mcp-yango-delivery).

Is the Yango Delivery MCP server safe to use?

Yango Delivery MCP scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Yango Delivery MCP server expose?

Yango Delivery MCP exposes 13 tools: check_price, create_claim, get_claim, accept_claim, get_cancel_info, and 8 more. Their descriptions and schemas cost roughly 2,331 tokens of context every time the server is loaded.

Is the Yango Delivery MCP server still maintained?

Yango Delivery MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Yango Delivery MCP server under?

Yango Delivery MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Yango Delivery MCP server?

VerifyMCP ran 16 checks on Yango Delivery MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.