Feishu Bridge (v1xingyue/feishu-bridge-mcp) is an MCP server listed on the M8ven Trust Index. It scores 56 out of 100, grade D. It declares 17 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
56/100

Feishu Bridge

MCP server for Feishu that enables document management, calendar CRUD, and event scheduling via Streamable HTTP transport, deployed on Vercel with OAuth and JWT authentication.

→ v1xingyue/feishu-bridge-mcp· listed on glama

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

v1xingyue

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

Glamanot scored here

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
🚨
Secret credentials may flow to a network call
3 flows detected: FEISHU_APP_KEY. We can’t prove the destination matches the brand the credential belongs to.
🚨
Known vulnerabilities in dependencies: 2 critical, 13 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 5 credentials: AUTH_SECRET, FEISHU_APP_KEY, FEISHU_APP_SECRET, MCP_ACCESS_KEY, MCP_JWT_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes17 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

list_documents

列出工作空间根目录中当前连接可访问的文档、表格和文件。

add_image_watermark

给 JPEG、PNG 或 WebP 图片添加文字水印，自动纠正图片方向并返回 WebP 图片。

list_calendars

列出当前连接可访问的日历。

get_team_calendar

查看团队共享日历及订阅方法；日历不存在时自动创建一个公开共享日历。

get_current_time_and_team_calendar

返回当前 Unix 秒时间戳、系统版本号、最近提交哈希、部署时间和团队共享日历信息；日历不存在时自动创建。

list_calendar_events

列出指定日历中的可见日程；未指定日历时使用团队共享日历。

create_calendar_event
update_calendar_event

编辑指定日程；必须提供完整的标题和起止时间，未指定日历时使用团队共享日历。

delete_calendar_event

删除指定日程；未指定日历时使用团队共享日历。

create_calendar

创建一个共享日历。

update_calendar

修改指定共享日历的名称、描述和权限。

delete_calendar

删除指定共享日历。

create_article

创建一篇纯文本文档文章，默认开启互联网公开只读分享。

get_article

读取指定文章的标题和纯文本正文。

update_article

修改指定文章的标题和纯文本正文。

set_article_full_access_user

为指定文章添加一名拥有完整管理权限的用户。

delete_article

删除指定文章。

// known CVEs in dependencies2 critical13 high7 medium8 low

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

criticalnext@15.5.0GHSA-9qr9-h5gf-34mp

Next.js is vulnerable to RCE in React flight protocol

criticalnext-auth@4.24.14GHSA-7rqj-j65f-68wh

Auth.js: Email normalizer validates the address before Unicode normalization, allowing a homoglyph @ bypass

highnext@15.5.0GHSA-267c-6grr-h53f

Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes

highnext@15.5.0GHSA-26hh-7cqf-hhc6

Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes - Incomplete Fix Follow-Up

highnext@15.5.0GHSA-36qx-fr4f-26g5

Next.js has a Middleware / Proxy bypass in Pages Router applications using i18n

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.
🔐 secretAUTH_SECRET使用 openssl rand -hex 32 分别生成 和 MCP_JWT_SECRET，写入 .env。两者不能相同，重启时也不要重新生成。
configAUTH_TRUST_HOST
configDEPLOYED_AT
configFEISHU_ADMIN_OPEN_IDS
configFEISHU_ALLOWED_OPEN_IDSou_reader1,ou_reader2
configFEISHU_APP_ID
🔐 secretFEISHU_APP_KEY
🔐 secretFEISHU_APP_SECRET
🔐 secretMCP_ACCESS_KEY
🔐 secretMCP_JWT_SECRET使用 openssl rand -hex 32 分别生成 AUTH_SECRET 和 ，写入 .env。两者不能相同，重启时也不要重新生成。
configWATERMARK_DEBUG
configWATERMARK_ENABLED
// 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

17/17 tools missing one or more hints — list_documents (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); add_image_watermark (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_calendars (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +14 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 test coverage

13/17 tools referenced in tests (76%)

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

Production dependencies are patched

2 critical, 13 high severity in production deps — next@15.5.0 (critical), next-auth@4.24.14 (critical)

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 4 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/v1xingyue/feishu-bridge-mcp?variant=verified)](https://m8ven.ai/mcp/v1xingyue/feishu-bridge-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 3f233845584d64e467d1f40f7a7a2536b039e47d
code hash: 5a40ab89b8c1772ad776d6b1086a0f01ea389f999051a6778ecf12e8d38a70dd
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