Hotel Fact Graph
REMOTE · HOTELS.ISITABIZDAY.COM
Dated, cited hotel facts from hotels' own sites and official registers, Portugal and Spain.
Available components
Last scanned (13 hours ago)
Scores higher than 61% of remote servers
Unreachable for 1 day in a row. Last reached 20 Nov 2026.
Category Search and Retrieval
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (3)
- HTTPS
- DNSSEC
- Transport
Checks we could not complete (8)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
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 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 19 Nov 26 +1
- Stability: 0.97 → pass security
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 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 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://hotels.isitabizday.com/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of hotels.isitabizday.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| isitabizday.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hotels.isitabizday.com/mcp | Unreachable | ||
| http (plaintext) | http://hotels.isitabizday.com/mcp | HTTPS enforced |
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 →
get_fact_changes ~48
Observed value differences across captures for one hotel. Not confirmed policy changes. Same identifiers as get_hotel_facts.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | – |
| property_id | string | – | – |
No output schema declared.
No examples provided.
get_hotel_facts ~66
Latest cited facts for one hotel (own website or official register). Prefer property_id. A chain domain returns the property list instead of mixing hotels. Each fact has as_of, source_url, evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | – |
| property_id | string | – | – |
No output schema declared.
No examples provided.
get_public_opinions ~90
Public opinion, not a verified fact. Guest testimonials, schema.org reviews and displayed ratings from one hotel's own website, each with source_url, captured date and a verbatim excerpt (<=25 words), plus aspect tags and an aggregate. Kept separate from get_hotel_facts.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | – |
| limit | integer | – | – |
| property_id | string | – | – |
No output schema declared.
No examples provided.
search_hotels ~86
Find hotels by name, town, domain or register id (Algarve, Lisbon coast, Costa de la Luz). Use the property_id with get_hotel_facts. Facts are cited. precision is null.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | Hotel name, municipality, domain or id (2-80 chars) |
| region | string | – | – |
No output schema declared.
No examples provided.
How do I install the Hotel Fact Graph MCP server?
Hotel Fact Graph is a hosted endpoint at https://hotels.isitabizday.com/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 · hotels.isitabizday.com
claude mcp add --transport http com-isitabizday-hotel-fact-graph 'https://hotels.isitabizday.com/mcp'
What is the Hotel Fact Graph MCP server?
Hotel Fact Graph is an MCP server listed in the public MCP registry as com.isitabizday/hotel-fact-graph. Dated, cited hotel facts from hotels' own sites and official registers, Portugal and Spain. This page covers its hosted endpoint (https://hotels.isitabizday.com/mcp).
Is the Hotel Fact Graph MCP server safe to use?
Hotel Fact Graph scores 74 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 Hotel Fact Graph MCP server expose?
Hotel Fact Graph exposes 4 tools: search_hotels, get_hotel_facts, get_public_opinions, get_fact_changes. Their descriptions and schemas cost roughly 290 tokens of context every time the server is loaded.
Does the Hotel Fact Graph MCP server require authentication?
Its publisher declares no required credentials for Hotel Fact Graph. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Hotel Fact Graph MCP server still maintained?
Hotel Fact Graph is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 20 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 Hotel Fact Graph MCP server?
VerifyMCP ran 3 checks on Hotel Fact Graph, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about Hotel Fact Graph: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.