trelly
npm
v0.3.9
Source verified
Published by brandonkramer — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
trelly — fast Trello CLI with multi-profile auth, MCP server, and kanban TUI
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 − 1.2 = 99. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −1.2 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
2. Client adoption risk — 99 − 6 = 93. 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 |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
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.
In the server's implementation (`bin/launch-cursor-mcp.mjs:6`): 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: rt { spawn } from "node:child_process"; import { existsSync, readdirSync, statSync } from "node:fs"; import { homedir }
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 bin/launch-cursor-mcp.mjs
In the server's implementation (`src/sync-plugin-versions.ts:1`): 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: spawnSync } from "node:child_process"; import { readFileSync, writeFileSync } from "node:fs"; import { dirname, join, r
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 src/sync-plugin-versions.ts
In the server's implementation (`src/update.ts:1`): 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: rt { spawn } from "node:child_process"; import { cpSync, existsSync, mkdirSync, readFileSync, realpathSync,
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 src/update.ts
In the server's implementation (`src/util/runtime.ts:1`): 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: rt { spawn } from "node:child_process"; import { createInterface } from "node:readline"; export async function readLine
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 src/util/runtime.ts
In a packaging/dev/install script (shipped, but not the server runtime) (`src/install.test.ts:2`): 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: spawnSync } from "node:child_process"; import { chmodSync, existsSync, mkdirSync, mkdtempSync, readFileSync,
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 src/install.test.ts
"trelly" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.
Evidence: node -e "try{const{chmodSync}=require('fs');for(const f of['bin/trelly','bin/trelly-mcp','bin/run-ts','bin/launch-cursor-mcp.mjs','bin/install-cursor-plugin-loc
Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.
Location: package trelly
Each tool and what it can reach — statically extracted from the published source.
trello_webhook_createnetwork egresstrello_webhook_deletenetwork egresstrello_api_getno sensitive capabilitytrello_api_mutateno sensitive capabilitytrello_board_archiveno sensitive capabilitytrello_board_contextno sensitive capabilitytrello_board_createno sensitive capabilitytrello_boards_listno sensitive capabilitytrello_card_add_labelno sensitive capabilitytrello_card_archiveno sensitive capabilitytrello_card_attachment_addno sensitive capabilitytrello_card_attachment_deleteno sensitive capabilitytrello_card_comment_createno sensitive capabilitytrello_card_comment_deleteno sensitive capabilitytrello_card_comment_updateno sensitive capabilitytrello_card_contextno sensitive capabilitytrello_card_createno sensitive capabilitytrello_card_deleteno sensitive capabilitytrello_card_moveno sensitive capabilitytrello_card_updateno sensitive capabilitytrello_checklist_add_itemno sensitive capabilitytrello_checklist_createno sensitive capabilitytrello_label_createno sensitive capabilitytrello_list_cardsno sensitive capabilitytrello_list_createno sensitive capabilitytrello_member_meno sensitive capabilitytrello_profiles_listno sensitive capabilitytrello_resolveno sensitive capabilitytrello_searchno sensitive capabilitytrello_webhooks_listno sensitive capabilityScan 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 |
|---|---|---|---|---|
v0.3.9 latest |
A 93/100 | 6 | 1.13.0 | 2026-09-07 |
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.
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 trelly --online
MCP AgentChat - 让 AI Agent 通过 Telegram 与用户实时交互:发送消息、图片,等待用户回复
A Model Context Protocol (MCP) server for Airthings Air Quality Monitor devices.
MCP server for Anki
TypeScript package for reading and searching Apple Notes on macOS via direct SQLite access. Includes markdown conversion, attachment support, and offers a local MCP server!
Verified biotech catalyst calendar (PDUFA/AdComm/trial readouts) anchored to official sources.
Appointment booking platform letting agents check provider availability and create bookings.