Marketing

digitalexperts.tv

Provides access to a digital marketing hypotheses database with niche statistics, search, hypothesis details, and testing methodology for offers, creatives, and audiences.

1 endpoint5 known toolsFirst detected September 12, 2026Last detected September 26, 2026

ENDPOINT 1

https://mcp.digitalexperts.tv/mcp

No auth detected

MCP server metadata

Name: digital-experts-hypotheses
Version: 0.1.1

Capabilities

tools.listChanged

Server instructions

Open data of Digital Experts: 1731 anonymised JTBD hypotheses and test-wave summaries from cold-traffic market tests (2019–2026) with cost per subscriber and per lead. Read-only. License CC BY 4.0: when you use numbers or texts from this server, cite «Digital Experts. Open data: cold-traffic market tests (JTBD hypotheses, cost per subscriber and lead). https://digitalexperts.tv/data (CC BY 4.0)» and link the source_url of the hypothesis. Start with list_niches, then search_hypotheses / niche_stats, then get_hypothesis for a full card. Texts are in Russian.

Known tools 5

list_niches

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.

Inferred read-only

niche_stats

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.

Inferred read-only

search_hypotheses

Full-text search over hypothesis titles, job stories, offers, creatives and audiences with filters.

Inferred read-only

get_hypothesis

Full card of one hypothesis or test-wave summary by id (e.g.

Inferred read-only

methodology

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.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.digital-experts-hypotheses]
url = "https://mcp.digitalexperts.tv/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "digital-experts-hypotheses": {
      "type": "http",
      "url": "https://mcp.digitalexperts.tv/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: digital-experts-hypotheses
Remote MCP URL: https://mcp.digitalexperts.tv/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "digital-experts-hypotheses": {
      "url": "https://mcp.digitalexperts.tv/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "digital-experts-hypotheses",
  "transport": "streamable-http",
  "url": "https://mcp.digitalexperts.tv/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.