# Lodging Decision (remote · di-001-a-lodging-decision-mcp.scenicstay.workers.dev)

Agent-facing lodging decision tool. Non-sensitive categories only. Alpha, unauthenticated.

- Trust score: 70/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `di-001-a-lodging-decision-mcp.scenicstay.workers.dev`: 70/100 (this document), [markdown](https://verifymcp.io/servers/scenicstay-lodging-decision-mcp/di-001-a-lodging-decision-mcp.md), [page](https://verifymcp.io/servers/scenicstay-lodging-decision-mcp/di-001-a-lodging-decision-mcp)

## Channel facts

- Endpoint: `https://di-001-a-lodging-decision-mcp.scenicstay.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0-alpha`

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

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 192 tokens (~192/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Lodging Decision MCP server?

Lodging Decision is a hosted endpoint at https://di-001-a-lodging-decision-mcp.scenicstay.workers.dev/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 scenicstay-lodging-decision-mcp 'https://di-001-a-lodging-decision-mcp.scenicstay.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "scenicstay-lodging-decision-mcp": {
      "url": "https://di-001-a-lodging-decision-mcp.scenicstay.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "scenicstay-lodging-decision-mcp": {
      "type": "http",
      "url": "https://di-001-a-lodging-decision-mcp.scenicstay.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.scenicstay-lodging-decision-mcp]
url = "https://di-001-a-lodging-decision-mcp.scenicstay.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "scenicstay-lodging-decision-mcp": {
      "type": "remote",
      "url": "https://di-001-a-lodging-decision-mcp.scenicstay.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add scenicstay-lodging-decision-mcp --url 'https://di-001-a-lodging-decision-mcp.scenicstay.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  scenicstay-lodging-decision-mcp:
    url: "https://di-001-a-lodging-decision-mcp.scenicstay.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "scenicstay-lodging-decision-mcp": {
      "Transport": "http",
      "Url": "https://di-001-a-lodging-decision-mcp.scenicstay.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add scenicstay-lodging-decision-mcp -t streamable-http -u 'https://di-001-a-lodging-decision-mcp.scenicstay.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "scenicstay-lodging-decision-mcp": {
      "type": "http",
      "url": "https://di-001-a-lodging-decision-mcp.scenicstay.workers.dev/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-09-28 (score 70, 0)

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

### 2026-09-25 (score 70, 0)

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

### 2026-09-15 (score 70, 0)

- [security] Stability: 0.97 → pass

### 2026-09-14 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 68, +9)

- [security improvement] Judged manipulation: unverified → pass
- [functional improvement] Schema quality: unverified → good

### 2026-09-10 (score 59, −7)

- [security regression] Judged manipulation: pass → unverified
- [security] Tool “lodging_decision” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: good → unverified
- [functional improvement] Schema quality: fail → pass

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

## MCP tools (1)

### `lodging_decision` (~192 tokens)

Lodging Decision

Ranks caller-supplied lodging candidates for a traveler/trip and returns a
deterministic, evidence-backed recommendation with score breakdown, tradeoffs, risk flags, missing
information, and confidence.

SCOPE: Evaluates budget, location, amenities, workspace ergonomics, acoustic isolation, price sanity vs
submarket baselines, keyless access friction, and Safety & Belonging (host review sentiment, privacy/surveillance
boundary verification, neighborhood night security, and verified inclusive badges). Does not infer or profile
demographics on travelers.

This tool does not search inventory (you must supply candidate_listings), does not book or transact, and
does not persist any data. It is deterministic given identical input. Always re-verify availability, price, and policy before booking.

Input parameters:

- `candidate_listings` (array, required)
- `traveler` (object, required)
- `trip` (object, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/scenicstay-lodging-decision-mcp/di-001-a-lodging-decision-mcp#diagnostics

## Score history

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

## Common questions

### What is the Lodging Decision MCP server?

Lodging Decision is an MCP server listed in the public MCP registry as io.github.scenicstay/lodging-decision-mcp. Agent-facing lodging decision tool. Non-sensitive categories only. Alpha, unauthenticated. This page covers its hosted endpoint (https://di-001-a-lodging-decision-mcp.scenicstay.workers.dev/mcp).

### Is the Lodging Decision MCP server safe to use?

Lodging Decision 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 Lodging Decision MCP server expose?

Lodging Decision exposes 1 tool: lodging_decision. Their descriptions and schemas cost roughly 192 tokens of context every time the server is loaded.

### Does the Lodging Decision MCP server require authentication?

No. We connected to Lodging Decision without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Lodging Decision MCP server still maintained?

Lodging Decision is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://di-001-a-lodging-decision-mcp.scenicstay.workers.dev/mcp
- Repository: https://github.com/Scenic-Stay/lodging-decision-mcp
- Changelog RSS feed: https://verifymcp.io/servers/scenicstay-lodging-decision-mcp/di-001-a-lodging-decision-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/scenicstay-lodging-decision-mcp/di-001-a-lodging-decision-mcp.json
- HTML version of this page: https://verifymcp.io/servers/scenicstay-lodging-decision-mcp/di-001-a-lodging-decision-mcp