Yandex Eda MCP Server

yandex-eda-mcp npm v0.1.18

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP-сервер для Яндекс Еды через Playwright (headless): поиск ресторанов, меню, корзина, оформление заказа

View on npm ↗ Raw report (JSON) ↗

Trust grade

97/100

Last scanned 2026-09-07 get badge →

Trust

A · 97/100

Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.

Capability

Minimal

Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.

Coverage

Source

How much the scan could actually inspect. Shallow coverage is stated, never hidden.

A Why this grade threat 99 − adoption risk = 97/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 1.2 = 99. What the published surface and source actually contain:

Points	What was found	Category
−1.2	Package runs install-time scripts MTC-SUP-010	supply-chain

2. Client adoption risk — 99 − 2 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

Points	Adoption-risk factor
−2	publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

low Package runs install-time scripts (postinstall)MTC-SUP-010

"yandex-eda-mcp" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.

Evidence: playwright install chromium

Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.

Location: package yandex-eda-mcp

Tools 18

Each tool and what it can reach — statically extracted from the published source.

add_productno sensitive capability
add_to_cartno sensitive capability
clear_cartno sensitive capability
debug_snapshotno sensitive capability
get_addressno sensitive capability
get_item_optionsno sensitive capability
get_menuno sensitive capability
list_payment_methodsno sensitive capability
list_saved_addressesno sensitive capability
loginno sensitive capability

Show 8 more tools ↓

login_statusno sensitive capability
navigateno sensitive capability
place_orderno sensitive capability
remove_from_cartno sensitive capability
search_productsno sensitive capability
search_restaurantsno sensitive capability
set_addressno sensitive capability
view_cartno sensitive capability

What this scan could not see

Tools were statically extracted from the published source (18 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

Version	Score	Findings	Engine	Scanned
`v0.1.18` latest	A 97/100	1	1.13.0	2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

Markdown (GitHub README)

[![MCP Trust Score](https://mcptrustchecker.com/registry/yandex-eda-mcp/badge.svg)](https://mcptrustchecker.com/registry/yandex-eda-mcp)

HTML

<a href="https://mcptrustchecker.com/registry/yandex-eda-mcp"><img src="https://mcptrustchecker.com/registry/yandex-eda-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>

Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/yandex-eda-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan yandex-eda-mcp --online

Use the free API → How scoring works

More in Browser Automation

Agentql Source verified npm

agentql-mcp

Model Context Protocol (MCP) server that integrates AgentQL data extraction capabilities.

Browser Automation Score 100/100 0 findings 157/wk Cap. Minimal

APIScreenshot Remote

https://apiscreenshot.com/mcp

Screenshot any URL or HTML as PNG/JPEG/WebP from your AI agent. Full-page, clean, no install.

Browser Automation Score 100/100 0 findings Cap. Minimal

Aria51 Source verified npm

@aria51/mcp

MCP server for aria51 accessibility scanner

Browser Automation Score 100/100 0 findings 21/wk Cap. Minimal

Bifrost Source verified npm

@businessmaps/bifrost

Bridge any browser web app to Claude Code via MCP

Browser Automation Score 100/100 0 findings 16/wk Cap. Minimal

Browserbase Official npm

@browserbasehq/mcp

Browserbase’s official MCP server: cloud headless browsers for agents, with sessions and screenshots.

Browser Automation Score 100/100 0 findings 5.3k/wk Cap. Minimal

Browserbase Official npm

@browserbasehq/mcp-server-browserbase

MCP server for AI web browser automation using Browserbase and Stagehand

Browser Automation Score 100/100 0 findings 2.9k/wk Cap. Minimal