Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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

0 this week 80 Trust /100

Last scanned (22 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage89
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 67% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Oct 26 0
    • Stability: 0.97 → pass security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 12 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 11 Sept 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.digitalexperts.tv/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.digitalexperts.tv CN=YE1,O=Let's Encrypt,C=US 10 Nov 2026 8 Feb 2027 ECDSA 256 ECDSA-SHA384 6120ab9946b75b19b808e90f4f149088e44
SANs: mcp.digitalexperts.tv
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.digitalexperts.tv. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
tv. DS published 57277 8 Verified
digitalexperts.tv. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.digitalexperts.tv/mcp Verified 200
http (plaintext) http://mcp.digitalexperts.tv/mcp HTTPS enforced 301 https://mcp.digitalexperts.tv/mcp
MCP tools · 5 exposed · ~466 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_hypothesis ~90

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.

NameTypeReqDescription
idstringyesHypothesis id from search_hypotheses, e.g. h-22788a

No output schema declared.

No examples provided.

list_niches ~68

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

methodology ~51

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

niche_stats ~85

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 'Бизнес').

NameTypeReqDescription
nichestringyesNiche slug or name, see list_niches

No output schema declared.

No examples provided.

search_hypotheses ~172

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).

NameTypeReqDescription
completenessstring–tested = launched with ads; wave = test-wave summary
limitinteger––
max_cost_leadnumber–Only rows with cost per lead ≤ this, USD
nichestring–Niche slug or name
querystring–Words to look for (Russian preferred), e.g. 'английский для детей'
verdictstring––
year_frominteger––

No output schema declared.

No examples provided.

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.

remote · mcp.digitalexperts.tv

# add to Claude Code
claude mcp add --transport http tv-digitalexperts-hypotheses 'https://mcp.digitalexperts.tv/mcp'
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 80 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 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 Digital Experts Hypotheses MCP server?

VerifyMCP ran 12 checks on Digital Experts Hypotheses, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Digital Experts Hypotheses: Authorization. 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.