theYahia/yookassa-mcp (theYahia/yookassa-mcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Emerging
74/100
6 days ago

theYahia/yookassa-mcp

MCP server for YooKassa API enabling payments, refunds, receipts, payouts, webhooks, and more via 20 tools.

→ theYahia/yookassa-mcp· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

theYahia

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Known vulnerabilities in dependencies: 1 critical
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 3 credentials: MCP_AUTH_TOKEN, YOOKASSA_PAYOUT_SECRET_KEY, YOOKASSA_SECRET_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 critical

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@3.2.4GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configHTTP_HOSTNo Bind address for HTTP mode (default 127.0.0.1; set 0.0.0.0 to expose — only behind a proxy)
configHTTP_PORTMCP_AUTH_TOKEN="$(openssl rand -hex 32)" =3000 npx -y @theyahia/yookassa-mcp --http
configMCP_ALLOWED_HOSTSNo Comma-separated Host allowlist (default 127.0.0.1:<port>,localhost:<port>)
configMCP_ALLOWED_ORIGINSNo Comma-separated browser Origin CORS allowlist (default: none — browser origins rejected)
🔐 secretMCP_AUTH_TOKEN"$(openssl rand -hex 32)" HTTP_PORT=3000 npx -y @theyahia/yookassa-mcp --http
configYOOKASSA_DEBUGNo Set to 1 to trace each request (method/path/status/latency/idempotency-key) to stderr — never logs secrets, the auth header, or request bodies
configYOOKASSA_PAYOUT_AGENT_IDPayouts Gateway id (agentId) for the Payouts product (Settings -> Payouts)
🔐 secretYOOKASSA_PAYOUT_SECRET_KEYPayouts Secret key for the Payouts gateway
🔐 secretYOOKASSA_SECRET_KEY"": "your-secret-key"
configYOOKASSA_SHOP_ID"": "your-shop-id",
// quality suggestions

Tool annotations

1/20 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

19/20 tools missing one or more hints — create_payment (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_payment (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); capture_payment (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +16 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 3 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/theyahia-yookassa-mcp-16kgl3)](https://m8ven.ai/mcp/theyahia-yookassa-mcp-16kgl3)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 7c1570a078f687ba5c45de31ad12d10e37633400
code hash: 1bf55d8e8f7ee089cc5a048b0d60168dd102ada8e10168d02c54d19d46cf1d5d
verified: 8/20/2026, 9:57:00 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client