Plane Ce MCP Server

plane-ce-mcp PyPI v1.1.0

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

Unofficial MCP server for self-hosted Plane (Community Edition)

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 1

low Hardcoded egress to an external endpoint in packaging/dev tooling (tests/test_oauth_security.py)MTC-SRC-003

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_oauth_security.py:151`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: "data:text/html,<script>fetch('https://evil.com')</script>", "myapp://callback", ], ids=[

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 tests/test_oauth_security.py

Tools 142

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

  • get_work_item_attachment_download_urlingests untrusted input
  • list_work_item_attachmentsingests untrusted input
  • attach_page_to_work_itemno sensitive capability
  • complete_cycleno sensitive capability
  • count_work_itemsno sensitive capability
  • create_cycleno sensitive capability
  • create_initiativeno sensitive capability
  • create_intake_work_itemno sensitive capability
  • create_labelno sensitive capability
  • create_milestoneno sensitive capability
Show 132 more tools ↓
  • create_moduleno sensitive capability
  • create_pageno sensitive capability
  • create_projectno sensitive capability
  • create_project_estimateno sensitive capability
  • create_project_estimate_pointsno sensitive capability
  • create_stateno sensitive capability
  • create_work_itemno sensitive capability
  • create_work_item_commentno sensitive capability
  • create_work_item_linkno sensitive capability
  • create_work_item_propertyno sensitive capability
  • create_work_item_property_optionno sensitive capability
  • create_work_item_relationno sensitive capability
  • create_work_item_relation_definitionno sensitive capability
  • create_work_item_typeno sensitive capability
  • create_work_logno sensitive capability
  • delete_cycleno sensitive capability
  • delete_initiativeno sensitive capability
  • delete_intake_work_itemno sensitive capability
  • delete_labelno sensitive capability
  • delete_milestoneno sensitive capability
  • delete_moduleno sensitive capability
  • delete_projectno sensitive capability
  • delete_project_estimateno sensitive capability
  • delete_project_estimate_pointno sensitive capability
  • delete_stateno sensitive capability
  • delete_work_itemno sensitive capability
  • delete_work_item_attachmentno sensitive capability
  • delete_work_item_commentno sensitive capability
  • delete_work_item_linkno sensitive capability
  • delete_work_item_propertyno sensitive capability
  • delete_work_item_property_optionno sensitive capability
  • delete_work_item_property_valueno sensitive capability
  • delete_work_item_relation_definitionno sensitive capability
  • delete_work_item_typeno sensitive capability
  • delete_work_logno sensitive capability
  • detach_page_from_work_itemno sensitive capability
  • get_featuresno sensitive capability
  • get_instance_infono sensitive capability
  • get_meno sensitive capability
  • get_pql_referenceno sensitive capability
  • get_project_estimateno sensitive capability
  • get_project_membersno sensitive capability
  • get_project_worklog_summaryno sensitive capability
  • get_work_item_property_valueno sensitive capability
  • get_workspace_membersno sensitive capability
  • import_work_item_types_to_projectno sensitive capability
  • link_estimate_to_projectno sensitive capability
  • list_archived_work_itemsno sensitive capability
  • list_cycle_work_itemsno sensitive capability
  • list_cyclesno sensitive capability
  • list_initiative_projectsno sensitive capability
  • list_initiativesno sensitive capability
  • list_intake_work_itemsno sensitive capability
  • list_labelsno sensitive capability
  • list_milestone_work_itemsno sensitive capability
  • list_milestonesno sensitive capability
  • list_module_work_itemsno sensitive capability
  • list_modulesno sensitive capability
  • list_pagesno sensitive capability
  • list_project_estimate_pointsno sensitive capability
  • list_projectsno sensitive capability
  • list_rolesno sensitive capability
  • list_statesno sensitive capability
  • list_toolsetsno sensitive capability
  • list_work_item_activitiesno sensitive capability
  • list_work_item_commentsno sensitive capability
  • list_work_item_linksno sensitive capability
  • list_work_item_pagesno sensitive capability
  • list_work_item_propertiesno sensitive capability
  • list_work_item_property_optionsno sensitive capability
  • list_work_item_relation_definitionsno sensitive capability
  • list_work_item_relationsno sensitive capability
  • list_work_item_typesno sensitive capability
  • list_work_itemsno sensitive capability
  • list_work_logsno sensitive capability
  • manage_cycle_archiveno sensitive capability
  • manage_cycle_work_itemsno sensitive capability
  • manage_initiative_projectsno sensitive capability
  • manage_milestone_work_itemsno sensitive capability
  • manage_module_archiveno sensitive capability
  • manage_module_work_itemsno sensitive capability
  • manage_project_archiveno sensitive capability
  • manage_work_item_archiveno sensitive capability
  • manage_work_item_assigneeno sensitive capability
  • manage_work_item_labelno sensitive capability
  • manage_work_item_type_propertiesno sensitive capability
  • read_work_item_attachmentno sensitive capability
  • remove_work_item_relationno sensitive capability
  • resolve_work_item_typeno sensitive capability
  • retrieve_cycleno sensitive capability
  • retrieve_initiativeno sensitive capability
  • retrieve_intake_work_itemno sensitive capability
  • retrieve_labelno sensitive capability
  • retrieve_milestoneno sensitive capability
  • retrieve_moduleno sensitive capability
  • retrieve_pageno sensitive capability
  • retrieve_projectno sensitive capability
  • retrieve_roleno sensitive capability
  • retrieve_stateno sensitive capability
  • retrieve_work_itemno sensitive capability
  • retrieve_work_item_activityno sensitive capability
  • retrieve_work_item_by_identifierno sensitive capability
  • retrieve_work_item_commentno sensitive capability
  • retrieve_work_item_linkno sensitive capability
  • retrieve_work_item_propertyno sensitive capability
  • retrieve_work_item_property_optionno sensitive capability
  • retrieve_work_item_typeno sensitive capability
  • search_pagesno sensitive capability
  • search_work_itemsno sensitive capability
  • set_work_item_property_valueno sensitive capability
  • transfer_cycle_work_itemsno sensitive capability
  • update_cycleno sensitive capability
  • update_initiativeno sensitive capability
  • update_intake_work_itemno sensitive capability
  • update_labelno sensitive capability
  • update_milestoneno sensitive capability
  • update_moduleno sensitive capability
  • update_projectno sensitive capability
  • update_project_estimateno sensitive capability
  • update_project_estimate_pointno sensitive capability
  • update_project_featuresno sensitive capability
  • update_stateno sensitive capability
  • update_work_itemno sensitive capability
  • update_work_item_commentno sensitive capability
  • update_work_item_linkno sensitive capability
  • update_work_item_propertyno sensitive capability
  • update_work_item_property_optionno sensitive capability
  • update_work_item_relation_definitionno sensitive capability
  • update_work_item_typeno sensitive capability
  • update_work_logno sensitive capability
  • update_workspace_featuresno sensitive capability
  • upload_work_item_attachment_from_urlno 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 96/100 1 1.13.0 2026-08-25

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/plane-ce-mcp/badge.svg)](https://mcptrustchecker.com/registry/plane-ce-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/plane-ce-mcp"><img src="https://mcptrustchecker.com/registry/plane-ce-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/plane-ce-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 plane-ce-mcp --online --registry pypi

Use the free API → How scoring works

More in Developer Tools