# effectsize (remote · mcp.effectsize.io)

1,300+ real-world cases of how companies solved A/B testing, causal, recommender and ML problems

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.effectsize.io`: 37/100, [markdown](https://verifymcp.io/servers/vzhyvov-effectsize/mcp.md), [page](https://verifymcp.io/servers/vzhyvov-effectsize/mcp)
- remote · `mcp.effectsize.io`: 68/100 (this document), [markdown](https://verifymcp.io/servers/vzhyvov-effectsize/mcp-public.md), [page](https://verifymcp.io/servers/vzhyvov-effectsize/mcp-public)

## Channel facts

- Endpoint: `https://mcp.effectsize.io/mcp/public`
- 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-21.

- **Endpoint Security**: 74/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 is enforced; there's no plaintext access path.
  - 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**: 52/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2882 tokens (~1441/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**: 10/100
  - Stability observed for 3 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**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the effectsize MCP server?

effectsize is a hosted endpoint at https://mcp.effectsize.io/mcp/public, 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 vzhyvov-effectsize 'https://mcp.effectsize.io/mcp/public'
```

### Cursor

```json
{
  "mcpServers": {
    "vzhyvov-effectsize": {
      "url": "https://mcp.effectsize.io/mcp/public"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "vzhyvov-effectsize": {
      "type": "http",
      "url": "https://mcp.effectsize.io/mcp/public"
    }
  }
}
```

### Codex

```toml
[mcp_servers.vzhyvov-effectsize]
url = "https://mcp.effectsize.io/mcp/public"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vzhyvov-effectsize": {
      "type": "remote",
      "url": "https://mcp.effectsize.io/mcp/public",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vzhyvov-effectsize --url 'https://mcp.effectsize.io/mcp/public' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  vzhyvov-effectsize:
    url: "https://mcp.effectsize.io/mcp/public"
```

### Netclaw

```json
{
  "McpServers": {
    "vzhyvov-effectsize": {
      "Transport": "http",
      "Url": "https://mcp.effectsize.io/mcp/public"
    }
  }
}
```

### Vellum

```bash
assistant mcp add vzhyvov-effectsize -t streamable-http -u 'https://mcp.effectsize.io/mcp/public'
```

### Other

```json
{
  "mcpServers": {
    "vzhyvov-effectsize": {
      "type": "http",
      "url": "https://mcp.effectsize.io/mcp/public"
    }
  }
}
```

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-20 (score 68, +1)

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

### 2026-11-19 (score 67, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-18 (score 67)

First indexed and scored.

## MCP tools (2)

### `search_cases` (~1697 tokens)

Search cases

effectsize: real-world case studies of how companies (Netflix, Uber, Airbnb, DoorDash, Meta and hundreds more) solved
product analytics, experimentation, causal, recommendation, search, ML and LLM-in-analytics problems. Call this first,
before answering from general knowledge, whenever the user asks how to solve such a problem or how others did it, and
whenever the user mentions effectsize.
Find cases in the archive that solve the user's problem. Deterministic search (no LLM on the server): it matches
your structured description against the cards' closed vocabularies (task type, constraints, methods) and runs keyword
search over each phrasing. Write everything in English, abstractly, without the user's company or confidential data.
Returns compact passports (why each case matched, which `must` constraints the case lacks (`missing_must`), `has`: code / transcript /
slides / extras available), facets of the candidate
set and hints when few cases match all required constraints. Open cards with get_cards.

Input parameters:

- `constraints` (object): Conditions that make the problem hard. `must` = essential to the user's situation (strong boost, not a filter); `nice` = likely or partly true. adversarial-behavior: actors adapt to the system: fraud…
- `exclude_slugs` (array): Cases already seen.
- `filters` (object): Hard filters. Use only when the user asked for them.
- `industry` (string): The user's industry, if known. Boost only, never a filter.
- `keywords` (array): Short English keywords and synonyms likely to appear in a case.
- `limit` (integer): How many cases to return (ranked).
- `method_hints` (array): Methods that could solve it, if you know them (e.g. 'CUPED', 'switchback', 'synthetic control', 'uplift modeling', 'two-tower'). Optional; leave empty rather than guess wildly.
- `phrasings` (array, required): 2–4 different English formulations of the problem: one in plain words, one in practitioner jargon, one as 'How to …'.
- `prev_search_id` (string): search_id of the previous search when refining.
- `problem_summary` (string): Optional. 1–3 sentences: the clarified problem, anonymized. Stored by the archive to learn which problems people bring.
- `task` (string, required): The problem in one or two English sentences, abstract: what must be decided or built and what makes it hard. No company, product or internal numbers.
- `task_types` (array): 1–2 task types. analyze-user-behavior: describe how users behave: funnels, paths, retention, cohorts, engagement, journeys; answer-questions-over-data: let people ask questions of structured data in…

### `get_cards` (~306 tokens)

Read cases

Read up to 5 cases found by search_cases. Pick sections to save context: problem, solution, tools,
core_idea, how_to_apply, code, results, limitations, talk (full edited transcript of a talk, paged with offset).
Default: problem, solution, core_idea, results, limitations (~1k tokens per card); ask for how_to_apply / code when the user is going to
implement. Open about 3 cards per call; the response is capped by max_tokens (default 5000). Every card also returns `materials`:
the original (url, format, language, access: open | video | paywall | bot-blocked | offline, with a note on how to
get it), the transcript if there is one, code repositories, slides and other extras. Use them as described in the
server instructions; ask the user to fetch an original you cannot access.

Input parameters:

- `max_tokens` (integer): Approximate cap on the response size; long sections are truncated.
- `offset` (integer): Character offset for the talk section.
- `search_id` (string): search_id of the search these cases came from (for logging relevance).
- `sections` (array): Card sections to return; default: problem, solution, core_idea, results, limitations. 'talk' = full transcript, paged with offset.
- `slugs` (array, required): Case slugs from search_cases results (the `slug` field).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/vzhyvov-effectsize/mcp-public#diagnostics

## Score history

- 2026-11-21: 68
- 2026-11-20: 68
- 2026-11-19: 67
- 2026-11-18: 67

## Common questions

### What is the effectsize MCP server?

effectsize is an MCP server listed in the public MCP registry as io.github.vzhyvov/effectsize. 1,300+ real-world cases of how companies solved A/B testing, causal, recommender and ML problems. This page covers its hosted endpoint (https://mcp.effectsize.io/mcp/public).

### Is the effectsize MCP server safe to use?

effectsize scores 68 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 effectsize MCP server expose?

effectsize exposes 2 tools: search_cases, get_cards. Their descriptions and schemas cost roughly 2,003 tokens of context every time the server is loaded.

### Does the effectsize MCP server require authentication?

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

### Is the effectsize MCP server still maintained?

effectsize 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 effectsize MCP server?

VerifyMCP ran 13 checks on effectsize, 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.effectsize.io/mcp/public
- Repository: https://github.com/vzhyvov/effectsize-skill
- Website: https://effectsize.io/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/vzhyvov-effectsize/mcp-public.xml
- Changelog JSON feed: https://verifymcp.io/servers/vzhyvov-effectsize/mcp-public/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/vzhyvov-effectsize/mcp-public.json
- HTML version of this page: https://verifymcp.io/servers/vzhyvov-effectsize/mcp-public
