Fizzy (Fabric-Pro) MCP Server

fizzy-mcp npm v1.0.0

Published by fabric-pro — 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.

MCP Server for Fizzy - A project management tool by Basecamp

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/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 100 − adoption risk = 96/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 − 4 = 96. 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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 47

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

  • fizzy_create_commentnetwork egress
  • fizzy_add_reactionno sensitive capability
  • fizzy_close_cardno sensitive capability
  • fizzy_create_boardno sensitive capability
  • fizzy_create_cardno sensitive capability
  • fizzy_create_columnno sensitive capability
  • fizzy_create_stepno sensitive capability
  • fizzy_deactivate_userno sensitive capability
  • fizzy_delete_boardno sensitive capability
  • fizzy_delete_cardno sensitive capability
Show 37 more tools ↓
  • fizzy_delete_columnno sensitive capability
  • fizzy_delete_commentno sensitive capability
  • fizzy_delete_stepno sensitive capability
  • fizzy_get_accountsno sensitive capability
  • fizzy_get_boardno sensitive capability
  • fizzy_get_boardsno sensitive capability
  • fizzy_get_cardno sensitive capability
  • fizzy_get_card_commentsno sensitive capability
  • fizzy_get_cardsno sensitive capability
  • fizzy_get_columnno sensitive capability
  • fizzy_get_columnsno sensitive capability
  • fizzy_get_commentno sensitive capability
  • fizzy_get_identityno sensitive capability
  • fizzy_get_notificationsno sensitive capability
  • fizzy_get_reactionsno sensitive capability
  • fizzy_get_stepno sensitive capability
  • fizzy_get_tagsno sensitive capability
  • fizzy_get_userno sensitive capability
  • fizzy_get_usersno sensitive capability
  • fizzy_mark_all_notifications_readno sensitive capability
  • fizzy_mark_notification_readno sensitive capability
  • fizzy_mark_notification_unreadno sensitive capability
  • fizzy_move_card_to_columnno sensitive capability
  • fizzy_move_card_to_not_nowno sensitive capability
  • fizzy_remove_reactionno sensitive capability
  • fizzy_reopen_cardno sensitive capability
  • fizzy_send_card_to_triageno sensitive capability
  • fizzy_toggle_card_assignmentno sensitive capability
  • fizzy_toggle_card_tagno sensitive capability
  • fizzy_unwatch_cardno sensitive capability
  • fizzy_update_boardno sensitive capability
  • fizzy_update_cardno sensitive capability
  • fizzy_update_columnno sensitive capability
  • fizzy_update_commentno sensitive capability
  • fizzy_update_stepno sensitive capability
  • fizzy_update_userno sensitive capability
  • fizzy_watch_cardno 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.0.0 latest A 96/100 0 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 · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/fizzy-mcp/badge.svg)](https://mcptrustchecker.com/registry/fizzy-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/fizzy-mcp"><img src="https://mcptrustchecker.com/registry/fizzy-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/fizzy-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 fizzy-mcp --online

Use the free API → How scoring works

Other implementations of Fizzy 2

Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →

More in Productivity & Workflow