Brello MCP Server

brello npm v1.8.0

Published by brickshubkuwait — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Roster CLI + MCP — query your team's work from the terminal or Claude

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/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
Moderate
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 99 − adoption risk = 95/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 − 1.2 = 99. What the published surface and source actually contain:

PointsWhat was foundCategory
−1.2 Package runs install-time scripts MTC-SUP-010 supply-chain

2. Client adoption risk — 99 − 4 = 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:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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 1

low Package runs install-time scripts (postinstall)MTC-SUP-010

"brello" 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 lib/postinstall.mjs

Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.

Location: package brello

Tools 38

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

  • roster_ps_issuesnetwork egress
  • roster_activeno sensitive capability
  • roster_activityno sensitive capability
  • roster_archiveno sensitive capability
  • roster_assignno sensitive capability
  • roster_auditno sensitive capability
  • roster_blockedno sensitive capability
  • roster_cardno sensitive capability
  • roster_cardsno sensitive capability
  • roster_changelogno sensitive capability
Show 28 more tools ↓
  • roster_clientno sensitive capability
  • roster_commentno sensitive capability
  • roster_commentsno sensitive capability
  • roster_createno sensitive capability
  • roster_departmentsno sensitive capability
  • roster_describeno sensitive capability
  • roster_doneno sensitive capability
  • roster_dueno sensitive capability
  • roster_leavesno sensitive capability
  • roster_mark_doneno sensitive capability
  • roster_moveno sensitive capability
  • roster_nowno sensitive capability
  • roster_overdueno sensitive capability
  • roster_reactionsno sensitive capability
  • roster_recentno sensitive capability
  • roster_renameno sensitive capability
  • roster_searchno sensitive capability
  • roster_set_dueno sensitive capability
  • roster_set_priorityno sensitive capability
  • roster_shootsno sensitive capability
  • roster_stage_cardsno sensitive capability
  • roster_stage_statsno sensitive capability
  • roster_stagesno sensitive capability
  • roster_statsno sensitive capability
  • roster_studiono sensitive capability
  • roster_teamno sensitive capability
  • roster_user_cardsno sensitive capability
  • roster_workloadno sensitive capability

What this scan could not see

Versions 2

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.8.0 latest A 95/100 1 1.13.0 2026-09-07
v1.6.0 A 95/100 1 1.12.1 2026-08-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 · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/brello/badge.svg)](https://mcptrustchecker.com/registry/brello)
HTML
<a href="https://mcptrustchecker.com/registry/brello"><img src="https://mcptrustchecker.com/registry/brello/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/brello/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 brello --online

Use the free API → How scoring works

More in Productivity & Workflow