Market research on European hosting: who owns which brands, what the market charges and how acquired brands integrate, each answer sourced and dated.
This listing identifies a third-party MCP server. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
This server may ask you to sign in when your AI client connects.
Last probed Nov 3, 2026 · mcp.hostingbrain.ai
35tools discovered
For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://mcp.hostingbrain.ai/mcp
Skill page: https://www.mcpbundles.com/skills/hostingbrain-mcp-eb4aa02d2b
Explore capabilities (35)
read 25
Showing 25 of 35
Showing 25 of 35 tools from the public preview. Connect the server to inspect the full live tool list.
Market3
Pricing2
Other capabilities20
Market structure by country
read
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 ranking (an analyst-tier feature — free and pro receive the top 50 plus a tail bucket).
meta.pagination carries the total, has_more and next_offset.
Population: the active-domains book of that market; sh
Description may be truncated on the public preview.
Market structure by country — 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 carries the total, has_more and next_offset.
Population: the active-domains book of that market; sh
Stack fragmentation profile (cross-layer) — 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 overall, and the builder-fronted subset of it, reported
side by side so the two are never read as one.
Me
New-site momentum vs installed base — 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 answers for and are published in this tool's own input schema. Every row says
which kind it is in sc
Market concentration (HHI by market and layer) — 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. chart=true returns a branded SVG.
Population: the active-domains book, at two layers — control_plane
Market pricing landscape (aggregate, unnamed) — 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 side, plus a named list of operators pricing far below the market's entry median
while renewing far
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
Market research on European hosting: who owns which brands, what the market charges and how acquired brands integrate, each answer sourced and dated.
How do I connect HostingBrain to my AI agent?
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
How many tools does HostingBrain provide?
Operate this server?
Request removal if you do not want HostingBrain listed here, or claim the listing if you want to manage it on MCPBundles.
Operate HostingBrain?
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms · Request removal
More in developer tools
Other MCP servers in this category from the directory index
TLD domain pricing (register / renew / cliff) — 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) | matrix (register/renew/transfer per brand); market = ISO country code, any case; tld =
'.com' or '
Search visibility (who owns the hosting SERP) — 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 hosts we do not yet recognize as operators — coverage gaps and onboarding
leads); market = ISO country
Operator pricing profile (package grain) — 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, each figure marked as stated terms or estimate. Group queries add a posture per
brand and market.
Argu
Pricing change events (typed feed) — 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 confirmed economics event.
Arguments: brand_or_group and market narrow the feed to one operator or country
Email security posture (SPF + DMARC adoption and strictness) — 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-domains book — every percentage is of the active domains
that carry mail, not of all websites. A count of
Layer stickiness (measured switching rates) — 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 switch is distinguished from onboarding and lapse journeys, aftermarket rotation, a serving
move that lef
SaaS adoption by operator book — 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 falls back to its group and the response says so. chart=true returns a branded
SVG.
Population: the
Technology & SaaS adoption census — 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 additive.
Arguments: no category/provider/operator = adoption across every category published (free);
Server/infrastructure adoption census (HTTP headers) — 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/operator = adoption across the categories (free); naming category or
provider = the per-provider break
SaaS vendor adoption census (DNS-observed) — 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'); mechanism = verification | spf_include;
market = TLD ('de','nl'); top_n caps the rows; default = the
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
max_results the page size.
Population: independent operators above the infrastructure-cohesion floor, above the size floor, and
not owned by any consolidator the ownership ledger maps.
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-support view across all
sections and its peers, use the dossier tool instead.
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 a brand that resolves to one.
Population: the group's folded book; each figure states the book it is measured on. For the whole
market side by side, use consolidation_landscape.
Book health & stability — 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 health is one call. chart=true adds a branded book-composition SVG.
Population: the named book; the '
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 customer relationship) | host (the serving
network).
Population: observed provider changes between the two dated readings. Magnitudes are DIRECTION-ONLY
until the longitudinal panel calibrates them — rea
Peer comparison — 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.
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 hosting market and how well.
Arguments: none required.
Population: the mapped consolidator groups; each row states the book its footprint is measured on, and
a measurement we do not stand behind for a
Platform integration depth (stages & architecture) — 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
acquisition dates and two drill-down levels that must not be conflated — how much of each brand's book
Operator/group dossier (one-call workflow) — 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 operator ('domeneshop') or a group ('group.one');
detail='summary' (default: executive summary + ri
Coverage & methodology 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 coverage trend); the default
returns the latest calibration per market and metric.
Population: our observed web-provisioned population against officially registered totals for the same
market.
Method: d
Showing the first 25 tools — full list and schemas: Directory API.
MCPBundles probed 35 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
What authentication does HostingBrain require?
HostingBrain may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.
Don't want this listed?
Request removal from the MCPBundles directory. We stop publishing this listing on mcpbundles.com.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.