_ registry / mcp streamable-http · checked 37m ago

digital-experts-hypotheses

https://mcp.digitalexperts.tv

Registry code: ea5c3f564bd47cc4

api record

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.

endpoint
https://mcp.digitalexperts.tv/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is digital-experts-hypotheses live?
Yes — it answered the hub's last check (checked 37m ago). It answered 99% of checks over the last 30 days.
Is digital-experts-hypotheses free to use?
Yes — the hub reached it with no key and no payment.
What tools does digital-experts-hypotheses have?
5 tools: methodology, niche_stats, get_hypothesis, list_niches, search_hypotheses.
Is digital-experts-hypotheses safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.7%

90 days 99.3%· all time 99.3%

latency
617ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 281 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • search tested marketing hypotheses
  • get cost per lead by niche
  • get hypothesis card
takes → gives
text → data
tools
5 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
2 open 3 never probed 2 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_niches reads open 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • search_hypotheses reads open 2h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 15,
          "maximum": 50,
          "minimum": 1
        },
        "niche": {
          "type": "string",
          "description": "Niche slug or name"
        },
        "query": {
          "type": "string",
          "description": "Words to look for (Russian preferred), e.g. 'английский для детей'"
        },
        "verdict": {
          "enum": [
            "worked",
            "failed",
            "ambiguous",
            "unclear",
            "no_conclusion",
            "not_launched"
          ],
          "type": "string"
        },
        "year_from": {
          "type": "integer"
        },
        "completeness": {
          "enum": [
            "tested",
            "prepared",
            "formulated",
            "wave"
          ],
          "type": "string",
          "description": "tested = launched with ads; wave = test-wave summary"
        },
        "max_cost_lead": {
          "type": "number",
          "description": "Only rows with cost per lead ≤ this, USD"
        }
      },
      "additionalProperties": false
    }
    arguments 49 lines
  • methodology reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • niche_stats reads unknown 10h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "niche"
      ],
      "properties": {
        "niche": {
          "type": "string",
          "description": "Niche slug or name, see list_niches"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • get_hypothesis reads unknown 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Hypothesis id from search_hypotheses, e.g. h-22788a"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id ea5c3f564bd47cc4.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ea5c3f564bd47cc4/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/ea5c3f564bd47cc4/badge.svg)](https://brick.blue/agent/ea5c3f564bd47cc4?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.