Feishu-MCP (cso1z/feishu-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.

D
Caution
54/100
14 days ago

Feishu-MCP

Provides access to Feishu (Lark) documents for AI-driven coding tools like Cursor, Windsurf, and Cline based on Model Context Protocol implementation.

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

cso1z

Source: modelscope

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
⚠️
Known vulnerabilities in dependencies: 13 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 5 credentials: FEISHU_APP_SECRET, FEISHU_ENCRYPTION_KEY, FEISHU_REQUIRE_USER_KEY, FEISHU_USER_KEY, MCP_BEARER_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies13 high5 medium12 low

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

highaxios@1.7.9GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

highaxios@1.7.9GHSA-3g43-6gmg-66jw

axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge

highaxios@1.7.9GHSA-43fc-jf86-j433

Axios is Vulnerable to Denial of Service via __proto__ Key in mergeConfig

highaxios@1.7.9GHSA-4hjh-wcwx-xvwj

Axios is vulnerable to DoS attack through lack of data size check

highaxios@1.7.9GHSA-6chq-wfr3-2hj9

Axios: Header Injection via Prototype Pollution

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.
configCACHE_ENABLED
configCACHE_MAX_SIZE
configCACHE_TTL
configFEISHU_APP_IDfeishu-tool config set cli_xxxxx
🔐 secretFEISHU_APP_SECRET✅ 飞书应用密钥 -
configFEISHU_AUTH_BASE_URL❌ 飞书授权页面域名,Lark 国际版设置为 https://accounts.larksuite.com https://accounts.feishu.cn
configFEISHU_AUTH_TYPEtenant/user
configFEISHU_BASE_URL❌ 飞书 API 基础 URL,Lark 国际版可配置为 https://open.larksuite.com/open-apis https://open.feishu.cn/open-apis
configFEISHU_ENABLED_MODULESdocument,task
🔐 secretFEISHU_ENCRYPTION_KEY❌ Token缓存敏感字段加密密钥。任意字符串,系统自动通过SHA-256派生加密密钥。设置后 access_token、refresh_token、client_secret 等敏感字段将被加密存储。Docker部署时建议设置固定密钥 -
configFEISHU_PUBLIC_BASE_URL❌ 服务对外可访问的基础 URL。user 认证时若 MCP 通过内网地址访问、但 OAuth 回调需走公网域名,可设置为如 https://mcp.example.com -
🔐 secretFEISHU_REQUIRE_USER_KEY❌ user 认证模式下是否强制要求显式 user-key。默认保持兼容;多用户 HTTP/中转场景建议设为 true false
configFEISHU_SCOPE_VALIDATION~~权限检查功能可配置化:将权限检查功能作为可配置选项,支持通过环境变量 或命令行参数 --feishu-scope-validation 控制,默认启用,满足不同用户的使用场景~~ 0.2.0 ✅
configFEISHU_TOKEN_ENDPOINT
🔐 secretFEISHU_USER_KEYfeishu-tool config set "$(node -e 'console.log(crypto.randomUUID())')"
configLOG_FILE_PATH
configLOG_LEVEL
configLOG_SHOW_LEVEL
configLOG_SHOW_TIMESTAMP
configLOG_TIMESTAMP_FORMAT
configLOG_TO_FILE
🔐 secretMCP_BEARER_TOKEN❌ MCP Bearer Token 认证令牌。设置后,所有 HTTP/SSE/StreamableHTTP 端点将要求请求头 Authorization: Bearer <token>,未设置时不启用认证。建议使用 UUID 等随机字符串 -
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
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

20/20 tools missing one or more hints — batch_update_feishu_block_text (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); batch_create_feishu_blocks (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); delete_feishu_document_blocks (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +17 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.

Tool inputs are validated

Only 1/20 tool handlers declare input schemas (5%)

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

Tool test coverage

Only 0/20 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

1 child_process/subprocess call in production code — runs shell commands (src/cli/commands/auth.ts:28)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Production dependencies are patched

0 critical, 13 high severity in production deps — axios@1.7.9 (high), axios@1.7.9 (high)

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

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 6 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/cso1z-feishu-mcp-1wg153?variant=verified)](https://m8ven.ai/mcp/cso1z-feishu-mcp-1wg153)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: ae620e2f76f4ec8a4e546ed10b1b0572f8e2f77d
code hash: 345625d50ccf2616070e179ea54eb3def4ecddfb992460caf2efdb7e045dbf07
verified: 8/13/2026, 8:53:05 PM
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