# Digital Experts Hypotheses (remote · mcp.digitalexperts.tv)

Open data: 1,590 JTBD hypotheses with cold-traffic test results and cost per lead. CC BY 4.0

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `mcp.digitalexperts.tv`: 77/100 (this document), [markdown](https://verifymcp.io/servers/tv-digitalexperts-hypotheses/mcp.md), [page](https://verifymcp.io/servers/tv-digitalexperts-hypotheses/mcp)

## Channel facts

- Endpoint: `https://mcp.digitalexperts.tv/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-10-04.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 78/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 610 tokens (~122/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 67% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Digital Experts Hypotheses MCP server?

Digital Experts Hypotheses is a hosted endpoint at https://mcp.digitalexperts.tv/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 tv-digitalexperts-hypotheses 'https://mcp.digitalexperts.tv/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tv-digitalexperts-hypotheses": {
      "url": "https://mcp.digitalexperts.tv/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tv-digitalexperts-hypotheses": {
      "type": "http",
      "url": "https://mcp.digitalexperts.tv/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tv-digitalexperts-hypotheses]
url = "https://mcp.digitalexperts.tv/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tv-digitalexperts-hypotheses": {
      "type": "remote",
      "url": "https://mcp.digitalexperts.tv/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tv-digitalexperts-hypotheses --url 'https://mcp.digitalexperts.tv/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tv-digitalexperts-hypotheses:
    url: "https://mcp.digitalexperts.tv/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tv-digitalexperts-hypotheses": {
      "Transport": "http",
      "Url": "https://mcp.digitalexperts.tv/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tv-digitalexperts-hypotheses -t streamable-http -u 'https://mcp.digitalexperts.tv/mcp'
```

### Other

```json
{
  "mcpServers": {
    "tv-digitalexperts-hypotheses": {
      "type": "http",
      "url": "https://mcp.digitalexperts.tv/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-10-03 (score 77, +1)

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

### 2026-10-01 (score 76, +1)

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

### 2026-09-29 (score 75, +1)

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

### 2026-09-28 (score 74, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 74, +1)

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

### 2026-09-25 (score 73, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-22 (score 72, +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-09-20 (score 71, +1)

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

## MCP tools (5)

### `list_niches` (~68 tokens)

Niches with counts and medians

All 18 niches of the Digital Experts hypotheses base with counts (hypotheses, tested, worked) and medians (cost per subscriber, cost per lead, USD) over tested hypotheses. Start here to pick a niche. Data: CC BY 4.0, cite Digital Experts.

### `niche_stats` (~85 tokens)

Niche summary

Summary of one niche: hypotheses, tested, worked, medians of cost per subscriber and per lead (USD), test budget, years, plus the 10 cheapest-lead tested hypotheses. niche = slug or Russian name (e.g. 'biznes-prodazhi' or 'Бизнес').

Input parameters:

- `niche` (string, required): Niche slug or name, see list_niches

### `search_hypotheses` (~172 tokens)

Search hypotheses

Full-text search over hypothesis titles, job stories, offers, creatives and audiences with filters. Returns compact rows (id, title, niche, year, cost per subscriber/lead, verdict, source_url). Use get_hypothesis(id) for the full card. Query in Russian works best (the base is in Russian).

Input parameters:

- `completeness` (string): tested = launched with ads; wave = test-wave summary
- `limit` (integer)
- `max_cost_lead` (number): Only rows with cost per lead ≤ this, USD
- `niche` (string): Niche slug or name
- `query` (string): Words to look for (Russian preferred), e.g. 'английский для детей'
- `verdict` (string)
- `year_from` (integer)

### `get_hypothesis` (~90 tokens)

Hypothesis card

Full card of one hypothesis or test-wave summary by id (e.g. 'h-22788a'): job story, audience, offer, creative text, budget, metrics, conclusion, plus a ready-made citation sentence and source_url. Quote the citation with the link.

Input parameters:

- `id` (string, required): Hypothesis id from search_hypotheses, e.g. h-22788a

### `methodology` (~51 tokens)

How the tests were run

Methodology of the Digital Experts base: where hypotheses come from, how a $50–500 exploratory test is run, what is measured, how verdicts are made, limitations and license. Read before interpreting the numbers.

## Diagnostics

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

## Score history

- 2026-10-04: 77
- 2026-10-03: 77
- 2026-10-02: 76
- 2026-10-01: 76
- 2026-09-30: 75
- 2026-09-29: 75
- 2026-09-28: 74
- 2026-09-27: 74
- 2026-09-26: 73
- 2026-09-25: 73
- 2026-09-24: 72
- 2026-09-23: 72
- 2026-09-22: 72
- 2026-09-21: 71
- 2026-09-20: 71
- 2026-09-19: 70
- 2026-09-18: 70
- 2026-09-17: 69
- 2026-09-16: 69
- 2026-09-15: 68
- 2026-09-14: 68
- 2026-09-13: 67
- 2026-09-12: 67
- 2026-09-11: 66

## Common questions

### What is the Digital Experts Hypotheses MCP server?

Digital Experts Hypotheses is an MCP server listed in the public MCP registry as tv.digitalexperts/hypotheses. Open data: 1,590 JTBD hypotheses with cold-traffic test results and cost per lead. CC BY 4.0. This page covers its hosted endpoint (https://mcp.digitalexperts.tv/mcp).

### Is the Digital Experts Hypotheses MCP server safe to use?

Digital Experts Hypotheses scores 77 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 Digital Experts Hypotheses MCP server expose?

Digital Experts Hypotheses exposes 5 tools: list_niches, niche_stats, search_hypotheses, get_hypothesis, methodology. Their descriptions and schemas cost roughly 466 tokens of context every time the server is loaded.

### Does the Digital Experts Hypotheses MCP server require authentication?

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

### Is the Digital Experts Hypotheses MCP server still maintained?

Digital Experts Hypotheses is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.digitalexperts.tv/mcp
- Website: https://digitalexperts.tv/data
- Changelog RSS feed: https://verifymcp.io/servers/tv-digitalexperts-hypotheses/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/tv-digitalexperts-hypotheses/mcp.json
- HTML version of this page: https://verifymcp.io/servers/tv-digitalexperts-hypotheses/mcp