Digital Experts Hypotheses MCP server
tv.digitalexperts/hypothesesdigitalexperts.tvstreamable-httpv0.1.1Scanned
Open data: 1,590 JTBD hypotheses with cold-traffic test results and cost per lead. CC BY 4.0
5 tools: 2 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Digital Experts Hypotheses MCP server can do
The Digital Experts Hypotheses MCP server is published by digitalexperts.tv, a domain the MCP Registry verified. It has 5 tools. It can create or change data (2 tools: niche_stats and methodology), but cannot delete data. 3 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 19, 2026, version 0.1.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 2Claude Code: ask
methodologyMethodology 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
niche_statsSummary 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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 'Бизнес').
Only reads 3Show 3 read-only tools
get_hypothesisFull card of one hypothesis or test-wave summary by id (e.g.No findings
Why it is in this group
- The name "get_hypothesis" says "get": a word for reading.
Description, as the server wrote it 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.
list_nichesAll 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.No findings
Why it is in this group
- The name "list_niches" says "list": a word for reading.
Description, as the server wrote it 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.
search_hypothesesFull-text search over hypothesis titles, job stories, offers, creatives and audiences with filters.No findings
Why it is in this group
- The name "search_hypotheses" says "search": a word for reading.
Description, as the server wrote it 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).
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:19 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.digitalexperts.tv/mcp: tools/list returned 5 tools to an anonymous client, including niche_stats (write), methodology (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http hypotheses https://mcp.digitalexperts.tv/mcpclaude mcp add --transport http hypotheses https://mcp.digitalexperts.tv/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__hypotheses__list_niches",
"mcp__hypotheses__search_hypotheses",
"mcp__hypotheses__get_hypothesis"
],
"ask": [
"mcp__hypotheses__niche_stats",
"mcp__hypotheses__methodology"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as hypotheses. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/tv.digitalexperts/hypotheses/verify?hash=271e3b081ca8893db86798319f4f4eaf897ed576e1acdbad98626571c364e1ba" | jq -e '.changed == false'Pinned hash 271e3b081ca8, from Nov 19, 2026, 07:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/tv.digitalexperts/hypotheses/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/tv.digitalexperts/hypotheses)Source: MCP Registry. Synced Oct 21, 2026, 18:55 UTC.
Digital Experts Hypotheses MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Digital Experts Hypotheses MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Digital Experts Hypotheses MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Digital Experts Hypotheses MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Digital Experts Hypotheses MCP server have?
- 5 tools: 2 write, 3 read. niche_stats, methodology, list_niches, search_hypotheses and get_hypothesis.
Does the Digital Experts Hypotheses MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Digital Experts Hypotheses MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Digital Experts Hypotheses MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.