Feishu Wiki MCP Server

@akaknele/feishu-wiki-mcp npm v1.3.1

Published by @akaknele — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Feishu Wiki MCP Server - 飞书知识库管理工具

Trust grade
A
92/100
Last scanned get badge →
Trust
A · 92/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 92/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 8 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 3

high Shell/command execution in server code (build/index.js)MTC-SRC-002

In the server's implementation (`build/index.js:8`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ort { exec } from "node:child_process"; function parseArgs() { const args = process.argv.slice(2); // Env var fa

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server build/index.js

medium Tool "drive_delete_file" can modify the filesystemMTC-CAP-002

Tool "drive_delete_file" can write, overwrite or delete files (keyword "delete_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool drive_delete_file

low Mutating tool "drive_delete_file" declares no destructiveHintMTC-CAP-005

Tool "drive_delete_file" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool drive_delete_file

Tools 36

Each tool and what it can reach — statically extracted from the published source.

  • drive_delete_filewrites files
  • drive_upload_filenetwork egress
  • im_send_messagenetwork egress
  • bitable_create_appno sensitive capability
  • bitable_create_recordno sensitive capability
  • bitable_create_tableno sensitive capability
  • bitable_list_fieldsno sensitive capability
  • bitable_list_tablesno sensitive capability
  • bitable_search_recordsno sensitive capability
  • bitable_update_recordno sensitive capability
Show 26 more tools ↓
  • contact_batch_get_user_idno sensitive capability
  • doc_create_blocksno sensitive capability
  • doc_delete_blocksno sensitive capability
  • doc_get_blockno sensitive capability
  • doc_get_raw_contentno sensitive capability
  • doc_importno sensitive capability
  • doc_list_blocksno sensitive capability
  • doc_searchno sensitive capability
  • doc_update_blockno sensitive capability
  • drive_add_permissionno sensitive capability
  • im_create_chatno sensitive capability
  • im_get_chat_membersno sensitive capability
  • im_list_chatsno sensitive capability
  • im_list_messagesno sensitive capability
  • wiki_copy_nodeno sensitive capability
  • wiki_create_nodeno sensitive capability
  • wiki_create_node_with_markdownno sensitive capability
  • wiki_delete_nodeno sensitive capability
  • wiki_get_nodeno sensitive capability
  • wiki_get_spaceno sensitive capability
  • wiki_list_nodesno sensitive capability
  • wiki_list_spacesno sensitive capability
  • wiki_move_docs_to_wikino sensitive capability
  • wiki_move_nodeno sensitive capability
  • wiki_searchno sensitive capability
  • wiki_update_titleno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.3.1 latest A 92/100 3 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 92/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/akaknele-feishu-wiki-mcp/badge.svg)](https://mcptrustchecker.com/registry/akaknele-feishu-wiki-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/akaknele-feishu-wiki-mcp"><img src="https://mcptrustchecker.com/registry/akaknele-feishu-wiki-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/akaknele-feishu-wiki-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @akaknele/feishu-wiki-mcp --online

Use the free API → How scoring works

More in AI, Memory & Reasoning