Servidor MCP de HostingBrain

Quais servidores do registro oficial de MCP são de HostingBrain, se respondem e o que oferecem. Um programa verificou cada item; nada foi copiado da página do produto.

lido em 2026-10-13

← Voltar para HostingBrain

De quem é o servidor

Nome no registroai.hostingbrain/intelligenceverificado no registro MCP

O nome no registro fica sob hostingbrain.ai. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.

Quando perguntamosverificado em 2026-10-13

Estadorespondeverificado em 2026-10-13
Ferramentas35
O servidor se chamahostingbrain-intelligence
Versão do servidor33436d47
Versão do protocolo2025-06-18

Em 2026-10-13 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 633 ms.

Ferramentas que oferece35 ferramentas · lido em 2026-10-13

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 =…
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…
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…
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…
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…
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…
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…
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…
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…
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…
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 =…
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…
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…
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…
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…
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_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…
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…
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…
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…
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…
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…
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…
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…
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…
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…
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…
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…
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…
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…
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…
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…
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…
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…

Como conectar

Adicione o servidor à configuração do seu cliente MCP. Claude Desktop, Cursor e a maioria dos outros clientes leem este formato:

{
  "mcpServers": {
    "intelligence": {
      "type": "http",
      "url": "https://mcp.hostingbrain.ai/mcp"
    }
  }
}

Cada linha é algo que um programa encontrou ao procurar: o registro, a resposta do próprio servidor, uma especificação que se lê. Linha ausente quer dizer que não encontramos, não que não exista.