Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Will It Stick

REMOTE · MCP.WILLITSTICK.APP

Tests whether your message will stick: grades readability and memorability before you send.

+3 this week 69 Trust /100

Last scanned (23 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Communication

Trust breakdown (7 categories)

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 Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
  • 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
Schema Quality & AI Usability57
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2196 tokens (~1098/item across 2 items; 2 tools + 0 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 Management53
  • Stability observed for 16 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

Changelog

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 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 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.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Nov 26 +1
    • Tool “check_if_it_sticks” rewrote its description, which is the text the model reads security
    • Tool “make_it_stick” rewrote its description, which is the text the model reads security
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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://mcp.willitstick.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=willitstick.app CN=WE1,O=Google Trust Services,C=US 3 Nov 2026 1 Feb 2027 ECDSA 256 ECDSA-SHA256 e4cee5523c0e137c1329e1f676cbdd92
SANs: willitstick.app, mcp.willitstick.app, *.mcp.willitstick.app
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 mcp.willitstick.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
willitstick.app. 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://mcp.willitstick.app/mcp Verified 200
http (plaintext) http://mcp.willitstick.app/mcp Served over HTTP 200
MCP tools · 2 exposed · ~1,386 tokens

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 →

Tool Tokens
check_if_it_sticks ~790

Tests how words someone is about to send will be received — whether an email will land well, how it comes across, whether it could be misunderstood, whether it sounds too harsh, what a manager might misunderstand. Three cold readers (a distracted stranger, a skeptic, and the target reader), each reading cold and never seeing the others, test how the message is actually received against the sender's stated goal. When the words leave gaps only the author can fill (the readers cannot find the point, the proof, or the specifics), the first result has status 'questions_first' and carries up to three short questions built from the readers' own complaints about this text, plus what the readers heard and where they split; a second call with the same text and motivation plus the author's answers returns the sharper, enriched verdict, and a second call with skip_questions true returns the verdict on the words as they stand. A verdict returns four plain grades out of 5, graded directly by the same readers in the same cold read (Easy to read, Holds your attention, The point lands, You'd pass it on; medians across the three readers); for conversation moments (a what's new update, a hard text) a walk_away pair: the thought the author wants the reader to leave with, from the goal, against the thought the readers may actually leave with, from what they heard; the core the readers heard (or the plain split when they heard different points); the readers' own notes including where they split; six SUCCESs medians with the spread between readers and a one-line reason each (the diagnostic layer underneath the plain grades); starter forms only (a proverb line, a curiosity-gap opener, a 3-4 sentence mini-story, concrete swaps for abstract phrases); the one prioritized fix for the element that most blocks the stated goal; and after_text: the draft copied exactly with only that one fix applied by a dedicated guarded step, when the bound passes (null when the bound discards it, with after_re…

NameTypeReqDescription
answersarray–Answers to a previous questions_first result, in the author's own words. Pass the same text and motivation, plus these, to get the enriched verdict.
momentstring–Optional moment name, e.g. 'what's new', 'recommend something', 'a story I tell', 'say thanks', 'ask or invite', 'a hard text'. Helps the target reader sit in the right seat.
motivationstringyesOne line: what should these words do? Who should do, feel, or remember what? Example: 'Get a friend to actually try the book I loved.'
skip_questionsboolean–Set true when the author declined the follow-up questions: returns the verdict on the words as they stand.
textstringyesThe exact words to check: a message, note, toast, post, or pitch. A few sentences up to about 900 words.

No output schema declared.

No examples provided.

make_it_stick ~596

Takes a draft and its goal and returns the version that sticks. The tool scans the draft for its real point (every part of it, human stakes first), then writes three transformations: a CONCRETE COMPARISON (the key fact restated as something the reader can see, the popcorn move), a CORE COMPRESSION (the one line the reader must repeat, like 'School is cancelled'), and a SCENE (one concrete moment built only from what the draft holds). A code fact gate drops any transformation whose numbers are not stated in the draft or a plain derivation of stated numbers; nothing is ever invented. Then cold readers pick the winner by a gist test: each candidate is read cold, the reader's one-line gist is scored against the point and the key fact, and the best-carrying version wins. The author's ORIGINAL competes as a candidate and can win outright: status 'already_sticks' means the words already stick and the original is the version to send. If the scan finds the core is unreachable without inventing (the draft needs a name, a scene, or an identity line only the author holds), the first result has status 'questions_first' with up to three short questions; a second call carrying the author's answers, or with skip_questions true, transforms the words as they stand. The result returns the winning version with its kind label, the original alongside, the losing transformations as alternates, and what a cold reader carried away from the winner. This tool returns a transformed version, not a diagnosis; the diagnosis and scores are the output of check_if_it_sticks. Takes about half a minute: cold readers are not instant. Words sent to this tool are not recorded or kept; the server keeps only daily counts of how many runs happened (integers, no text). The readers run on Cloudflare Workers AI (Meta Llama 3.3 70B); under Cloudflare's published Workers AI terms, text is not retained once it is no longer needed to answer, and it is never used to train AI models.

NameTypeReqDescription
answersarray–Answers to a previous questions_first result, in the author's own words. Pass the same text and goal, plus these, to run the transformation with the seed material included.
audiencestring–Optional: who it is for, named plainly, not 'everyone'. Example: 'my team at work'.
goalstringyesOne line: what should these words do? Who should do, feel, or remember what? Example: 'Get parents to thank a teacher this week.'
skip_questionsboolean–Set true when the author declined the seed questions: transforms the words as they stand.
textstringyesThe draft to transform, in the user's own words: a message, note, toast, post, or pitch. A few sentences up to about 900 words.

No output schema declared.

No examples provided.

Install

How do I install the Will It Stick MCP server?

Will It Stick is a hosted endpoint at https://mcp.willitstick.app/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 · mcp.willitstick.app

# add to Claude Code
claude mcp add --transport http app-willitstick-will-it-stick 'https://mcp.willitstick.app/mcp'
Common questions

What is the Will It Stick MCP server?

Will It Stick is an MCP server listed in the public MCP registry as app.willitstick/will-it-stick. Tests whether your message will stick: grades readability and memorability before you send. This page covers its hosted endpoint (https://mcp.willitstick.app/mcp).

Is the Will It Stick MCP server safe to use?

Will It Stick scores 69 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 Will It Stick MCP server expose?

Will It Stick exposes 2 tools: check_if_it_sticks, make_it_stick. Their descriptions and schemas cost roughly 1,386 tokens of context every time the server is loaded.

Does the Will It Stick MCP server require authentication?

No. We connected to Will It Stick without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Will It Stick MCP server still maintained?

Will It Stick 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 Will It Stick MCP server?

VerifyMCP ran 13 checks on Will It Stick, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.