HasData Airbnb
REMOTE · MCP.HASDATA.COM · 3 COMPONENTS
Airbnb stays by location and dates, and full listing details, as structured JSON.
Available components
Last scanned (19 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 16 Oct 2026.
Category E-commerce
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 Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 522 tokens (~261/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 20. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 13. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 +41
- Injection markers: unverified → pass ▲ security
- Transport: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.03 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- 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
- 22 Sept 26 39
First indexed and scored.
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 16 Oct 2026 · Probed https://mcp.hasdata.com/mcp?apis=airbnb
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.hasdata.com | CN=YR1,O=Let's Encrypt,C=US | 20 Aug 2026 | 18 Nov 2026 | RSA 2048 | SHA256-RSA | 5cef740443d03259c4ef72de38826f9d2a3 |
| SANs: mcp.hasdata.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.hasdata.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| hasdata.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="Authorization is required: connect with OAuth or send an x-api-key header", scope="mcp:tools", resource_metadata="https://mcp.hasdata.com/.well-known/oauth-protected-resource/mcp"
Bearer error="invalid_token", error_description="Authorization is required: connect with OAuth or send an x-api-key header", scope="mcp:tools", resource_metadata="https://mcp.hasdata.com/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Protected resource metadata
| Document | https://mcp.hasdata.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.hasdata.com/mcp |
| Authorisation server | https://mcp.hasdata.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.hasdata.com/mcp?apis=airbnb | Verified | 200 | |
| http (plaintext) | http://mcp.hasdata.com/mcp?apis=airbnb | HTTPS enforced | 308 | https://mcp.hasdata.com/mcp?apis=airbnb |
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 →
hasdata_airbnb_listing_getAirbnbListings airbnb_listing: GET / ~330
Get Airbnb Listings Searches Airbnb for available stays by location or map bounding box (neLat/neLng/swLat/swLng) and date range (check-in/check-out) with guest composition (adults, children, infants, pets) and nextPageToken pagination. Returns listing id/url, title, price per night and total, rating, review count, coordinates, and photos. Use for travel planning agents, short-term rental market analysis, pricing/occupancy research, and lead lists for property management.
| Name | Type | Req | Description |
|---|---|---|---|
| adults | number | – | Number of adults. |
| checkIn | string | yes | The check-in date for the listings. |
| checkOut | string | – | The check-out date for the listings. |
| children | number | – | Number of children. |
| infants | number | – | Number of infants. |
| location | string | – | The location to search for listings. Required unless a full map bounding box (neLat, neLng, swLat, swLng) is provided. |
| neLat | number | – | North-east corner latitude of the map bounding box. When all four bounding-box coordinates are provided, listings are searched within the box instead of by location. |
| neLng | number | – | North-east corner longitude of the map bounding box. |
| nextPageToken | string | – | The token used to retrieve the next page of results. |
| pets | number | – | Number of pets. |
| swLat | number | – | South-west corner latitude of the map bounding box. |
| swLng | number | – | South-west corner longitude of the map bounding box. |
No output schema declared.
No examples provided.
hasdata_airbnb_property_getAirbnbPropertyDetails airbnb_property: GET / ~119
Get Airbnb Property Details Fetches the full Airbnb property page by listing URL. Returns title, description, location, coordinates, rating and review count, host profile, room/bed/bath counts, photos, and amenities list. Use for travel-planning agents, deep-dive rate research, photo/amenity enrichment of listings discovered via the listing-search endpoint, and LSTR compliance or market-quality audits.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL of the Airbnb listing. Must be a valid Airbnb listing URL. |
No output schema declared.
No examples provided.
How do I install the HasData Airbnb MCP server?
HasData Airbnb is a hosted endpoint at https://mcp.hasdata.com/mcp?apis=airbnb, 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.hasdata.com
claude mcp add --transport http com-hasdata-airbnb 'https://mcp.hasdata.com/mcp?apis=airbnb'
What is the HasData Airbnb MCP server?
HasData Airbnb is an MCP server listed in the public MCP registry as com.hasdata/airbnb. Airbnb stays by location and dates, and full listing details, as structured JSON. This page covers its hosted endpoint (https://mcp.hasdata.com/mcp?apis=airbnb).
Is the HasData Airbnb MCP server safe to use?
HasData Airbnb scores 84 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 HasData Airbnb MCP server expose?
HasData Airbnb exposes 2 tools: hasdata_airbnb_listing_getAirbnbListings, hasdata_airbnb_property_getAirbnbPropertyDetails. Their descriptions and schemas cost roughly 449 tokens of context every time the server is loaded.
Does the HasData Airbnb MCP server require authentication?
Yes. HasData Airbnb asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the HasData Airbnb MCP server still maintained?
HasData Airbnb is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.