CoHostBnB
REMOTE · COHOSTBNB.XYZ
Guest replies, housekeeping and handovers in one workspace for hosts and small hotels, with optional
Available components
Last scanned (19 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 21 Nov 2026.
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 350 tokens (~58/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (17% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +44
- HSTS header: pass → fail ▼ security
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.30 ▲ functional
- 17 Nov 26 −43
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.20 → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: fail → pass ▲ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 16 Nov 26 −5
- Authorization: pass → partial ▼ security
- Tool coverage: 50% → 17% ▼ functional
- Schema quality: 68 → 58 ▲ functional
- New tool “get_checkout_link” functional
- New tool “get_company_info” functional
- New tool “list_pricing” functional
- New tool “search_site” functional
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 10 Nov 26 71
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://cohostbnb.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cohostbnb.xyz | CN=WE1,O=Google Trust Services,C=US | 19 Oct 2026 | 17 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 41156bee29eddfe41385285245e73c61 |
| SANs: cohostbnb.xyz | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of cohostbnb.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | DS published | 3599, 18130 | 8, 8 | Verified |
| cohostbnb.xyz. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cohostbnb.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://cohostbnb.xyz/mcp | HTTPS enforced | 301 | https://cohostbnb.xyz/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_state_availability ~69
Return the exact public state-rules response: GREEN/YELLOW/RED/UNKNOWN, managed_allowed, verification, missing requirements, fees and disclosures. State verification is required before ordering; this lookup cannot verify it.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| state | string | yes | – |
No output schema declared.
No examples provided.
get_checkout_link ~110
Return a Stripe Checkout URL for plan=host or autopilot (interval month or year). For plan=remote or full (apply-first, state availability is confirmed before any setup fee) returns the application URL. Never charges anything; the link opens an unpaid session that expires in 31 minutes. Falls back to the pricing page.
| Name | Type | Req | Description |
|---|---|---|---|
| interval | string | – | – |
| plan | string | – | – |
| utm_campaign | string | – | – |
| utm_source | string | – | – |
No output schema declared.
No examples provided.
get_company_info ~35
What CoHostBnB sells, who runs it, and every agent entry point (llms.txt, OpenAPI, MCP).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_public_guide ~28
Read /v1/public-api/guide verbatim; does not grant tenant API access.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_pricing ~31
Every plan with its USD price and buy link; identical to https://cohostbnb.xyz/pricing.json.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_site ~38
Find CoHostBnB pages by keyword; returns url, title and description.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
How do I install the CoHostBnB MCP server?
CoHostBnB is a hosted endpoint at https://cohostbnb.xyz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · cohostbnb.xyz
claude mcp add --transport http xyz-cohostbnb-cohostbnb 'https://cohostbnb.xyz/mcp'
What is the CoHostBnB MCP server?
CoHostBnB is an MCP server listed in the public MCP registry as xyz.cohostbnb/cohostbnb. Guest replies, housekeeping and handovers in one workspace for hosts and small hotels, with optional. This page covers its hosted endpoint (https://cohostbnb.xyz/mcp).
Is the CoHostBnB MCP server safe to use?
CoHostBnB scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CoHostBnB MCP server expose?
CoHostBnB exposes 6 tools: check_state_availability, get_public_guide, get_company_info, list_pricing, search_site, get_checkout_link. Their descriptions and schemas cost roughly 311 tokens of context every time the server is loaded.
Does the CoHostBnB MCP server require authentication?
No. We connected to CoHostBnB without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CoHostBnB MCP server still maintained?
CoHostBnB is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the CoHostBnB MCP server?
VerifyMCP ran 13 checks on CoHostBnB, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.