How It Spread

Viral precedents with sourced, dated spread timelines and a Spread Score. Each answer cites a case.

Should I use this

Quality & Safety

A
Description quality
93%
Schema completeness
71%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~609Tokens (tool definitions)
~1.4 KBTypical response size
Minimal attention impact (0.48% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "howitspread": {
      "url": "https://howitspread.com/api/mcp"
    }
  }
}

Remote endpoints

https://howitspread.com/api/mcpstreamable-http

What it can do

Tool inventory

Tools (3)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢search_cases(query, kind, mechanic, platform, limit)

Search the How It Spread library of viral cases (films, products, memes, campaigns) by text, kind, mechanic or platform. Returns each case's Spread Score, dates, platforms, mechanics, an image URL and the case URL to cite.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Free text: a brand, product, film, format or idea."
    },
    "kind": {
      "type": "string",
      "enum": [
        "campaign",
        "product",
        "food",
        "app",
        "film",
        "series",
        "music",
        "game",
        "book",
        "creator",
        "meme",
        "trend",
        "activity",
        "moment"
      ]
    },
    "mechanic": {
      "type": "string",
      "enum": [
        "remixable-template",
        "audio-meme",
        "catchphrase",
        "shareable-output",
        "daily-ritual",
        "challenge",
        "response-chain",
        "low-effort-copy",
        "identity-badge",
        "scarcity-drop",
        "variable-reward",
        "collectible-set",
        "visible-use",
        "unscripted-proof",
        "underdog",
        "founder-origin",
        "mystery-lore",
        "spectacle",
        "controversy",
        "transgression",
        "celebrity-amplifier",
        "creator-relay",
        "fandom-mobilisation",
        "brand-pile-on",
        "platform-jump",
        "press-loop",
        "political-adoption",
        "dupe-economy",
        "resale-market",
        "sell-out-loop",
        "counter-programming",
        "newsjacking",
        "mascot-persona",
        "unhinged-voice",
        "nostalgia-revival"
      ],
      "description": "A spread mechanic id; list_mechanics defines them."
    },
    "platform": {
      "type": "string",
      "enum": [
        "tiktok",
        "instagram",
        "youtube",
        "x",
        "reddit",
        "facebook",
        "threads",
        "snapchat",
        "twitch",
        "chat",
        "xiaohongshu",
        "press",
        "tv",
        "audio",
        "retail",
        "box-office",
        "app-store",
        "web"
      ],
      "description": "A platform the case spread on."
    },
    "limit": {
      "type": "number",
      "default": 10,
      "maximum": 50
    }
  }
}
🟢get_case(slug)

One case: its dated spread timeline (seed, first amplifier, platform jumps, press, peak), Spread Score and citation. A free account reads every event; Pro adds the playbook (why it worked, what to do), every sourced number and the sources.

Input Schema

{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "description": "The case slug from search_cases."
    }
  },
  "required": [
    "slug"
  ]
}
🟢list_mechanics

The closed vocabulary of spread mechanics, each defined, with how many cases use it.

Input Schema

{
  "type": "object",
  "properties": {}
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded3 tools