# Will It Stick (remote · mcp.willitstick.app)

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

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- remote · `mcp.willitstick.app`: 70/100 (this document), [markdown](https://verifymcp.io/servers/app-willitstick-will-it-stick/mcp.md), [page](https://verifymcp.io/servers/app-willitstick-will-it-stick/mcp)

## Channel facts

- Endpoint: `https://mcp.willitstick.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-22.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http app-willitstick-will-it-stick 'https://mcp.willitstick.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-willitstick-will-it-stick": {
      "url": "https://mcp.willitstick.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-willitstick-will-it-stick": {
      "type": "http",
      "url": "https://mcp.willitstick.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-willitstick-will-it-stick]
url = "https://mcp.willitstick.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-willitstick-will-it-stick": {
      "type": "remote",
      "url": "https://mcp.willitstick.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-willitstick-will-it-stick --url 'https://mcp.willitstick.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-willitstick-will-it-stick:
    url: "https://mcp.willitstick.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-willitstick-will-it-stick": {
      "Transport": "http",
      "Url": "https://mcp.willitstick.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-willitstick-will-it-stick -t streamable-http -u 'https://mcp.willitstick.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-willitstick-will-it-stick": {
      "type": "http",
      "url": "https://mcp.willitstick.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-22 (score 70, +1)

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

### 2026-11-20 (score 69, +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.

### 2026-11-18 (score 68, +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.

### 2026-11-16 (score 67, +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.

### 2026-11-13 (score 66, +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.

### 2026-11-11 (score 65, +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.

### 2026-11-09 (score 64, +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.

### 2026-11-07 (score 63, +1)

- [security] 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

## MCP tools (2)

### `check_if_it_sticks` (~790 tokens)

Check if it sticks

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…

Input parameters:

- `answers` (array): 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.
- `moment` (string): 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.
- `motivation` (string, required): One 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_questions` (boolean): Set true when the author declined the follow-up questions: returns the verdict on the words as they stand.
- `text` (string, required): The exact words to check: a message, note, toast, post, or pitch. A few sentences up to about 900 words.

### `make_it_stick` (~596 tokens)

Make it stick

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.

Input parameters:

- `answers` (array): 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.
- `audience` (string): Optional: who it is for, named plainly, not 'everyone'. Example: 'my team at work'.
- `goal` (string, required): One line: what should these words do? Who should do, feel, or remember what? Example: 'Get parents to thank a teacher this week.'
- `skip_questions` (boolean): Set true when the author declined the seed questions: transforms the words as they stand.
- `text` (string, required): The draft to transform, in the user's own words: a message, note, toast, post, or pitch. A few sentences up to about 900 words.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-willitstick-will-it-stick/mcp#diagnostics

## Score history

- 2026-11-22: 70
- 2026-11-21: 69
- 2026-11-20: 69
- 2026-11-19: 68
- 2026-11-18: 68
- 2026-11-17: 67
- 2026-11-16: 67
- 2026-11-15: 66
- 2026-11-14: 66
- 2026-11-13: 66
- 2026-11-12: 65
- 2026-11-11: 65
- 2026-11-10: 64
- 2026-11-09: 64
- 2026-11-08: 63
- 2026-11-07: 63
- 2026-11-06: 62
- 2026-11-05: 62

## 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 70 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 22 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.

## Links

- Remote endpoint: https://mcp.willitstick.app/mcp
- Repository: https://github.com/wdlcmu/will-it-stick
- Website: https://willitstick.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-willitstick-will-it-stick/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-willitstick-will-it-stick/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/app-willitstick-will-it-stick/mcp.json
- HTML version of this page: https://verifymcp.io/servers/app-willitstick-will-it-stick/mcp
