Should my agent depend on the MCP server ai.hostingbrain/intelligence?

Verdict: allow — rich-slow-solo — safe to depend on As of 2026-09-13T06:22:43Z: a dated observation with receipts, not a warranty.

HostingBrain Intelligence

ai.hostingbrain/intelligence

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

— the operator's own registry description reported

Publisher ai.hostingbrain · first seen 2026-08-12 · endpoint https://mcp.hostingbrain.ai/mcp

allow

verdict

rich-slow-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow
allow — alive & usable · retrieval-public ● · V3 has answer key ◐

allow — because answers ●, 35 tools legible (band B) ●, no confirmed drift in 7 probes ●; not yet checked: truth (2 attempts unverifiable, 0 disagreements)

Cluster rich-slow-solo · distinctiveness 0.806 (unusual). Every figure is a percentile or class within the 19,148-server census — see the whole spectrum.

Does it answer? Q1 · observed

answersalive_tools

latency407 ms

vs populationslow

protocolcurrent

authopen

Can it be used? Q4 · observed

tools35

vs populationhigh

capabilities5

harnessB

Did it hold when checked? Q3–Q4 · derived

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers true0/0 agree

🔏 Signed receipt rr_4fbf39df8b7a62fa487b9b83 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Q1Does it answer?alive & usable — 7 probes ●evidence ↓

Q2What is it?retrieval-public ● evidence ↓

Q3Can it be checked?V3 has answer key ◐evidence ↓

Q4Did it hold?harness B · truth not yet run · no drift ●evidence ↓

Q5What company does it keep?rich-slow-solo · 1 on its host (context, not verdict) ◐evidence ↓

● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →

History observed

Every probe we made, oldest → newest (7 shown, 2026-08-12 → 2026-09-13). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (2 events)

date	type	what changed
2026-09-13	outcome	ok_tools (was auth_required)
2026-08-12	outcome	first probe: auth_required

What kind of tools these are derived

Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from tool names/descriptions/annotations WE OBSERVED. What checking applies to each kind (the full methodology →):

nature	tools	meaning	what checking applies
retrieval-public	33	serves public facts	truth-checkable against a public source — the V-ladder applies in full
computational	1	deterministic transforms	self-checkable by re-computation and known-answer tests
unclassified	1	not classifiable from its text	Tier-1 only until its tools describe themselves

Tools last seen observed

book_health consolidation_landscape consolidator_scorecard coverage_calibration customer_faithfulness definitions dossier email_security feedback fetch group_movement header_adoption hosting_momentum independent_operators integration_depth layer_stickiness market_concentration market_digitization market_pricing market_structure migration_flows operator_profile ownership_evidence peer_compare pricing_moves pricing_profile provenance saas_adoption saas_diversification search search_visibility stack_profile technology_adoption tld_pricing vendor_adoption

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band B — usable, with rough edges.

legibility check	tools passing	ok
name is clear & specific	35/35	✓
has a description	35/35	✓
description is substantive	35/35	✓
parameters are typed	35/35	✓
parameters are described	3/35	3/35

35 of 35 tools graded · 35 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not yet confirmed — 2 attempt(s) currently unverifiable (rate limits, walls, or unmappable schemas — never counted against the server) · 0 disagreements.

claim class	key	verdict	primary source
tariff-duty	0901.21.00	unverifiable	us-hts
tariff-duty	6109.10.00	unverifiable	us-hts

Protocol conformance observed

2025-06-18

protocol version

—

session model

770ccf1e

server version hostingbrain-intelligence

Capabilities: experimental prompts resources tasks tools

Drift observed

No confirmed drift on record. Baseline set 2026-09-13; changes appear here after human review.

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-09-13T06:11:57Z	ok_tools	200	407	2025-06-18
2026-09-06T06:11:26Z	auth_required	401	357
2026-08-30T06:11:18Z	auth_required	401	427
2026-08-23T06:11:15Z	auth_required	401	413
2026-08-16T06:11:08Z	auth_required	401	398
2026-08-14T19:57:36Z	auth_required	401	400
2026-08-12T05:32:53Z	auth_required	401	333

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/ai.hostingbrain/intelligence.svg)](https://robinsaige.com/s/ai.hostingbrain/intelligence)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview

Operator of this server? Everything we hold about it is on this page — free, no account, for anyone. Wrong attribution, stale probe, misclassification? Dispute this record →