_ registry / mcp streamable-http · checked 1h ago

will-it-stick

https://mcp.willitstick.app

Registry code: eda86e4fb4f1f866

api record

Will it stick? Two tools. make_it_stick transforms a draft into the version that sticks: it scans the draft for its point, writes three transformations (a concrete comparison, the one-line core, a scene), drops any that adds a fact the draft does not hold, and lets cold readers pick the winner by what they actually carry away; the author's original competes too, and can win. check_if_it_sticks runs the message test underneath: three cold readers (a distracted stranger, a skeptic, and the target reader), each reading cold and never seeing the others, score the words against the author's goal.…

endpoint
https://mcp.willitstick.app/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is will-it-stick live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is will-it-stick free to use?
Yes — the hub reached it with no key and no payment.
What tools does will-it-stick have?
2 tools: check_if_it_sticks, make_it_stick.
Is will-it-stick safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
122ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 2 tools
2 never probed 0 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • check_if_it_sticks unknown 1h ago

    Use this when someone asks whether words they are about to send will land: 'Will this email land well?', 'How does this come across?', 'Could this be misunderstood?', 'Does this sound too harsh?', 'What might my manager 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. QUESTIONS FIRST: 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. Ask the author those questions, then call again with the same text and motivation plus answers to get the sharper, enriched verdict; if the author would rather not answer, call again with skip_questions true to get 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_reason saying why; changed_lines counts the lines that differ). The tool never rewrites the draft in full; for the finished version itself, call make_it_stick, which returns the transformation cold readers carried away best (the same readers feed it). Do not use this for shortening, grammar fixes, translation, or generic 'make this clearer' rewriting; the host does those itself. Use it only to test how a finished draft will be received. Your words are not recorded or kept; the server keeps only a daily count of how many checks ran (integers, no text). The three readers run on Cloudflare Workers AI (Meta Llama 3.3 70B); under Cloudflare's published Workers AI terms, your text is not retained once it is no longer needed to answer, and it is never used to train AI models. Show the human the questions, scores, starters, and after_text as returned; the human decides what to send, and the tool sends nothing.

    mcp-tool

    {
      "type": "object",
      "required": [
        "text",
        "motivation"
      ],
      "properties": {
        "text": {
          "type": "string",
          "description": "The exact words to check: a message, note, toast, post, or pitch. A few sentences up to about 900 words."
        },
        "moment": {
          "type": "string",
          "description": "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."
        },
        "answers": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "answer"
            ],
            "properties": {
              "answer": {
                "type": "string",
                "description": "The author's answer, in a few words."
              },
              "question": {
                "type": "string",
                "description": "The question as the tool asked it."
              }
            },
            "additionalProperties": false
          },
          "description": "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."
        },
        "motivation": {
          "type": "string",
          "description": "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": {
          "type": "boolean",
          "description": "Set true when the author declined the follow-up questions: returns the verdict on the words as they stand."
        }
      },
      "additionalProperties": false
    }
    arguments 47 lines
  • make_it_stick unknown 1h ago

    Hand it a draft and its goal; get back 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; pass the author's answers back as answers on a second call, or set skip_questions true to transform 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. Takes about half a minute: cold readers are not instant. Use check_if_it_sticks instead when the human wants the diagnosis and scores first. Your words 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, your text is not retained once it is no longer needed to answer, and it is never used to train AI models.

    mcp-tool

    {
      "type": "object",
      "required": [
        "text",
        "goal"
      ],
      "properties": {
        "goal": {
          "type": "string",
          "description": "One line: what should these words do? Who should do, feel, or remember what? Example: 'Get parents to thank a teacher this week.'"
        },
        "text": {
          "type": "string",
          "description": "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."
        },
        "answers": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "answer"
            ],
            "properties": {
              "answer": {
                "type": "string",
                "description": "The author's answer, in a few words."
              },
              "question": {
                "type": "string",
                "description": "The question as the tool asked it."
              }
            },
            "additionalProperties": false
          },
          "description": "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": {
          "type": "string",
          "description": "Optional: who it is for, named plainly, not 'everyone'. Example: 'my team at work'."
        },
        "skip_questions": {
          "type": "boolean",
          "description": "Set true when the author declined the seed questions: transforms the words as they stand."
        }
      },
      "additionalProperties": false
    }
    arguments 47 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id eda86e4fb4f1f866.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/eda86e4fb4f1f866/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/eda86e4fb4f1f866/badge.svg)](https://brick.blue/agent/eda86e4fb4f1f866?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.