exyu-mcp (easingthemes/exyu-mcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

C
Caution
74/100
20 days ago

exyu-mcp

An MCP server that gives AI agents ex-Yugoslav cultural context, resolving cultural references with accurate quotes, attributions, and slang meanings from a citable database.

Caution. Specific findings reduced this grade. They are listed on the page. 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

easingthemes

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 →

Install from

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

// key findings
🚨
Secret credentials may flow to a network call
5 flows detected: OPENSUBTITLES_API_KEY, GROK_API_KEY, OPENAI_EMBEDDING_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🚨
Known vulnerabilities in dependencies: 2 critical, 1 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 6 credentials: ANTHROPIC_API_KEY, GROK_API_KEY, OPENAI_API_KEY, OPENAI_EMBEDDING_API_KEY, OPENSUBTITLES_API_KEY, VOYAGE_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 critical1 high1 medium1 low

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

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

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

criticalvitest@2.1.0GHSA-9crc-q9x8-hgqq

Vitest allows Remote Code Execution when accessing a malicious website while Vitest API server is listening

high@modelcontextprotocol/sdk@1.0.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

mediumajv@8.17.1GHSA-2g4f-4pwh-qvx6

ajv has ReDoS when using `$data` option

lowyaml@2.6.0GHSA-48c2-rrv3-qjmp

yaml is vulnerable to Stack Overflow via deeply nested YAML collections

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.
🔐 secretANTHROPIC_API_KEY/ OPENAI_API_KEY / GROK_API_KEY ingest only key for the selected CHAT_PROVIDER
configCHAT_PROVIDERingest only anthropic \ openai \ grok, default anthropic
configEMBEDDING_PROVIDERyes openai \ voyage \ local, default openai
🔐 secretGROK_API_KEYANTHROPIC_API_KEY / OPENAI_API_KEY / ingest only key for the selected CHAT_PROVIDER
configLOCAL_EMBEDDING_URLOPENAI_EMBEDDING_API_KEY / VOYAGE_API_KEY / yes credential for the selected EMBEDDING_PROVIDER
🔐 secretOPENAI_API_KEYANTHROPIC_API_KEY / / GROK_API_KEY ingest only key for the selected CHAT_PROVIDER
🔐 secretOPENAI_EMBEDDING_API_KEY/ VOYAGE_API_KEY / LOCAL_EMBEDDING_URL yes credential for the selected EMBEDDING_PROVIDER
🔐 secretOPENSUBTITLES_API_KEYno only for npm run fetch-subtitle
🔐 secretVOYAGE_API_KEYOPENAI_EMBEDDING_API_KEY / / LOCAL_EMBEDDING_URL yes credential for the selected EMBEDDING_PROVIDER
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

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

All four hints declared on every tool

1/1 tools missing one or more hints — resolve_reference (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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.

Tool inputs are validated

Only 0/1 tool handlers declare input schemas (0%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 0/1 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

Secrets stay with their owner

1 secret/sensitive value flow into network calls (GROK_API_KEY → api.x.ai) (4 other flows matched canonical API hosts)

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Production dependencies are patched

0 critical, 1 high severity in production deps — @modelcontextprotocol/sdk@1.0.0 (high), ajv@8.17.1 (medium)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

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

Upgrade dev dependencies when convenient.

Dependency freshness

1/9 production deps stale: ajv-formats@2024-03-30 (2.4y)

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 7 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 Verified](https://m8ven.ai/badge/mcp/easingthemes-exyu-mcp-1yh7kr?variant=verified)](https://m8ven.ai/mcp/easingthemes-exyu-mcp-1yh7kr)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: b23ec96624e9d30d21d8f6d19b800a9a0750510d
code hash: bcd375b6ced433e667aba1545c576b06b5f0fed740f373afc796add0ae0d0d56
verified: 8/8/2026, 7:30:29 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