Intelligence MCP

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_concentration. Arguments: market = TLD ('de','nl'); layer = control_plane | hosting | email | web; offset= walks the full ranking (an analyst-tier feature — free and pro receive the top 50 plus a tail bucket). meta.pagination

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 hosting stack didn't disappear — it fragmented". Arguments: market (TLD, e.g. 'no'); operator (control-plane key, e.g. 'hyp.net') — the operator filter is a named-provider feature. Population: the active-domains book overa

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. Arguments: scope = an aggregate ('global', 'europe', or 'europe_screened' — bulk moves excluded, the organic headline) or a single market ('dk'); empty = every row. The allowed values are exactly the scopes this release

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; this tool answers how tight the market is, not who is in it. Arguments: market = 'global', 'europe', or a European market TLD ('dk'); empty = all rows. actor_scope selects which actor base leads the control-plane rows. c

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 must not be conflated (storefront, ownership-group, share-weighted, and a like-for-like entry-rung median), the share of the market priced as an introductory teaser, and hosting AND domain renewal-cliff statistics side by

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 side of the bill. Use it for a named-brand domain price; use market_pricing for a market's aggregate level. Arguments: view = cheapest (register ranked per market and TLD) | cliffs (steepest measured renewal multiples)

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 different question from market_structure's ownership view; compare them, do not substitute one. Arguments: view = leaders (per group: best rank and page-one listings) | rankings (the folded page-one list) | leads (ranked ho

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, category-labelled, each carrying its ladder rung (rung 1 = the entry offer, the cross-brand comparison unit — plan names are merchandising), entitlements, commitment and invoicing terms, and full economics in local currency, ea

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 observations of the SAME persistent product; change_class says what moved (economics = a comparable price, merchandising = promotional presentation only, observation = neither), and alert_grade is true only for a confir

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 spoofed mail rather than merely monitoring it. Arguments: market grain ('global', 'europe', or a European TLD) is open; operator-book grain is a named-provider feature. Population: the mail-carrying part of the active-domai

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 quickly, trust migrates slowly". Arguments: scope = 'global' or 'europe'; empty = both. chart=true returns a branded SVG. Population: the active-domains book over the trailing 26 weeks, annualized. A true provider switc

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. Arguments: grain='group' (default) rolls up to the consolidator that owns the book; grain='operator' drills to one nameserver book. operators = 1-3 comma-separated names to compare; a name with no book at the requested grain

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 API adoption, plus social presence — read from the page itself. Its neighbour header_adoption reads server response headers on a different population; vendor_adoption reads the DNS relationship layer. The three are not a

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 Varnish, LiteSpeed, Plesk, IIS, OpenResty" by operator, market or overall. Its neighbour technology_adoption reads the PAGE instead, on a different population: do not add or compare the two. Arguments: no category/provider/op

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: mechanism='verification' = domain-verification records, evidence the relationship was ESTABLISHED; mechanism='spf_include' = which platform SENDS the domain's email. Arguments: vendor = a name fragment ('openai','sendgrid');

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 a recommendation. Arguments: country_tld filters by the operator's dominant market; min_live sets the size floor and max_results the page size. Population: independent operators above the infrastructure-cohesion floor,

Full profile of ONE hosting operator — footprint, geography, infrastructure signature and cohesion, ownership check, book health and industry mix. Arguments: brand_or_operator = an NS brand ('kasserver.com') or a provider id. Population: that operator's own book. For the packaged one-call decision-support view across all sections and its peers, use the dossier tool instead.

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 industry mix, when the question is about one owner rather than the whole landscape. Arguments: group = the consolidator, or a brand that resolves to one. Population: the group's folded book; each figure states the book it is

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: operator = a consumer BRAND, a nameserver operator, or a consolidator GROUP; brand names resolve automatically (ionos to united_internet, domeneshop to miss_group) and prefer the group rollup, so a whole consolidator's book h

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's own portfolio is group_movement's job, not this one's. Arguments: subject = a consolidator group; layer = ns (the customer relationship) | host (the serving network). Population: observed provider changes between the

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 resolve to the group that owns them. Population: each operator's own book, each figure labelled with the book it is measured on so unlike books are not silently ranked against each other.

THE INDUSTRY MAP of hosting consolidation — every consolidator group side by side: live-business footprint, integration quality, sponsor and hold status, and acquisition activity including the hosting-versus-software mix and latest deal. The one-call orientation on who is consolidating the European hosting market and how well. Arguments: none required. Population: the mapped consolidator groups; e

No parameter schema on file.

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, and how deeply ledger-matched acquisitions were integrated (a low score is a buy-and-hold FINDING, not an error). Arguments: group = a consolidator or a brand that resolves to one, returns the per-brand breakdown with ac

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 summary, market position, book quality, stability, SaaS attach, email-security posture, integration status with the acquisition ledger, assembled risks and a peer table. Arguments: target = a consumer brand ('ionos'), an

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 similar), plus operator-level calibration examples. Arguments: include_history=True returns the full dated series (the coverage trend); the default returns the latest calibration per market and metric. Population: our obs

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 question. Arguments: no argument = the aggregate loyalty distribution (free): share of owners with a single provider, average wallet share, and the cross-border cut. provider= a consolidator or a brand that resolves to one

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 (migration_flows). Arguments: group = a consolidator or a brand that resolves to one; empty = the groups with the most internal movement. Deal tier. chart=true returns a branded SVG. Population: two intent-neutral tiers on th

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 for evidence about a cluster of domains; for a hosting group's book use consolidator_scorecard or dossier. Arguments: domain= finds the cluster containing that domain; operator= takes a cluster's representative domain ke

Search HostingBrain's hosting-market intelligence — canonical definitions, published analyst briefs, and provider or consolidator names — when you need to find the right term, brief or entity before asking a numeric question. Arguments: query = what to look for; results carry ids usable by the fetch tool, plus meta.suggested_tool, an intent-routed pointer into the dedicated analytical tools, which

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 analyst brief summary and link), or 'operator:<group>' (a free-tier aggregate view).

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 the external metadata only. Term-level methodology and book-type definitions are available through definitions(term=…).

No parameter schema on file.

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 confusing or missing, or when you have a suggestion. Arguments: kind = data_error | confusing | missing | suggestion | other; about = the tool or topic it concerns; reference = the specific value or entity in question (e.g. 'tea

The canonical HostingBrain glossary — every dataset, coverage tier, attribution layer, metric and evidence grade in one authoritative place, so nobody conflates our terms. Consult it whenever a term's exact meaning, denominator or confidence grade matters; it is the source every other tool's response points back to. Arguments: no arguments = the full grouped overview; term='<key or phrase>' = one

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-versus-software acquisition mix, and the acquisition clusters the deals fall into. Arguments: none. Population: the curated acquisition ledger — publicly reported deals, each carrying the date its source states. It is a reco

No parameter schema on file.

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: market_grain='country' = the like-for-like national ranking; 'generic_tld' = generic namespaces (.io/.shop/…); '' = both, each row still labelled with its grain. market='pl' (a country code, or a namespace like 'com.au') ret