Line (zients) MCP Server
@zients/line-mcp-server
npm
v1.0.1
Published by @zients — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
MCP server for LINE Messaging API — send messages, manage groups, rich menus, and query analytics
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 − 5 = 95. 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:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — 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 2
medium Tool "unlink_rich_menu_from_user" can modify the filesystemMTC-CAP-002
Tool "unlink_rich_menu_from_user" can write, overwrite or delete files (keyword "unlink" 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 unlink_rich_menu_from_user
low Mutating tool "unlink_rich_menu_from_user" declares no destructiveHintMTC-CAP-005
Tool "unlink_rich_menu_from_user" 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 unlink_rich_menu_from_user
Tools 44
Each tool and what it can reach — statically extracted from the published source.
unlink_rich_menu_from_userwrites filesbroadcast_flex_messageno sensitive capabilitybroadcast_text_messageno sensitive capabilitycancel_default_rich_menuno sensitive capabilitycreate_rich_menuno sensitive capabilitydelete_rich_menuno sensitive capabilityget_bot_infono sensitive capabilityget_default_rich_menuno sensitive capabilityget_follower_idsno sensitive capabilityget_friend_demographicsno sensitive capability
Show 34 more tools ↓
get_group_member_countno sensitive capabilityget_group_member_idsno sensitive capabilityget_group_member_profileno sensitive capabilityget_group_summaryno sensitive capabilityget_message_deliveriesno sensitive capabilityget_message_eventno sensitive capabilityget_message_quotano sensitive capabilityget_message_quota_consumptionno sensitive capabilityget_number_of_followersno sensitive capabilityget_rich_menuno sensitive capabilityget_room_member_countno sensitive capabilityget_room_member_idsno sensitive capabilityget_room_member_profileno sensitive capabilityget_sent_broadcast_countno sensitive capabilityget_sent_multicast_countno sensitive capabilityget_sent_push_countno sensitive capabilityget_sent_reply_countno sensitive capabilityget_statistics_per_unitno sensitive capabilityget_user_profileno sensitive capabilityleave_groupno sensitive capabilityleave_roomno sensitive capabilitylink_rich_menu_to_userno sensitive capabilitylist_rich_menusno sensitive capabilitymulticast_flex_messageno sensitive capabilitymulticast_text_messageno sensitive capabilitypush_audio_messageno sensitive capabilitypush_flex_messageno sensitive capabilitypush_image_messageno sensitive capabilitypush_location_messageno sensitive capabilitypush_sticker_messageno sensitive capabilitypush_text_messageno sensitive capabilitypush_video_messageno sensitive capabilityset_default_rich_menuno sensitive capabilityshow_loading_indicatorno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (44 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.1 latest |
A 95/100 | 2 | 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.
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 @zients/line-mcp-server --onlineOther implementations of Line 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in API Development
Adapters for the FrontMCP framework
Transcend MCP Server — Admin tools.
Transcend MCP Server — Assessments tools.
MCP Server for Bling
MCP Server for Blogger API
Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.