mcp-yandex-dostavka

MCPcommunity
v1.1.0Aleksandr KovalkoMITUpdated 1mo agonpmGitHub

MCP server for the Yandex Delivery B2B API (dostavka.yandex.ru) — express-courier price checks, claims and tracking plus NDD/pickup-point offers and orders for AI agents.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
310Downloads/wk
1mo agoLast update
Package
AuthorAleksandr Kovalko
LicenseMIT
Version1.1.0
Sourcenpm+mcp-registry
npmmcp-yandex-dostavka
GitHubA1-x-Tech/mcp-yandex-dostavka
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface16 tools · none privileged
Security scan✓ Cleanv1.0.0 · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 11, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

16 tools · none privileged
Statically extracted from the published packagev1.0.0 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

express_check_priceNo description published

This tool published no description. Forge does not invent one.

express_create_claimNo description published

This tool published no description. Forge does not invent one.

express_get_claimNo description published

This tool published no description. Forge does not invent one.

express_accept_claimNo description published

This tool published no description. Forge does not invent one.

express_cancel_infoNo description published

This tool published no description. Forge does not invent one.

express_cancel_claimNo description published

This tool published no description. Forge does not invent one.

express_search_claimsNo description published

This tool published no description. Forge does not invent one.

express_performer_positionNo description published

This tool published no description. Forge does not invent one.

express_tracking_linksNo description published

This tool published no description. Forge does not invent one.

platform_list_pickup_pointsNo description published

This tool published no description. Forge does not invent one.

platform_create_offersNo description published

This tool published no description. Forge does not invent one.

platform_confirm_offerNo description published

This tool published no description. Forge does not invent one.

platform_get_requestNo description published

This tool published no description. Forge does not invent one.

platform_request_historyNo description published

This tool published no description. Forge does not invent one.

platform_cancel_requestNo description published

This tool published no description. Forge does not invent one.

raw_requestNo description published

This tool published no description. Forge does not invent one.

0 of 16 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for the Yandex Delivery B2B API (dostavka.yandex.ru) — express-courier price checks, claims and tracking plus NDD/pickup-point offers and orders for AI agents.

Keywords
mcpmodel-context-protocolyandexyandex-dostavkayandex-deliverydeliverylogisticscourierexpress-deliverypickup-points
Alternatives
Comparing tool surfaces…

Tools exposed

16 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.