lilyco (lilyco-42/lilyco) is an MCP server listed on the M8ven Trust Index. It scores 58 out of 100, grade D. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Warning
58/100

lilyco

让人类远离计算机，AI 可做任何事 —— 一个 struct 派生 CLI/TUI/Web/MCP 四端，天生 AI-callable：MCP 服务器 + 进度通知 + 采样桥（工具可反向调用 Agent 的 LLM）。一套代码，Windows/Linux/Android 全平台。

→ lilyco-42/lilyco· listed on github_topic

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we 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

lilyco-42

Source: github_topic · also listed on github_repo_search

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

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Code appears obfuscated
1 file are unreadable to a human reviewer. Cannot audit what they do.
// quality suggestions

No eval / new Function

4 eval() or new Function() calls — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

Readable source code

1 file are minified or bundled, which is usually build output rather than concealment

Ship unminified, readable source.

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 2 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/lilyco-42/lilyco?variant=verified)](https://m8ven.ai/mcp/lilyco-42/lilyco)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 379536f26cc07673a277ab39cf34c10982f9e22d
code hash: b1efb577c8fa8d3a7af475a4bc0401be91689fdfe586c2601d7b2e95fcf208fd
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