LodgeDeck
REMOTE · LODGEDECK.VERCEL.APP
STR legality, permits and lodging tax by city, each field cited to its source jurisdiction.
Available components
Last scanned (4 hours ago)
Scores higher than 10% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 the endpoint returned HTTP 404. 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.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- 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 5 Nov 2026 · Probed https://lodgedeck.vercel.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | RSA 2048 | SHA256-RSA | 9c5f0e6a35c955e113044c86848e4cd5 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of lodgedeck.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | absent | 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 |
|---|---|
| HTTP status | 404 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lodgedeck.vercel.app/api/mcp | HTTP error | 404 | |
| http (plaintext) | http://lodgedeck.vercel.app/api/mcp | HTTPS enforced | 308 | https://lodgedeck.vercel.app/api/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_str_eligibility ~117
Deterministic verdict on whether a short-term rental is allowed in a jurisdiction for a given use type, with the requirements, cautions, a confidence and the citations behind them. No model: same input always gives the same answer, and when the governing rules are unknown it says so rather than guessing. Free, no API key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | Jurisdiction slug or "City, ST" string. |
| use_type | string | yes | primary_residence | whole_home | adu | unhosted. |
No output schema declared.
No examples provided.
get_lodging_tax ~102
Return the lodging / occupancy tax for one jurisdiction: state rate, local transient occupancy tax, the combined rate a guest pays, whether the cleaning fee is taxable, and whether the marketplace collects and remits. Every field is { value, source, confidence }; unconfirmed fields are null. Free, no API key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | Jurisdiction slug (e.g. san-diego-ca) or a "City, ST" string. |
No output schema declared.
No examples provided.
get_str_rules ~110
Return the short-term rental rules for one jurisdiction: whether a licence is required, primary-residence rule, annual night cap, zoning restriction, listing-number display rule, registration URL and enforcement notes. Every field is an object { value, source, confidence }; an unconfirmed field is value:null with confidence:"unverified", never guessed. Free, no API key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | Jurisdiction slug (e.g. austin-tx) or a "City, ST" string. |
No output schema declared.
No examples provided.
list_jurisdictions ~90
List every US short-term-rental jurisdiction LodgeDeck covers, with its slug, city, state and a coverage count of how many rule and tax fields are confirmed. Call this first to learn which slugs the other tools accept. Optional q filters by city or state name. Free, no API key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | – | Optional case-insensitive filter over city and state name. |
No output schema declared.
No examples provided.
How do I install the LodgeDeck MCP server?
LodgeDeck is a hosted endpoint at https://lodgedeck.vercel.app/api/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 · lodgedeck.vercel.app
claude mcp add --transport http maxbeech-lodgedeck 'https://lodgedeck.vercel.app/api/mcp'
What is the LodgeDeck MCP server?
LodgeDeck is an MCP server listed in the public MCP registry as io.github.maxbeech/lodgedeck. STR legality, permits and lodging tax by city, each field cited to its source jurisdiction. This page covers its hosted endpoint (https://lodgedeck.vercel.app/api/mcp).
Is the LodgeDeck MCP server safe to use?
LodgeDeck scores 25 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 LodgeDeck MCP server expose?
LodgeDeck exposes 4 tools: list_jurisdictions, get_str_rules, get_lodging_tax, check_str_eligibility. Their descriptions and schemas cost roughly 419 tokens of context every time the server is loaded.
Does the LodgeDeck MCP server require authentication?
Its publisher declares no required credentials for LodgeDeck. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the LodgeDeck MCP server still maintained?
LodgeDeck is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.