# Hotel Fact Graph (remote · hotels.isitabizday.com)

Dated, cited hotel facts from hotels' own sites and official registers, Portugal and Spain.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `hotels.isitabizday.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-isitabizday-hotel-fact-graph/hotels.md), [page](https://verifymcp.io/servers/com-isitabizday-hotel-fact-graph/hotels)

## Channel facts

- Endpoint: `https://hotels.isitabizday.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-isitabizday-hotel-fact-graph 'https://hotels.isitabizday.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-isitabizday-hotel-fact-graph": {
      "url": "https://hotels.isitabizday.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-isitabizday-hotel-fact-graph": {
      "type": "http",
      "url": "https://hotels.isitabizday.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-isitabizday-hotel-fact-graph]
url = "https://hotels.isitabizday.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-isitabizday-hotel-fact-graph": {
      "type": "remote",
      "url": "https://hotels.isitabizday.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-isitabizday-hotel-fact-graph --url 'https://hotels.isitabizday.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-isitabizday-hotel-fact-graph:
    url: "https://hotels.isitabizday.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-isitabizday-hotel-fact-graph": {
      "Transport": "http",
      "Url": "https://hotels.isitabizday.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-isitabizday-hotel-fact-graph -t streamable-http -u 'https://hotels.isitabizday.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-isitabizday-hotel-fact-graph": {
      "type": "http",
      "url": "https://hotels.isitabizday.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 74, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: pass → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-19 (score 74, +1)

- [security] Stability: 0.97 → pass

### 2026-11-17 (score 73, +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.

### 2026-11-15 (score 72, +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.

### 2026-11-12 (score 71, +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.

### 2026-11-10 (score 70, +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.

### 2026-11-08 (score 69, +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.

### 2026-11-06 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (4)

### `search_hotels` (~86 tokens)

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.

Input parameters:

- `limit` (integer)
- `query` (string, required): Hotel name, municipality, domain or id (2-80 chars)
- `region` (string)

### `get_hotel_facts` (~66 tokens)

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.

Input parameters:

- `domain` (string)
- `property_id` (string)

### `get_public_opinions` (~90 tokens)

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.

Input parameters:

- `domain` (string)
- `limit` (integer)
- `property_id` (string)

### `get_fact_changes` (~48 tokens)

Observed value differences across captures for one hotel. Not confirmed policy changes. Same identifiers as get_hotel_facts.

Input parameters:

- `domain` (string)
- `property_id` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-isitabizday-hotel-fact-graph/hotels#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 74
- 2026-11-19: 74
- 2026-11-18: 73
- 2026-11-17: 73
- 2026-11-16: 72
- 2026-11-15: 72
- 2026-11-14: 71
- 2026-11-13: 71
- 2026-11-12: 71
- 2026-11-11: 70
- 2026-11-10: 70
- 2026-11-09: 69
- 2026-11-08: 69
- 2026-11-07: 68
- 2026-11-06: 68
- 2026-11-05: 67
- 2026-11-04: 67
- 2026-11-03: 66
- 2026-11-02: 66
- 2026-11-01: 23
- 2026-10-31: 65
- 2026-10-30: 64
- 2026-10-29: 23
- 2026-10-28: 64
- 2026-10-27: 23
- 2026-10-26: 63
- 2026-10-25: 62
- 2026-10-24: 62
- 2026-10-23: 61

## Common questions

### 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.

## Links

- Remote endpoint: https://hotels.isitabizday.com/mcp
- Website: https://hotels.isitabizday.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-isitabizday-hotel-fact-graph/hotels.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-isitabizday-hotel-fact-graph/hotels/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-isitabizday-hotel-fact-graph/hotels.json
- HTML version of this page: https://verifymcp.io/servers/com-isitabizday-hotel-fact-graph/hotels
