github not yet analyzed

Trello

github

Unofficial, third-party integration for Trello’s web-based kanban-style, list-making application.

maintainer
trello
license
first seen
2026-06-12
last seen
2026-06-17
releases · 30d
0
short id
risk 60/100 · heuristic grade
D high

Source not yet analyzed — this grade rests on attested signals (CVEs, supply-chain) only. It is a floor: reading the code could raise it, not lower it.

  • capability exposureinferred+35
  • tool safetyinferred+25

inferred

The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.

graded 13m ago · see ecosystem CVEs →

capability exposure grade factor +35
Inferred surface — each links to servers holding it:
vulnerabilities 0 CVEs

No known CVEs for this server.

tool safety 7 findings · grade factor +25
  1. highexfiltration comboTRELLO_ADD_CARDS

    single tool reads + sends: fs, net

  2. highexfiltration comboTRELLO_ADD_CARDS_ATTACHMENTS_BY_ID_CARD

    single tool reads + sends: fs, net

  3. highexfiltration comboTRELLO_ADD_TOKENS_WEBHOOKS_BY_TOKEN

    single tool reads + sends: net, secrets

  4. highexfiltration comboTRELLO_DELETE_TOKENS_BY_TOKEN

    single tool reads + sends: fs, net, secrets

  5. highexfiltration comboTRELLO_DELETE_TOKENS_WEBHOOKS_BY_TOKEN_BY_ID_WEBHOOK

    single tool reads + sends: net, secrets

  6. highexfiltration comboTRELLO_GET_MEMBERS_TOKENS_BY_ID_MEMBER

    single tool reads + sends: net, secrets

  7. hightoxic flow (lethal trifecta)

    lethal trifecta reachable across this server's tools: private-data access + untrusted-content ingestion + network exfil

embed badge readme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/smithery:trello/badge.svg)](https://mcpobservatory.com/servers/smithery:trello/security)

Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of trello.