Lodging Decision
by scenicstay · remote · no sign-in to list tools · v0.1.0-alpha · published by GitHub user scenicstay
Agent-facing lodging decision tool. Non-sensitive categories only. Alpha, unauthenticated.
1 tool: 1 change things.
Scanned Oct 21, 2026
- Deletes or cancels0Claude Code: deny
- Can't be undone0Claude Code: ask
- Changes things1Claude Code: ask: see these tools
- Only reads0Claude Code: allow
No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http lodging-decision https://di-001-a-lodging-decision-mcp.scenicstay.workers.dev/mcpTools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
1 tool
Changes things 1Claude Code: ask
lodging_decisionRanks caller-supplied lodging candidates for a traveler/trip and returns a deterministic, evidence-backed recommendation with score breakdown, tradeoffs, risk flags, missing inform…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 0.1.0-alpha. Values in angle brackets are yours to fill in.
claude mcp add --transport http lodging-decision https://di-001-a-lodging-decision-mcp.scenicstay.workers.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__lodging-decision__lodging_decision"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as lodging-decision. Review it before you use it.
