Panel Todo MCP Server

panel-todo-mcp npm v1.1.0

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP server for Panel Todo - 38 MCP tools for AI assistants to manage todos, issues, sprints, and coordinate parallel sessions

Trust grade
A
98/100
Last scanned get badge →
Trust
A · 98/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
Minimal
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 = 98/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 − 2 = 98. 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
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 38

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

  • panelTodo_addno sensitive capability
  • panelTodo_addCommentno sensitive capability
  • panelTodo_addIssueno sensitive capability
  • panelTodo_addTagToIssueno sensitive capability
  • panelTodo_batchCreateIssuesno sensitive capability
  • panelTodo_completeno sensitive capability
  • panelTodo_completeIssueno sensitive capability
  • panelTodo_completeSprintno sensitive capability
  • panelTodo_configureno sensitive capability
  • panelTodo_createProjectno sensitive capability
Show 28 more tools ↓
  • panelTodo_createSprintno sensitive capability
  • panelTodo_createTagno sensitive capability
  • panelTodo_deleteCommentno sensitive capability
  • panelTodo_deleteIssueno sensitive capability
  • panelTodo_deleteProjectno sensitive capability
  • panelTodo_deleteSprintno sensitive capability
  • panelTodo_deleteTagno sensitive capability
  • panelTodo_getBacklogno sensitive capability
  • panelTodo_getIssueno sensitive capability
  • panelTodo_getSprintno sensitive capability
  • panelTodo_listno sensitive capability
  • panelTodo_listCommentsno sensitive capability
  • panelTodo_listIssuesno sensitive capability
  • panelTodo_listProjectsno sensitive capability
  • panelTodo_listSprintsno sensitive capability
  • panelTodo_listTagsno sensitive capability
  • panelTodo_moveIssueToSprintno sensitive capability
  • panelTodo_removeno sensitive capability
  • panelTodo_removeTagFromIssueno sensitive capability
  • panelTodo_searchIssuesno sensitive capability
  • panelTodo_startSprintno sensitive capability
  • panelTodo_statusno sensitive capability
  • panelTodo_switchProjectno sensitive capability
  • panelTodo_updateno sensitive capability
  • panelTodo_updateCommentno sensitive capability
  • panelTodo_updateIssueno sensitive capability
  • panelTodo_updateSprintno sensitive capability
  • panelTodo_updateTagno 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.1.0 latest A 98/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 · 98/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/panel-todo-mcp/badge.svg)](https://mcptrustchecker.com/registry/panel-todo-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/panel-todo-mcp"><img src="https://mcptrustchecker.com/registry/panel-todo-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/panel-todo-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 panel-todo-mcp --online

Use the free API → How scoring works

More in Productivity & Workflow