
How It Spread MCP server
Which MCP servers are How It Spread's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-28
- Registry namecom.howitspread/howitspreadverified in the MCP registry
The registry name sits under howitspread.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-28
- Tools3
- Server calls itselfhow-it-spread
- Server version1.2.2
- Protocol version2025-06-18
On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 369 ms.
- Its tools do every use case we checked: trace how a film or product went viral; review sourced timelines of past viral campaigns.
Once connected
- For "trace how a film or product went viral", the likely first call is search_cases.
- For "review sourced timelines of past viral campaigns", the likely first call is search_cases.
- Parameters are untyped or undescribed in 1 of 3 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP score99 of 100answers 100 · does the job 100 · definitions 94 · context 100 · connects 100
- What an agent can do with it2 of 2 use cases
- Answered100% of days7 of 7 daily checks
- Median first answer135 ms
- Space in an agent's context≈ 526 tokensthe definitions of all its tools (3), which an agent carries on every turn
- Tool definitionsA · 94 of 100
- Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 1 of 3
What an agent can do with it
- can do · trace how a film or product went viral
- not sure · compare viral cases by reach, speed and longevity
- can do · review sourced timelines of past viral campaigns
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
search_casesSearch 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.
get_caseOne case: its dated spread timeline (seed, first amplifier, platform jumps, press, peak), Spread Score and citation. Fields that need sign-in come back locked, with the case URL where the full record is.
list_mechanicsThe closed vocabulary of spread mechanics, each defined, with how many cases use it.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"howitspread": {
"type": "http",
"url": "https://howitspread.com/api/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http howitspread https://howitspread.com/api/mcpclaude.ai, ChatGPT and other clients: add https://howitspread.com/api/mcp as a custom connector in the settings.
OpenAPI spec
3 paths, read 2026-10-28. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.