HostingBrain Intelligence

ai.hostingbrain/intelligence · v0.9.2

Market research on European hosting and domains: ownership, structure, pricing, technology adoption.

MCPremoteno credentialsCRM & salesEmail

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 35 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

A 91/100

What it does: 35 tools · 34 read, 1 write · CRM & sales, Email, Web search & scraping

Test call stack_profile: worked (8,369 ms)

How the rating is made

Answers without login: +30
Speed of first answer: +10
Lists tools: +10
Tool descriptions: +15
Parameter descriptions: +1
Read/write annotations: +5
Safe test call: +20
More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL

https://mcp.hostingbrain.ai/mcp

Tools

35 tools listed at last check

market_structure 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 ran
stack_profile 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. 'hy
hosting_momentum 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) o
market_concentration 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 marke
market_pricing 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
tld_pricing 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:
search_visibility 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 (
pricing_profile 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 me
pricing_moves 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, merchandisin
email_security 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; ope
layer_stickiness 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 SV
saas_adoption 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
technology_adoption 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 head
header_adoption 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 i
vendor_adoption 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' =
independent_operators 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 ma
operator_profile 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-s
consolidator_scorecard 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
book_health 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 unit
migration_flows 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 cus
peer_compare 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 measu
consolidation_landscape 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
integration_depth 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). Argume
dossier 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 acqu
coverage_calibration 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 co
customer_faithfulness 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, avera
group_movement 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 intern
ownership_evidence 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: do
search 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
fetch 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).
provenance 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=…).
feedback 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; ab
definitions 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 respons
saas_diversification 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
market_digitization 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, ea

Badge

Markdown for your README

[![Connect-MCP](https://clawy.uk/mcp/badge/ai.hostingbrain/intelligence.svg)](https://clawy.uk/mcp/s/ai.hostingbrain/intelligence)

Website