WEEEK (smart)
NPM · WEEEK-MCP-SMART · SCANNED SEP 20
WEEEK tasks by name, not IDs — an MCP server
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to IlyaIvanchikov/weeek-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 49 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 761 tokens (~63/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage68
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 3% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the WEEEK (smart) MCP server?
WEEEK (smart) runs locally as an npm package, launched with npx -y weeek-mcp-smart. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · weeek-mcp-smart
claude mcp add ilyaivanchikov-weeek-mcp-smart -- npx -y weeek-mcp-smart
{
"mcpServers": {
"ilyaivanchikov-weeek-mcp-smart": {
"command": "npx",
"args": [
"-y",
"weeek-mcp-smart"
]
}
}
} {
"servers": {
"ilyaivanchikov-weeek-mcp-smart": {
"command": "npx",
"args": [
"-y",
"weeek-mcp-smart"
]
}
}
} codex mcp add ilyaivanchikov-weeek-mcp-smart -- npx -y weeek-mcp-smart
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ilyaivanchikov-weeek-mcp-smart": {
"type": "local",
"command": [
"npx",
"-y",
"weeek-mcp-smart"
],
"enabled": true
}
}
} openclaw mcp add ilyaivanchikov-weeek-mcp-smart --command npx --arg -y --arg weeek-mcp-smart
mcp_servers:
ilyaivanchikov-weeek-mcp-smart:
command: "npx"
args: ["-y", "weeek-mcp-smart"] {
"McpServers": {
"ilyaivanchikov-weeek-mcp-smart": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"weeek-mcp-smart"
]
}
}
} assistant mcp add ilyaivanchikov-weeek-mcp-smart -t stdio -c npx -a -y weeek-mcp-smart
{
"mcpServers": {
"ilyaivanchikov-weeek-mcp-smart": {
"command": "npx",
"args": [
"-y",
"weeek-mcp-smart"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 15 Sept 26 −3
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
- 14 Sept 26 +1
- Stability: 0.97 → pass security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/weeek-mcp-smart@0.4.4
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | IlyaIvanchikov/weeek-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/IlyaIvanchikov/weeek-mcp/.github/workflows/release.yml@refs/tags/v0.4.4 |
| Rekor log index | 2311993722 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:5f46b2cd0572f64ec94a29229f70bd4bb437de4858c8aee7acb6b53b1259dec6af0848ac14dc7229641c1045728cbb76f978bb4d9233a3ad131f08177 |
Background: How many MCP packages publish verified provenance →
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
weeek_attach_file ~78
Attach a local file to a WEEEK task. For safety only files inside the allowed directory (the server's working directory by default, or WEEEK_ATTACH_DIR if set) — and its subfolders — may be attached; paths outside it are refused.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
| task_id | integer | yes | – |
No output schema declared.
No examples provided.
weeek_complete_task ~39
Mark a WEEEK task complete, or reopen it (completed:false).
| Name | Type | Req | Description |
|---|---|---|---|
| completed | boolean | yes | – |
| id | integer | yes | – |
No output schema declared.
No examples provided.
weeek_create_task ~144
Create a WEEEK task. Accepts project/column/assignee by NAME or id, and a natural-language `due` date. One call — no need to look up ids first. Omit `assignee` to self-assign (WEEEK assigns the token owner); pass a member name/id to assign someone else. Reassigning an existing task is not supported by the WEEEK public API — set the assignee at creation.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | – | – | – |
| column | – | – | – |
| description | string | – | – |
| due | string | – | – |
| project | string|number | yes | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
weeek_create_tasks ~42
Create many WEEEK tasks in one call. Returns a per-item report; one bad name does not abort the batch.
| Name | Type | Req | Description |
|---|---|---|---|
| tasks | array | yes | – |
No output schema declared.
No examples provided.
weeek_delete_task ~72
Permanently delete a WEEEK task by id. Irreversible — the task is removed, not just completed. Requires confirm:true; to merely close a task use weeek_complete_task instead.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Must be true to confirm this irreversible deletion. |
| id | integer | yes | – |
No output schema declared.
No examples provided.
weeek_get_task ~32
Get one WEEEK task by id (includes its assignees).
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
weeek_list_members ~48
List WEEEK workspace members (id + display name). Use to find the id for assigning a task to someone; pass that id as `assignee` to weeek_create_task.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
weeek_list_projects ~20
List WEEEK projects (id + name).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
weeek_list_tasks ~118
List WEEEK tasks with server-side filters. Set allPages=true together with userId, startDate, and endDate to fetch every matching page inside the connector without returning unrelated workspace pages.
| Name | Type | Req | Description |
|---|---|---|---|
| allPages | boolean | – | – |
| completed | boolean | – | – |
| endDate | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| projectId | integer | – | – |
| sortBy | string | – | – |
| startDate | string | – | – |
| userId | string | – | – |
No output schema declared.
No examples provided.
weeek_move_task ~59
Move a WEEEK task to a column (by name or id, scoped to the given board) on that board.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | integer | yes | – |
| column | string|number | yes | – |
| id | integer | yes | – |
No output schema declared.
No examples provided.
weeek_update_task ~82
Update an existing WEEEK task's title or due date. NOTE: description is NOT updatable — WEEEK's API silently ignores it on update; set the description at create time (weeek_create_task) or edit it in the UI.
| Name | Type | Req | Description |
|---|---|---|---|
| due | string | – | – |
| id | integer | yes | – |
| title | string | – | – |
No output schema declared.
No examples provided.
weeek_version ~27
Return this MCP server's name and version, so callers can check which build is running.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the WEEEK (smart) MCP server?
WEEEK (smart) is an MCP server listed in the public MCP registry as io.github.IlyaIvanchikov/weeek-mcp-smart. WEEEK tasks by name, not IDs, an MCP server. This page covers its npm package (weeek-mcp-smart).
Is the WEEEK (smart) MCP server safe to use?
WEEEK (smart) scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the WEEEK (smart) MCP server expose?
WEEEK (smart) exposes 12 tools: weeek_version, weeek_list_projects, weeek_list_tasks, weeek_get_task, weeek_list_members, and 7 more. Their descriptions and schemas cost roughly 761 tokens of context every time the server is loaded.
Is the WEEEK (smart) MCP server still maintained?
WEEEK (smart) is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the WEEEK (smart) MCP server under?
WEEEK (smart) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.