Pickle
NPM · PICKLE-MCP · SCANNED SEP 20
Free, local MCP server that audits ClickUp, Slack & Teams for work that slipped through.
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
- 39 of 123 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 36 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 3830 tokens (~67/item across 57 items; 57 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "clickup_send_chat_message" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 57 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 Pickle MCP server?
Pickle runs locally as an npm package, launched with npx -y pickle-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · pickle-mcp
claude mcp add adityaarsharma-pickle -- npx -y pickle-mcp
{
"mcpServers": {
"adityaarsharma-pickle": {
"command": "npx",
"args": [
"-y",
"pickle-mcp"
]
}
}
} {
"servers": {
"adityaarsharma-pickle": {
"command": "npx",
"args": [
"-y",
"pickle-mcp"
]
}
}
} codex mcp add adityaarsharma-pickle -- npx -y pickle-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"adityaarsharma-pickle": {
"type": "local",
"command": [
"npx",
"-y",
"pickle-mcp"
],
"enabled": true
}
}
} openclaw mcp add adityaarsharma-pickle --command npx --arg -y --arg pickle-mcp
mcp_servers:
adityaarsharma-pickle:
command: "npx"
args: ["-y", "pickle-mcp"] {
"McpServers": {
"adityaarsharma-pickle": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"pickle-mcp"
]
}
}
} assistant mcp add adityaarsharma-pickle -t stdio -c npx -a -y pickle-mcp
{
"mcpServers": {
"adityaarsharma-pickle": {
"command": "npx",
"args": [
"-y",
"pickle-mcp"
]
}
}
} 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 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −1
- Security disclosure: unverified → pass ▲ functional
- Stability: pass → 0.83 functional
- 16 Sept 26 +1
- CVE-2026-82562 no longer affects this package ▲ security
- CVE-2026-82417 no longer affects this package ▲ security
- Known CVEs: fail → pass ▲ security
- Stability: 0.97 → pass security
- Security disclosure: pass → unverified ▼ functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 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.
- 10 Sept 26 −2
- Stability: pass → 0.80 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
- 8 Sept 26 +1
- Security disclosure: unverified → pass ▲ 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/pickle-mcp@1.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 123 packages
| Packages resolved | 123 |
|---|---|
| Stale | 39 |
| 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 →
slack_list_users ~68
List active members of the Slack workspace. Returns id, name, real_name, email, is_bot, is_deleted. Useful for resolving user IDs in messages to readable names during audits.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| include_locale | boolean | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
slack_search_messages ~112
Full-text search Slack messages (user token only, search:read scope required). Returns ranked matches with channel, user, ts, text. Useful for audits like 'find every message containing shipping today' or '@mention X without follow-up'.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| query | string | yes | Slack search query. Supports operators like `in:#channel`, `from:@user`, `before:2026-05-10`. |
| sort | string | – | – |
| time_window | string | – | – |
No output schema declared.
No examples provided.
teams_get_channel_messages ~77
Get messages in a Teams channel scoped to the audit time window (default 7d; pass any window). Returns id, from, body, createdDateTime, replies count.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | – |
| team_id | string | yes | – |
| time_window | string | – | – |
| top | integer | – | – |
No output schema declared.
No examples provided.
teams_get_chat_messages ~61
Get messages in a Teams chat (DM or group) scoped to the audit window. Returns id, from, body, createdDateTime.
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string | yes | – |
| time_window | string | – | – |
| top | integer | – | – |
No output schema declared.
No examples provided.
teams_list_channels ~43
List channels within a Microsoft Teams team. Returns id, displayName, description, membershipType.
| Name | Type | Req | Description |
|---|---|---|---|
| team_id | string | yes | Team ID from teams_list_teams. |
No output schema declared.
No examples provided.
teams_list_chats ~45
List the authenticated user's 1:1 and group chats in Microsoft Teams. Returns id, chatType, topic, lastUpdatedDateTime.
| Name | Type | Req | Description |
|---|---|---|---|
| top | integer | – | – |
No output schema declared.
No examples provided.
teams_list_teams ~45
List Microsoft Teams the authenticated user has joined. Returns id, displayName, description. Use this first to pick a team for channel audits.
| Name | Type | Req | Description |
|---|---|---|---|
| top | integer | – | – |
No output schema declared.
No examples provided.
What is the Pickle MCP server?
Pickle is an MCP server listed in the public MCP registry as io.github.adityaarsharma/pickle. Free, local MCP server that audits ClickUp, Slack & Teams for work that slipped through. This page covers its npm package (pickle-mcp).
Is the Pickle MCP server safe to use?
Pickle scores 77 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. 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 Pickle MCP server expose?
Pickle exposes 57 tools: pickle_setup, clickup_get_workspace_hierarchy, clickup_get_workspace_members, clickup_find_member_by_name, clickup_resolve_assignees, and 52 more. Their descriptions and schemas cost roughly 3,830 tokens of context every time the server is loaded.
Is the Pickle MCP server still maintained?
Pickle 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 Pickle MCP server under?
Pickle declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.