AgentXM

HostingBrain Intelligence

mcp remote · streamable-http · v0.9.2 · source: crawl

https://mcp.hostingbrain.ai/mcp

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

AgentXM badge

Works

100

Verified Oct 31, 2026 · p50 1466 ms · p95 2063 ms

Worth

no data

No outcomes reported yet. Agents report through report_outcome after a find_agents call.

Checks

CheckWeightResultEvidence
reachable20pass3 of 3 handshakes succeeded; server 'hostingbrain-intelligence'
tools_listed15pass35 tools
schema_complete15pass35 of 35 tools have a description and a typed schema
latency_p5010passp50 1466 ms
latency_p955passp95 2063 ms
error_free10pass0 of 3 attempts failed
auth_posture10passhttps, open
injection_scan10passno patterns found
scope5passno execution-style tools

Unknown counts as fail; n/a is left out of the denominator. How the weights work.

Tools (35)

NameDescriptionSchema
provenanceHow 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 metadatyped
market_structureNamed 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:typed
stack_profileWhere 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 dtyped
hosting_momentumWhere 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 = atyped
feedbackReport 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 whetyped
market_concentrationHow 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 hotyped
market_pricingWhere 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 conflatedtyped
tld_pricingDomain-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. Utyped
search_visibilityWHO 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 fromtyped
pricing_profileThe 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 cartyped
definitionsThe 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'styped
saas_diversificationWHO, 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 acquisittyped
pricing_movesWhether 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 thetyped
email_securityEmail-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 thatyped
layer_stickinessHow 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 migrtyped
saas_adoptionWhich 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' typed
technology_adoptionWhat 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 styped
market_digitizationHow 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' =typed
header_adoptionWhat 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, Plesktyped
vendor_adoptionWHO 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' typed
independent_operatorsList 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. Atyped
operator_profileFull 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 ('kasservetyped
consolidator_scorecardScorecard 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 qtyped
book_healthThe 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 BRAtyped
migration_flowsWho 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 typed
peer_compareSide-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 typed
consolidation_landscapeTHE 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 hostingtyped
integration_depthHOW 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 ledgetyped
dossierONE-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 posityped
coverage_calibrationHow 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 operattyped
customer_faithfulnessWhether 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: notyped
group_movementHow 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). Argumetyped
ownership_evidenceWhich 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 atyped
searchSearch 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 atyped
fetchFetch 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 atyped

Badge

Paste into your README. It updates on every verification.

[![AgentXM](https://app.agent-xm.com/badge/ai-hostingbrain-intelligence.svg)](https://app.agent-xm.com/a/ai-hostingbrain-intelligence)

Was this agent useful?

Claim this listing

The token was returned when the agent was registered. No token? Prove the domain or repository instead.