Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Spann Stays

REMOTE · MCP.SPANNHQ.COM · SCANNED SEP 24

Read-only sample stays, booking constraints, and staged reservation actions for review.

Available components

0 this week 79 Trust /100
Trust breakdown (7 categories)

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 Security77
Transport & Reachability100
Schema Quality & AI Usability57
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 296 tokens (~98/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Spann Stays MCP server?

Spann Stays is a hosted endpoint at https://mcp.spannhq.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 · mcp.spannhq.com

# add to Claude Code
claude mcp add --transport http com-spannhq-stays 'https://mcp.spannhq.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-spannhq-stays": {
      "url": "https://mcp.spannhq.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-spannhq-stays": {
      "type": "http",
      "url": "https://mcp.spannhq.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-spannhq-stays]
url = "https://mcp.spannhq.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-spannhq-stays": {
      "type": "remote",
      "url": "https://mcp.spannhq.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-spannhq-stays --url 'https://mcp.spannhq.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-spannhq-stays:
    url: "https://mcp.spannhq.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-spannhq-stays": {
      "Transport": "http",
      "Url": "https://mcp.spannhq.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-spannhq-stays -t streamable-http -u 'https://mcp.spannhq.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-spannhq-stays": {
      "type": "http",
      "url": "https://mcp.spannhq.com/mcp"
    }
  }
}

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

Changelog

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.

  • 4 Sept 26 +1
    • Stability: 0.97 → pass security
  • 2 Sept 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.

  • 31 Aug 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.

  • 28 Aug 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.

  • 26 Aug 26 75
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 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
  • 6 Aug 26 0
    • Stability: unverified → 0.03 functional
  • 5 Aug 26 0
    • Authorization: unverified → partial security
    • Transport: fail → pass security
    • MCP protocol: unverified → fail functional
    • Tool coverage: unverified → 100 functional
    • First check of Tool coverage: 0 functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: fair functional
    • First check of Schema quality: pass functional
Diagnostics

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 24 Sept 2026 · Probed https://mcp.spannhq.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.spannhq.com CN=YE1,O=Let's Encrypt,C=US 3 Aug 2026 1 Nov 2026 ECDSA 256 ECDSA-SHA384 6f3918767bf8cfa9639480597d3d64a32d3
SANs: mcp.spannhq.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.spannhq.com. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
spannhq.com. present 16192 8 Verified
mcp.spannhq.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.spannhq.com/mcp Verified 200
http (plaintext) http://mcp.spannhq.com/mcp HTTPS enforced 308 https://mcp.spannhq.com/mcp
MCP tools · 3 exposed · ~236 tokens

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 →

Tool Tokens
explain_booking_constraints ~63

Explain fixture-backed booking constraints for a sample property and rate; no property authority or live policy decision is provided.

NameTypeReqDescription
languagestringyes
property_idstringyes
room_rate_idstringyes
traveler_constraintsarray

No output schema declared.

No examples provided.

prepare_reservation_action ~91

Prepare a fixture-only reservation action for review; never holds a room, books, pays, sends, or contacts a property. Use sample traveler placeholders only.

NameTypeReqDescription
confirmation_languagestring
desired_action_modestringyes
option_idstringyes
room_rate_idstringyes
special_requestsarray
traveler_packetobjectyes

No output schema declared.

No examples provided.

search_availability ~82

Search deterministic sample stay options from the Spann Stays fixture; no live inventory or property availability is queried.

NameTypeReqDescription
destinationobject
guest_countobjectyes
languagestringyes
limitinteger
property_idstring
required_constraintsarray
stayobjectyes

No output schema declared.

No examples provided.

Common questions

What is the Spann Stays MCP server?

Spann Stays is an MCP server listed in the public MCP registry as com.spannhq/stays. Read-only sample stays, booking constraints, and staged reservation actions for review. This page covers its hosted endpoint (https://mcp.spannhq.com/mcp).

Is the Spann Stays MCP server safe to use?

Spann Stays scores 79 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 Spann Stays MCP server expose?

Spann Stays exposes 3 tools: search_availability, explain_booking_constraints, prepare_reservation_action. Their descriptions and schemas cost roughly 236 tokens of context every time the server is loaded.

Does the Spann Stays MCP server require authentication?

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

Is the Spann Stays MCP server still maintained?

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