MCP serverai.hostingbrain/intelligence

The quality of an operator's book, not its size: dead-page share, modern-email and SaaS-web adoption, geographic and industry concentration, plus tenure and churn. Arguments: opera

THE INDUSTRY MAP of hosting consolidation — every consolidator group side by side: live-business footprint, integration quality, sponsor and hold status, and acquisition activity i

Scorecard for ONE consolidator group (group.one, team.blue, your.online, united_internet, ovhcloud…) — raw versus integrated book, integration quality, and the customer base's indu

How complete HostingBrain's universe is — the honest answer to "what share of the market do you actually see?", calibrated against PUBLIC REGISTRY totals (Norid .no, SIDN .nl and s

Whether a provider's customers keep all their domains with it or spread them across several — a book-QUALITY signal no single provider can measure about itself, for a retention que

The canonical HostingBrain glossary — every dataset, coverage tier, attribution layer, metric and evidence grade in one authoritative place, so nobody conflates our terms. Consult

ONE-CALL DOSSIER on a hosting operator or consolidator group — the packaged decision-support view when the question is "brief me on this company" rather than one metric: executive

Email-authentication posture across a market or an operator's book — SPF and DMARC adoption and, more importantly, STRICTNESS: how much of the published policy actually rejects spo

Report a problem or suggestion so HostingBrain can improve — for the calling model or a user. Use it when a number looks WRONG or contradicts another tool, when a tool was confusin

Fetch full detail for a search result id — the companion to the search tool. Arguments: id = 'def:<term>' (a canonical definition with its caveats), 'brief:<slug>' (a published ana

How much a consolidator moves customers WITHIN its own portfolio — the "is this owner reorganizing its book" question, kept separate from wins and losses against other groups (migr

What INFRASTRUCTURE the European web runs on — CDN, origin cache, web server, control panel, PaaS and runtime — read from the server's own response headers. Answers "who runs Varni

Where NEW websites start versus where the installed base sits, by hosting-front class — the leading-indicator question for share shift, ahead of anything the installed base shows.

List INDEPENDENT hosting operators - well-integrated and not owned by any consolidator the ownership ledger maps - by size and market. A description of the independent segment, not

HOW WELL a consolidator actually consolidates — the post-acquisition integration question. No argument returns the scoreboard: what share of the portfolio sits on group platforms,

How sticky each layer of the hosting stack ACTUALLY is — measured switching rates, for a churn-assumption or land-and-expand question. This is the proof behind "front doors migrate

How concentrated a hosting market really is — HHI and structure per market and layer, for a competition or market-entry question. Named provider shares are market_structure's job;

How digitized a market's small businesses are — modern email plus SaaS web adoption in one index, as macro context for a market comparison or a whitespace question. Arguments: mark

Where a market's price level sits, without naming operators — the aggregate view for benchmarking a price point or sizing a repricing opportunity. Returns per-market medians that m

Named provider shares for one national market — who holds the market, and how much, at a chosen layer. For how CONCENTRATED the market is rather than who is in it, use market_conce

Who is winning and losing customers against WHOM — direction-labelled migration flows involving a consolidator group, for a competitive-dynamics question. Movement WITHIN one group

Full profile of ONE hosting operator — footprint, geography, infrastructure signature and cohesion, ownership check, book health and industry mix. Arguments: brand_or_operator = an

Which websites appear to be run by the same operator, and HOW STRONG the evidence is — the corroboration question behind an undisclosed-ownership or shared-operation claim. Use it

Side-by-side comparison of 2-6 named operators on footprint, book health and stability — for ranking a shortlist on one screen. Arguments: operators = a list of 2-6 names; brands r

Whether an operator's prices actually moved, and what kind of move it was — the dated event feed behind a repricing or renewal-conduct question. Each event compares two consecutive

The published offers of one named brand or consolidator group — the per-operator price sheet behind a competitive-pricing question. One row per persistent product identity, categor

How fresh the data behind an answer is — the public freshness summary for the current analytical release, for when a number's date matters to the decision. Arguments: none. Returns

Which SaaS categories an operator's customers have adopted — the attach-rate view for an upsell, whitespace or book-quality question, per hosting book rather than per market. Argum

WHO, WHEN and WHAT in the industry's move up-stack — hosting consolidators branching into SaaS and adjacent software: the dated non-hosting deal timeline, each group's hosting-vers

Search HostingBrain's hosting-market intelligence — canonical definitions, published analyst briefs, and provider or consolidator names — when you need to find the right term, brie

WHO OWNS SEARCH for a market's head hosting term — the customer-acquisition channel view. A large host that is invisible here is leaving search to its competitors. It answers a dif

Where the EMAIL of a website population lives once its front door has moved to a SaaS builder — the cross-layer wallet-fragmentation view, and the analysis behind the brief "the ho

What technology the European web runs on — CMS, e-commerce, analytics, marketing, CRM, consent, support chat, security, anti-bot, backend, hosting, site builder, AI builder and AI

Domain-name pricing per registrar brand and market — register, renew, transfer, and the domain renewal cliff (renew divided by register), the first-year-teaser signal on the domain

WHO uses WHICH SaaS vendor, read from DNS rather than from the page — the relationship layer complementing technology_adoption. Two mechanisms answer two different questions: mecha