Spann

Protocol discovery surface

Spann Stays · support

Connection and release support.

Email hello@spannhq.com. Never include traveler data, request bodies, session IDs, credentials, or secrets.

Include only operational metadata.

  • UTC time and endpoint hostname.
  • HTTP status and the X-Request-Id response header.
  • Client name and whether this was a new connection or reconnect.

Connection checklist

  • Use the /mcp endpoint with Streamable HTTP.
  • Advertise protocol version 2025-06-18.
  • Accept both application/json and text/event-stream.
  • Initialize first, then send the returned session ID and protocol-version header.
  • Reconnect after an invalid or expired session. Respect Retry-After after a 429 response.

Security and privacy reports should use the same mailbox with the subject “Private: Spann Stays security” and must not include live credentials or personal data.

Back to Spann Stays
Spann Stays MCP Support