Pickle MCP Server

pickle-mcp npm v1.1.0

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

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 57

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

  • slack_list_dmsingests untrusted input
  • clickup_add_task_watcherno sensitive capability
  • clickup_create_docno sensitive capability
  • clickup_create_doc_pageno sensitive capability
  • clickup_create_listno sensitive capability
  • clickup_create_list_commentno sensitive capability
  • clickup_create_reminderno sensitive capability
  • clickup_create_spaceno sensitive capability
  • clickup_create_taskno sensitive capability
  • clickup_create_task_commentno sensitive capability
Show 47 more tools ↓
  • clickup_create_threaded_commentno sensitive capability
  • clickup_delete_chat_messageno sensitive capability
  • clickup_delete_commentno sensitive capability
  • clickup_delete_taskno sensitive capability
  • clickup_filter_tasksno sensitive capability
  • clickup_find_member_by_nameno sensitive capability
  • clickup_get_chat_channelno sensitive capability
  • clickup_get_chat_channel_messagesno sensitive capability
  • clickup_get_chat_channelsno sensitive capability
  • clickup_get_chat_message_repliesno sensitive capability
  • clickup_get_docno sensitive capability
  • clickup_get_doc_pagesno sensitive capability
  • clickup_get_folderless_listsno sensitive capability
  • clickup_get_listno sensitive capability
  • clickup_get_list_commentsno sensitive capability
  • clickup_get_list_custom_fieldsno sensitive capability
  • clickup_get_list_tasksno sensitive capability
  • clickup_get_lists_in_folderno sensitive capability
  • clickup_get_spaceno sensitive capability
  • clickup_get_taskno sensitive capability
  • clickup_get_task_commentsno sensitive capability
  • clickup_get_task_membersno sensitive capability
  • clickup_get_threaded_commentsno sensitive capability
  • clickup_get_workspace_hierarchyno sensitive capability
  • clickup_get_workspace_membersno sensitive capability
  • clickup_react_to_chat_messageno sensitive capability
  • clickup_remove_task_watcherno sensitive capability
  • clickup_resolve_assigneesno sensitive capability
  • clickup_search_docsno sensitive capability
  • clickup_search_remindersno sensitive capability
  • clickup_send_chat_messageno sensitive capability
  • clickup_send_chat_replyno sensitive capability
  • clickup_set_task_custom_fieldno sensitive capability
  • clickup_update_chat_messageno sensitive capability
  • clickup_update_commentno sensitive capability
  • clickup_update_doc_pageno sensitive capability
  • clickup_update_taskno sensitive capability
  • pickle_setupno sensitive capability
  • slack_get_channel_historyno sensitive capability
  • slack_list_channelsno sensitive capability
  • slack_list_usersno sensitive capability
  • slack_search_messagesno sensitive capability
  • teams_get_channel_messagesno sensitive capability
  • teams_get_chat_messagesno sensitive capability
  • teams_list_channelsno sensitive capability
  • teams_list_chatsno sensitive capability
  • teams_list_teamsno 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 0 1.10.0 2026-07-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/pickle-mcp/badge.svg)](https://mcptrustchecker.com/registry/pickle-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/pickle-mcp"><img src="https://mcptrustchecker.com/registry/pickle-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/pickle-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 pickle-mcp --online

Use the free API → How scoring works

More in Analytics & Monitoring