Fizzy Do MCP Server

fizzy-do-mcp npm v0.5.1

Published by ryanyogan — 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 integrating AI agents with Fizzy, Basecamp's task management tool

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/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
High
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 = 93/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 − 7 = 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:

PointsAdoption-risk factor
−6 capability blast radius (high) — 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 2

high Shell/command execution in server code (dist/cli.js)MTC-SRC-002

In the server's implementation (`dist/cli.js: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: ort { exec } from "node:child_process"; import { fileURLToPath } from "node:url"; import * as path from "node:path"; imp

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 dist/cli.js

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([fizzy_list_cards]) co-exist with external-action tools ([fizzy_create_comment, fizzy_get_webhook, fizzy_create_webhook, fizzy_update_webhook, fizzy_delete_webhook, fizzy_test_webhook]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [fizzy_list_cards] → sinks [fizzy_create_comment, fizzy_get_webhook, fizzy_create_webhook, fizzy_update_webhook, fizzy_delete_webhook, fizzy_test_webh

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow fizzy_list_cards → fizzy_create_comment

Tools 73

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

  • fizzy_create_commentnetwork egress
  • fizzy_create_webhooknetwork egress
  • fizzy_delete_webhooknetwork egress
  • fizzy_get_webhooknetwork egress
  • fizzy_list_cardsingests untrusted input
  • fizzy_test_webhooknetwork egress
  • fizzy_update_webhooknetwork egress
  • fizzy_add_card_reactionno sensitive capability
  • fizzy_add_comment_reactionno sensitive capability
  • fizzy_assign_cardno sensitive capability
Show 63 more tools ↓
  • 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_delete_boardno sensitive capability
  • fizzy_delete_cardno sensitive capability
  • fizzy_delete_columnno sensitive capability
  • fizzy_delete_commentno sensitive capability
  • fizzy_delete_stepno sensitive capability
  • fizzy_get_accountno sensitive capability
  • fizzy_get_boardno sensitive capability
  • fizzy_get_cardno sensitive capability
  • fizzy_get_columnno sensitive capability
  • fizzy_get_commentno sensitive capability
  • fizzy_get_identityno sensitive capability
  • fizzy_get_notificationno sensitive capability
  • fizzy_get_userno sensitive capability
  • fizzy_list_boardsno sensitive capability
  • fizzy_list_card_reactionsno sensitive capability
  • fizzy_list_columnsno sensitive capability
  • fizzy_list_comment_reactionsno sensitive capability
  • fizzy_list_commentsno sensitive capability
  • fizzy_list_notificationsno sensitive capability
  • fizzy_list_stepsno sensitive capability
  • fizzy_list_tagsno sensitive capability
  • fizzy_list_usersno sensitive capability
  • fizzy_list_webhooksno sensitive capability
  • fizzy_mark_all_notifications_readno sensitive capability
  • fizzy_mark_goldenno sensitive capability
  • fizzy_mark_notification_readno sensitive capability
  • fizzy_notification_countno sensitive capability
  • fizzy_pending_work_abandonno sensitive capability
  • fizzy_pending_work_claimno sensitive capability
  • fizzy_pending_work_completeno sensitive capability
  • fizzy_pending_work_getno sensitive capability
  • fizzy_pending_work_listno sensitive capability
  • fizzy_pending_work_statusno sensitive capability
  • fizzy_pin_cardno sensitive capability
  • fizzy_pm_actionable_cardsno sensitive capability
  • fizzy_pm_end_sessionno sensitive capability
  • fizzy_pm_project_contextno sensitive capability
  • fizzy_pm_report_progressno sensitive capability
  • fizzy_pm_start_sessionno sensitive capability
  • fizzy_postpone_cardno sensitive capability
  • fizzy_publish_boardno sensitive capability
  • fizzy_remove_card_reactionno sensitive capability
  • fizzy_remove_comment_reactionno sensitive capability
  • fizzy_reopen_cardno sensitive capability
  • fizzy_tag_cardno sensitive capability
  • fizzy_toggle_stepno sensitive capability
  • fizzy_triage_cardno sensitive capability
  • fizzy_unmark_goldenno sensitive capability
  • fizzy_unpin_cardno sensitive capability
  • fizzy_unpublish_boardno sensitive capability
  • fizzy_untriage_cardno 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_watch_cardno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

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
v0.5.1 latest A 93/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.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/fizzy-do-mcp/badge.svg)](https://mcptrustchecker.com/registry/fizzy-do-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/fizzy-do-mcp"><img src="https://mcptrustchecker.com/registry/fizzy-do-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/fizzy-do-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-do-mcp --online

Use the free API → How scoring works

More in Productivity & Workflow