Productboard (drmaxbdc) MCP Server
@drmaxbdc/productboard-mcp
npm
v2.1.1
Published by @drmaxbdc — 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 Productboard API v2 — 30 tools for entities, notes, relationships, members, and analytics. V1 retained only as a narrow fallback for two filters; V1 stops working on 2026-07-08.
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:
| Points | Adoption-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 1
high Shell/command execution in server code (build/auth/oauth-setup.js)MTC-SRC-002
In the server's implementation (`build/auth/oauth-setup.js:3`): 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 { writeTokensAtomic } from "./token-store.js"; import { createAuthError,
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 build/auth/oauth-setup.js
Tools 29
Each tool and what it can reach — statically extracted from the published source.
list_all_notesingests untrusted inputlist_notesingests untrusted inputadd_note_commentno sensitive capabilitycreate_entityno sensitive capabilitycreate_entity_relationshipno sensitive capabilitycreate_noteno sensitive capabilitycreate_note_relationshipno sensitive capabilitydelete_entityno sensitive capabilitydelete_entity_relationshipno sensitive capabilitydelete_noteno sensitive capability
Show 19 more tools ↓
delete_note_relationshipno sensitive capabilityget_entityno sensitive capabilityget_entity_configurationsno sensitive capabilityget_entity_relationshipsno sensitive capabilityget_memberno sensitive capabilityget_member_activitiesno sensitive capabilityget_noteno sensitive capabilityget_note_configurationsno sensitive capabilityget_note_relationshipsno sensitive capabilityget_note_v1no sensitive capabilitylist_entitiesno sensitive capabilitylist_membersno sensitive capabilityresolve_noteno sensitive capabilitysearch_entitiesno sensitive capabilitysearch_notesno sensitive capabilityset_entity_parentno sensitive capabilityset_note_customerno sensitive capabilityupdate_entityno sensitive capabilityupdate_noteno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (29 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v2.1.1 latest |
A 93/100 | 1 | 1.13.0 | 2026-09-07 |
v2.0.3 |
A 93/100 | 1 | 1.13.0 | 2026-09-04 |
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.
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 @drmaxbdc/productboard-mcp --onlineOther implementations of Productboard 2
Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →
Integrate the Productboard API into agentic workflows via MCP
Read-only MCP server for ProductBoard product management data
More in Productivity & Workflow
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.