io.github.Waysway-app/waysway
REMOTE · API.WAYSWAY.COM · SCANNED SEP 20
Waysway AI travel MCP for hotels, live prices, restaurants, flights, and activities.
Available components
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 20 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1959 tokens (~97/item across 20 items; 20 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 Coverage71
- 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 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
How do I install the io.github.Waysway-app/waysway MCP server?
io.github.Waysway-app/waysway is a hosted endpoint at https://api.waysway.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 · api.waysway.com
claude mcp add --transport http waysway-app-waysway 'https://api.waysway.com/mcp'
{
"mcpServers": {
"waysway-app-waysway": {
"url": "https://api.waysway.com/mcp"
}
}
} {
"servers": {
"waysway-app-waysway": {
"type": "http",
"url": "https://api.waysway.com/mcp"
}
}
} [mcp_servers.waysway-app-waysway] url = "https://api.waysway.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"waysway-app-waysway": {
"type": "remote",
"url": "https://api.waysway.com/mcp",
"enabled": true
}
}
} openclaw mcp add waysway-app-waysway --url 'https://api.waysway.com/mcp' --transport streamable-http
mcp_servers:
waysway-app-waysway:
url: "https://api.waysway.com/mcp" {
"McpServers": {
"waysway-app-waysway": {
"Transport": "http",
"Url": "https://api.waysway.com/mcp"
}
}
} assistant mcp add waysway-app-waysway -t streamable-http -u 'https://api.waysway.com/mcp'
{
"mcpServers": {
"waysway-app-waysway": {
"type": "http",
"url": "https://api.waysway.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 16 Sept 26 +14
- HSTS header: unverified → fail ▼ security
- HTTPS: pass → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 20 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 15 Sept 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 13 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: fail → pass ▲ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 10 Sept 26 0
- HSTS header: unverified → fail ▼ security
- HTTPS: pass → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 20 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 9 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: fail → pass ▲ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 4 Sept 26 0
- HTTPS: pass → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 20 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 3 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the 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 +1
- 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 20 Sept 2026 · Probed https://api.waysway.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.waysway.com | CN=Encryption Everywhere DV TLS CA - G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 22 Jul 2026 | 19 Oct 2026 | RSA 2048 | SHA256-RSA | 1978be2ce806c17e1d2973beb95e348 |
| SANs: api.waysway.com, www.api.waysway.com | ||||||
| CN=Encryption Everywhere DV TLS CA - G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 27 Nov 2017 | 27 Nov 2027 | RSA 2048 | SHA256-RSA | de0ffb5ee62cb61109f608c9ced5ed3 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.waysway.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| waysway.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.waysway.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.waysway.com/mcp | Served over HTTP | 200 |
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_stay_price ~61
Check live stay price for a previously recommended hotel. REQUIREMENT: - update_stay_dates must already have been called
| Name | Type | Req | Description |
|---|---|---|---|
| hotel_code_or_name | – | – | – |
| hotel_index | – | – | – |
| session_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
clear_session ~24
Clear the entire session.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
extract_user_profile_from_text ~79
Lightweight fallback extraction from raw text. This is mainly for debugging and fallback use. It is NOT the preferred production path. Preferred production path: - external model understands raw text - external model outputs standard UserProfile fields - call update_user_profile_from_model(...)
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_booking_offers ~84
Get available hotel offers for the current session dates. REQUIREMENT: - update_stay_dates should already be set - hotel should come from previous search results
| Name | Type | Req | Description |
|---|---|---|---|
| hotel_code_or_name | – | – | – |
| hotel_index | – | – | – |
| limit | integer | – | – |
| preferred_room_name | – | – | – |
| session_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_hotel_details ~59
Get detailed information for a hotel. Use this after search_hotels when the user asks for more details about a recommended option.
| Name | Type | Req | Description |
|---|---|---|---|
| hotel_code_or_name | string | yes | – |
| session_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_session_state ~30
Get a compact summary of the current session state.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_user_profile_schema ~98
Return the strict standard schema for user_profile. IMPORTANT: - Only these standard UserProfile fields are allowed. - No alias mapping is supported. - city is NOT a profile field. - checkin_date / checkout_date are NOT profile fields. - Numeric budget constraints usually belong to search_hotels price_min/price_max. Use this tool when the external model is unsure what fields are allowed.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
health_check ~18
Health check for the MCP server.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
ingest_user_message ~147
Store raw user message into session context. IMPORTANT: This tool is no longer the main profile extraction path. RECOMMENDED USE: - store raw user text for context - let the external model decide profile fields - then call update_user_profile_from_model(...) DEFAULT BEHAVIOR: - append raw text into user_info - do not aggressively infer profile fields OPTIONAL: - if use_fallback_extraction=True, run a lightweight fallback extractor
| Name | Type | Req | Description |
|---|---|---|---|
| merge | boolean | – | – |
| message | string | yes | – |
| session_id | string | yes | – |
| use_fallback_extraction | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_sessions ~24
List all in-memory session summaries. Useful for debugging only.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
normalize_stay_dates ~67
Parse stay dates without using session state. user_profile here is optional and only accepts standard profile fields. city is not required here.
| Name | Type | Req | Description |
|---|---|---|---|
| checkin_str | string | yes | – |
| checkout_str | – | – | – |
| nights | – | – | – |
| user_profile | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_activities_in_city ~54
Search activities in a city. If city is omitted, use session.city from prior hotel search.
| Name | Type | Req | Description |
|---|---|---|---|
| city | – | – | – |
| limit | integer | – | – |
| session_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_flight_content ~39
Search airline-related content.
| Name | Type | Req | Description |
|---|---|---|---|
| airline_tag | – | – | – |
| limit | integer | – | – |
| session_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_homestays_in_city ~58
Search homestays in a city. If city is omitted, use session.city from prior hotel search.
| Name | Type | Req | Description |
|---|---|---|---|
| city | – | – | – |
| limit | integer | – | – |
| session_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_hotels ~273
Search and recommend hotels. USE THIS TOOL FOR: - city-based hotel search - main search intent - direct numeric search constraints such as price_min / price_max - explicit room or amenity filters IMPORTANT: - city MUST be passed here, not inside user_profile - user_profile is for stable preferences, not for search location - if dates are known, call update_stay_dates first - if profile preferences are known, call update_user_profile_from_model first RECOMMENDED ORDER: 1. start_session 2. update_user_profile_from_model (optional) 3. update_stay_dates (optional) 4. search_hotels(city=..., ...)
| Name | Type | Req | Description |
|---|---|---|---|
| amenities | – | – | – |
| city | string | yes | – |
| exclude_hotel_codes | – | – | – |
| hotel_class_stars | – | – | – |
| limit | integer | – | – |
| main_interest | string | yes | – |
| non_refundable | – | – | – |
| price_max | – | – | – |
| price_min | – | – | – |
| rating_min | – | – | – |
| required_name_terms | – | – | – |
| room_type | – | – | – |
| session_id | string | yes | – |
| suitable | – | – | – |
| surroundings | – | – | – |
| user_specific | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_restaurants_near_hotel ~56
Search restaurants near a hotel.
| Name | Type | Req | Description |
|---|---|---|---|
| hotel_code_or_name | – | – | – |
| hotel_index | – | – | – |
| hotel_lat | – | – | – |
| hotel_lon | – | – | – |
| session_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
start_session ~292
Create or replace a session. PURPOSE: - Initialize conversation state - Optionally store stable user profile fields DO: - pass stable or semi-stable profile information in user_profile - pass preferred_language if known - call this before other hotel-related tools DO NOT: - do NOT put city inside user_profile - do NOT put checkin_date or checkout_date inside user_profile - do NOT put search filters inside user_profile CORRECT WORKFLOW: 1. start_session(...) 2. update_user_profile_from_model(...) # optional 3. update_stay_dates(...) # optional 4. search_hotels(city=..., ...) WRONG: user_profile = { "city": "New York", "checkin_date": "2023-04-01", "checkout_date": "2023-04-05" } RIGHT: start_session(user_profile={"preferred_language": "en"}) update_stay_dates(checkin_str="2023-04-01", checkout_str="2023-04-05") search_hotels(city="New York", ...)
| Name | Type | Req | Description |
|---|---|---|---|
| metadata | – | – | – |
| preferred_language | string | – | – |
| session_id | string | yes | – |
| user_id | – | – | – |
| user_profile | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
update_stay_dates ~99
Update session stay dates. USE THIS TOOL FOR: - check-in date - check-out date - nights-based date calculation DO NOT: - do NOT put dates inside user_profile - do NOT try to pass dates through start_session user_profile
| Name | Type | Req | Description |
|---|---|---|---|
| checkin_str | string | yes | – |
| checkout_str | – | – | – |
| nights | – | – | – |
| session_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
update_user_profile ~138
Update session.user_profile using standard UserProfile fields only. USE THIS WHEN: - the caller already has structured profile fields DO NOT PUT HERE: - city - checkin_date - checkout_date - raw numeric search constraints that belong in search_hotels Preferred profile fields include: - price_range - budget_flexibility - relationships - travel_purpose - hotel_style - facilities_like - surroundings_like
| Name | Type | Req | Description |
|---|---|---|---|
| merge | boolean | – | – |
| session_id | string | yes | – |
| user_profile | object | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
update_user_profile_from_model ~259
Preferred path for profile extraction. The external model should: - read the user's natural language message - decide which STANDARD UserProfile fields are supported by evidence - send ONLY those fields here HARD RULES: - only standard UserProfile fields are allowed - do NOT invent new fields - do NOT put city here - do NOT put checkin_date or checkout_date here - omit uncertain fields instead of guessing - numeric budget constraints usually belong to search_hotels price_min/price_max GOOD EXAMPLE: { "relationships": "solo", "travel_purpose": "leisure", "hotel_style": "luxury", "facilities_like": "breakfast, gym", "surroundings_like": "downtown" } BAD EXAMPLE: { "city": "New York", "checkin_date": "2023-04-01", "checkout_date": "2023-04-05", "budget": 100 }
| Name | Type | Req | Description |
|---|---|---|---|
| extracted_user_profile | object | yes | – |
| merge | boolean | – | – |
| session_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the io.github.Waysway-app/waysway MCP server?
io.github.Waysway-app/waysway is an MCP server listed in the public MCP registry as io.github.Waysway-app/waysway. Waysway AI travel MCP for hotels, live prices, restaurants, flights, and activities. This page covers its hosted endpoint (https://api.waysway.com/mcp).
Is the io.github.Waysway-app/waysway MCP server safe to use?
io.github.Waysway-app/waysway scores 69 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 io.github.Waysway-app/waysway MCP server expose?
io.github.Waysway-app/waysway exposes 20 tools: get_user_profile_schema, start_session, get_session_state, clear_session, list_sessions, and 15 more. Their descriptions and schemas cost roughly 1,959 tokens of context every time the server is loaded.
Does the io.github.Waysway-app/waysway MCP server require authentication?
No. We connected to io.github.Waysway-app/waysway without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.Waysway-app/waysway MCP server still maintained?
io.github.Waysway-app/waysway is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.