Pickly
REMOTE · USEPICKLY.COM
Make group polls from a chat and check who's winning. Voters need no account.
Available components
Last scanned (15 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Productivity and Notes
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (review_suggestion). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1185 tokens (~197/item across 6 items; 5 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
- Server version: 1.0.0 → 1.1.0 functional
- 15 Nov 26 +3
- Schema quality: 232 → 197 ▲ functional
- The server now declares the “resources” capability functional
- First check of Capabilities: pass functional
- First check of Schema quality: 100 functional
- Schema quality: excellent → good functional
- New resource “Pickly poll card” functional
- 13 Nov 26 +1
- “create_poll” reworded the description of “resultsEmail” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- New tool “review_voter_request”, which the server declares destructive security
- Tool “review_suggestion” is now declared destructive security
- Schema quality: 897 → 1141 ▼ functional
- “create_poll” added an optional parameter “showVoters” cosmetic
- “create_poll” added an optional parameter “voterNames” cosmetic
- 7 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 −8
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 21 Nov 2026 · Probed https://usepickly.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usepickly.com | CN=WE1,O=Google Trust Services,C=US | 1 Oct 2026 | 30 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d41db41c76517d42138017e6401efd3f |
| SANs: usepickly.com, *.usepickly.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of usepickly.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| usepickly.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://usepickly.com/mcp | Verified | 200 | |
| http (plaintext) | http://usepickly.com/mcp | HTTPS enforced | 301 | https://usepickly.com/mcp |
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 →
close_poll Close a poll ~86
Stop voting on a poll this chat made (it needs the manage key) and get the final results. Only when the person asks: it can only be reopened from the manage link.
| Name | Type | Req | Description |
|---|---|---|---|
| manageKey | string | yes | The manage key create_poll returned for this poll. |
| poll | string | yes | The poll's link (https://usepickly.com/p/…) or its id. |
No output schema declared.
No examples provided.
create_poll Create a poll ~612
Create a Pickly poll to help a group decide something together (where to eat, which date, what to watch) and get a link to share in the group chat. Nobody needs an account to vote.
| Name | Type | Req | Description |
|---|---|---|---|
| allowSuggestions | boolean | – | Let voters suggest more options. Nothing joins the poll until the creator approves it (review_suggestion, or the manage link). |
| allowVoterEmails | boolean | – | Let voters leave an email address to get the results when voting closes. |
| closesInHours | number | – | When voting closes, in hours from when it opens. Defaults to 24. |
| description | string | – | Optional extra context shown under the question. |
| maxChoices | integer | – | multi polls only: how many options each person may tick. Leave out for no limit. |
| opensAt | string | – | When voting opens, as an ISO 8601 date-time with the person's UTC offset, e.g. 2026-11-07T18:00:00+01:00. Leave out to open right away. The link works before then, but voting stays locked. |
| optionKind | string | – | What every option is: a named thing, a calendar date, a time of day, or a place. |
| options | array | yes | 2 to 20 options, all of the optionKind. |
| password | string | – | A password voters type before they can open the poll. Only when the person asks for one; they share it with the link. |
| question | string | yes | What the group is deciding, e.g. "Where do we eat on Friday?" |
| resultsEmail | string | – | The creator's own email address, to get the results when voting closes. Only when they give it and ask for that. Needs a closing time, so not with stayOpen. Pickly first emails that address a link to… |
| showVoters | boolean | – | true shows who voted what: voters pick their name from voterNames, and everyone sees each person's answers. Leave out (or false) for anonymous votes, the default. Use it when the person wants to see… |
| stayOpen | boolean | – | Keep voting open until the creator closes it (close_poll, or the manage link) instead of closing at a set time. |
| voterNames | array | – | With showVoters: the names of everyone who can vote, e.g. the people in the group chat. Only they can vote, each name once. |
| votingStyle | string | – | How people vote. multi: tick every option that works (the default, good for most choices). ranked: put the options in order; an instant runoff picks the winner. score: 1 to 5 stars each. swipe: yes o… |
No output schema declared.
No examples provided.
get_results Get poll results ~102
Read the current standings of a Pickly poll: who's winning, by how much, and whether voting has closed. With the poll's manage key it also lists suggestions waiting for review.
| Name | Type | Req | Description |
|---|---|---|---|
| manageKey | string | – | The poll's manage key, if this chat made it: also lists suggestions waiting for review, and opens password-protected polls. |
| poll | string | yes | The poll's link (https://usepickly.com/p/…) or its id. |
No output schema declared.
No examples provided.
review_suggestion Review a suggested option ~132
Approve or turn down an option a voter suggested on a poll this chat made (it needs the manage key). Approved suggestions become options everyone can vote on. Check with the person before deciding for them.
| Name | Type | Req | Description |
|---|---|---|---|
| approve | boolean | yes | true adds it to the poll as an option; false turns it down. Either is final. |
| manageKey | string | yes | The manage key create_poll returned for this poll. |
| poll | string | yes | The poll's link (https://usepickly.com/p/…) or its id. |
| suggestionId | string | yes | The suggestion's id, from get_results. |
No output schema declared.
No examples provided.
review_voter_request Answer a request to vote ~131
On a poll that shows who voted, add someone who asked to be on the list of names, or turn them down (needs the manage key). Check with the person before deciding for them.
| Name | Type | Req | Description |
|---|---|---|---|
| approve | boolean | yes | true adds the name to the poll's list so they can vote; false turns it down. |
| manageKey | string | yes | The manage key create_poll returned for this poll. |
| poll | string | yes | The poll's link (https://usepickly.com/p/…) or its id. |
| requestId | string | yes | The request's id, from get_results. |
No output schema declared.
No examples provided.
How do I install the Pickly MCP server?
Pickly is a hosted endpoint at https://usepickly.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · usepickly.com
claude mcp add --transport http com-usepickly-pickly 'https://usepickly.com/mcp'
What is the Pickly MCP server?
Pickly is an MCP server listed in the public MCP registry as com.usepickly/pickly. Make group polls from a chat and check who's winning. Voters need no account. This page covers its hosted endpoint (https://usepickly.com/mcp).
Is the Pickly MCP server safe to use?
Pickly scores 74 out of 100 on VerifyMCP. 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 Pickly MCP server expose?
Pickly exposes 5 tools: create_poll, get_results, review_suggestion, review_voter_request, close_poll. Their descriptions and schemas cost roughly 1,063 tokens of context every time the server is loaded.
Does the Pickly MCP server require authentication?
No. We connected to Pickly without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Pickly MCP server still maintained?
Pickly is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Pickly MCP server?
VerifyMCP ran 14 checks on Pickly, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.