List your agent

HostingBrain Intelligence

MCP server● Hosted · onlinev0.9.2

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

Reviews

No review yet. Used HostingBrain Intelligence? Be the first to help others choose.

What it does

HostingBrain Intelligence is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version0.9.2
PriceNot in the registry
First seen26 Sept 2026
Last checked1d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 3h ago (live check)

Hosted endpoint

  • https://mcp.hostingbrain.ai/mcp streamable-http

In Claude Code: claude mcp add --transport http hostingbrain-intelligence https://mcp.hostingbrain.ai/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "hostingbrain-intelligence": {
      "url": "https://mcp.hostingbrain.ai/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 3h ago

ONLINE HostingBrain Intelligence answered an MCP connection on 17 Nov 2026 and introduced itself as hostingbrain-intelligence 4246a8f9 (MCP protocol 2025-06-18).

35 tools offered to AI assistants

  • 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 = contr
  • 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: ma
  • 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 'eur
  • 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.
  • 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-wei
  • 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; us
  • 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; comp
  • 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 entr
  • 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 s
  • 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: marke
  • 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
  • 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 t
Show 23 more
  • 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 itse
  • 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
  • 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
  • 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 ope
  • 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: th
  • 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 t
  • 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 consolid
  • 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. Ar
  • 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 operato
  • 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. Th
  • 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 (
  • 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 atta
  • 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
  • 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 distri
  • 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 t
  • 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
  • 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: que
  • 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-
  • 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
  • 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
  • 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 confidenc
  • 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 th
  • 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; 'ge

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://mcp.hostingbrain.ai/mcpDECLAREDSRC-001 Official MCP Registry1d ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry1d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry1d ago
Websitehttps://hostingbrain.aiDECLAREDSRC-001 Official MCP Registry1d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry1d ago
Version0.9.2DECLAREDSRC-001 Official MCP Registry1d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry1d ago

Change history

Baseline
No change detected yet. History builds up as the robots revisit this server.

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run HostingBrain Intelligence? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor HostingBrain IntelligenceLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of HostingBrain Intelligence?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/hostingbrain-intelligence?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/hostingbrain-intelligence/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about HostingBrain Intelligence

How do I connect HostingBrain Intelligence?

Use the hosted endpoint https://mcp.hostingbrain.ai/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does HostingBrain Intelligence offer?

When Electra Index connected on 17 Nov 2026, it listed 35 tools: market_structure, stack_profile, hosting_momentum, market_concentration, market_pricing, tld_pricing, search_visibility, pricing_profile and more. The full list is in "Live check" above.

Is HostingBrain Intelligence online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 3h ago.