Weeek (adalekin) MCP Server

weeek-mcp PyPI v0.2.0

Published by adalekin — 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 Weeek: task management via the public API, knowledge base via its internal API and collaborative editor channel.

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 45

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

  • weeek_get_attachmentingests untrusted input
  • weeek_add_task_commentno sensitive capability
  • weeek_add_task_to_projectno sensitive capability
  • weeek_complete_taskno sensitive capability
  • weeek_create_taskno sensitive capability
  • weeek_delete_taskno sensitive capability
  • weeek_delete_task_commentno sensitive capability
  • weeek_get_taskno sensitive capability
  • weeek_kb_createno sensitive capability
  • weeek_kb_deleteno sensitive capability
Show 35 more tools ↓
  • weeek_kb_exportno sensitive capability
  • weeek_kb_iconsno sensitive capability
  • weeek_kb_listno sensitive capability
  • weeek_kb_moveno sensitive capability
  • weeek_kb_readno sensitive capability
  • weeek_kb_searchno sensitive capability
  • weeek_kb_table_widthsno sensitive capability
  • weeek_kb_updateno sensitive capability
  • weeek_list_board_columnsno sensitive capability
  • weeek_list_boardsno sensitive capability
  • weeek_list_custom_fieldsno sensitive capability
  • weeek_list_membersno sensitive capability
  • weeek_list_projectsno sensitive capability
  • weeek_list_task_commentsno sensitive capability
  • weeek_list_tasksno sensitive capability
  • weeek_manage_board_columnsno sensitive capability
  • weeek_manage_boardsno sensitive capability
  • weeek_manage_custom_fieldsno sensitive capability
  • weeek_manage_portfoliosno sensitive capability
  • weeek_manage_projectsno sensitive capability
  • weeek_manage_tagsno sensitive capability
  • weeek_manage_time_entryno sensitive capability
  • weeek_move_taskno sensitive capability
  • weeek_remove_assigneesno sensitive capability
  • weeek_remove_task_from_projectno sensitive capability
  • weeek_remove_watchersno sensitive capability
  • weeek_set_assigneesno sensitive capability
  • weeek_set_task_parentno sensitive capability
  • weeek_set_watchersno sensitive capability
  • weeek_task_timerno sensitive capability
  • weeek_uncomplete_taskno sensitive capability
  • weeek_update_taskno sensitive capability
  • weeek_update_task_commentno sensitive capability
  • weeek_upload_attachmentno sensitive capability
  • weeek_whoamino 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
v0.2.0 latest A 96/100 0 1.13.0 2026-09-05

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

Use the free API → How scoring works

Other implementations of Weeek 1

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

More in Productivity & Workflow