Novasol

What the Novasol connector does

The Novasol MCP server brings European holiday-home search into Claude, ChatGPT and other MCP clients. One tool, search-properties, looks across Novasol's self-catering rental catalogue by destination, dates, guests, budget and amenities, and returns matching homes with prices, review scores, bedroom counts and pet policies. Nothing here books a property, takes a payment or holds a reservation.

Novasol tools (1)

• search-properties

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

• Nothing books, pays or holds a property. Novasol's listing excludes "any booking or payment action" in its own words. Booking, deposits, instalments, cancellations and date changes all happen on Novasol's website through checkout and its MyBooking area. An agent that presents a search result as a reservation is over-reading it.
• We read no tool schema, so the parameter list on this page is prose, not a contract. The endpoint refused every anonymous request, so we never saw search-properties' inputSchema. Which of destination, dates, occupancy, budget, bedrooms, property type and amenities are named parameters — and what formats they take — is undocumented anywhere we could reach.
• We read no safety annotations, so the read-only claim is attributed, not observed. The tool name and Novasol's own exclusion of booking both point one way, and we state it as Novasol's claim. We did not read readOnlyHint or destructiveHint from the server, so this is not our observation of the schema.
• The directory's authless flag is unconfirmed rather than contradicted. Anthropic records is_authless true and auth_posture no_auth; the endpoint returned HTTP 403 to every anonymous request we made. The refusal is route-aware and reaches the application — robots.txt returns 200, invented paths return 404, and malformed JSON returns a 400 parse error — so it is not a bot wall. But it carries no WWW-Authenticate header and does not change when credentials are supplied, so it is not an auth challenge either. We can say the endpoint declined us; we cannot say why.
• No RFC 9728 descriptor exists to consult. The bare .well-known/oauth-protected-resource path returns the same blanket 403 as the host root, and every path beneath it returns a router 404. So no scope names read or write access, no consent screen can display one, and no token could be audited for one afterwards.
• The nominated documentation URL is a playground, not a document. It carries roughly eight words, is generated by Alpic rather than written by Novasol, and yields no prerequisites, no troubleshooting, no tool reference and no limits. mcp.novasol.com publishes no llms.txt and no .well-known/mcp.json, and its robots.txt is a blanket Disallow: /.
• The two published property counts disagree by roughly 8,000 homes. Novasol says 50,000; Awaze says over 42,000 for the same brand, both retrieved 2026-09-09. Neither document acknowledges the other and we found no reconciliation. The 18-country figure is consistent across Novasol's site and Anthropic's listing.
• Coverage is self-catering rentals in 18 European countries and nothing else. Novasol's listing rules out hotels, flights, car hire, package holidays, short-term urban city apartments and aggregate price statistics. A destination outside those 18 countries is out of scope, not merely unavailable.
• Data freshness is undefined. Anthropic's listing describes "real time availability and pricing", but no document states a refresh interval, cache window or staleness bound. Prices and availability should be confirmed at Novasol's checkout before being relied on.
• Pet rules are per property and narrower than most travellers expect. Novasol's FAQ states only dogs are permitted, with capacity shown per property. Other animals are not covered.
• Support routes to the platform, not the travel brand. Anthropic's listing gives support@alpic.ai as the support contact, so connector problems go to Alpic while booking problems go to Novasol's customer services. Nothing in the listing explains that split to a user.
• No rate limit, quota or fair-use policy is published for this connector by Novasol, by Alpic in the listing, or by Anthropic. Absence of a published limit is not absence of a limit.

Frequently asked questions

Sources

• Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-09-08. Source of the tool name search-properties, partner tier, is_authless true, auth_posture no_auth, has_mcp_app true, works_with claude / claude-api / claude-code / claude-desktop, zero prompt_names, the Alpic author and support@alpic.ai contact, the streamable-http transport, the endpoint, the "18 European countries" figure, the "real time availability and pricing" permissions string, the search-only scope statement and the booking/payment exclusion. Entry added 2026-06-24. · retrieved 2026-09-08
• Live posture check (2026-09-09): anonymous initialize requests to https://mcp.novasol.com/mcp returned HTTP 403 with a 40-byte JSON body {"message":"Forbidden","statusCode":403} on three separate attempts, with no WWW-Authenticate header. Controls on the same host: GET /robots.txt returned 200 (26 bytes, Disallow: /); POST and GET /totally-fake-path-xyz, /api/mcp, /message, /messages, /v1/mcp and /sse each returned 404 with a route-specific "Cannot POST/GET" body; POST /mcp with a malformed body returned 400 with a Node JSON parse error, showing the body is parsed before the refusal; /try returned 405. The 403 body was byte-identical (SHA-1 prefix fc0d2bda0062) across /mcp, /mcp/, the host root, /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server, and was unchanged by Authorization: Bearer invalidtoken123, Origin: https://claude.ai, Origin: https://mcp.novasol.com, a Referer, Sec-Fetch-Site and an x-api-key header. OPTIONS /mcp returned 204 with permissive CORS. No tool schema, annotation or parameter was read. · retrieved 2026-09-09
• RFC 9728 descriptor control (2026-09-09): /.well-known/oauth-protected-resource returned the blanket 403, while /.well-known/oauth-protected-resource/mcp, /mcpx and /totally-not-real-xyz each returned a router 404. Because paths beneath the descriptor 404 rather than 403, the bare path's 403 is the catch-all handler and not an auth declaration. /.well-known/mcp.json and /llms.txt on the same host returned 404. · retrieved 2026-09-09
• DNS checks (2026-09-09): mcp-write.novasol.com, mcp.awaze.com, chatgpt-app.novasol.com and claude.novasol.com return no A record; api.novasol.com resolves. No alternative connector hostname was found, so the listed endpoint is the only one. · retrieved 2026-09-09
• Novasol connector documentation URL, published by Anthropic's directory (retrieved 2026-09-09, HTTP 200, 17,563 bytes of markup, roughly eight words of visible copy). Titled "MCP Server Playground | Try This MCP Server"; its metadata names Alpic as author, creator, publisher and generator. Contained no prerequisites, no tool reference, no troubleshooting, no limits and no rate limits. Fetched as the exact page Anthropic's directory nominates for this connector, notwithstanding the host's blanket robots.txt disallow. · retrieved 2026-09-09
• https://mcp.novasol.com/robots.txt (retrieved 2026-09-09, HTTP 200) — User-agent: * / Disallow: /, with no Content-Signal directive. Only the directory-nominated page above was fetched on this host; no siblings were crawled. · retrieved 2026-09-09
• Novasol website (retrieved 2026-09-09, HTTP 200, ~1,594 words). Source of the "50,000 vacation homes in 18 countries" claim, the named country list, the 1968 founding date, the "more than 55 years of experience" phrasing and the "part of the Awaze Group" statement. Contains no mention of MCP, the connector or any tool name. · retrieved 2026-09-09
• https://www.novasol.com/robots.txt (retrieved 2026-09-09, HTTP 200 with a browser user agent) — a standard Drupal robots.txt allowing general crawling and disallowing only admin, user and search paths. No Content-Signal directive. The pages cited below are permitted. A default curl user agent receives a CloudFront 403 on this host, which is client-based bot blocking rather than a policy signal. · retrieved 2026-09-09
• Novasol customer FAQ (retrieved 2026-09-09, HTTP 200). Source of the checkout payment methods, the security deposit variability, the instalment behaviour, the cancellation and date-change routes through MyBooking, the dogs-only pet rule with its paw-symbol notation, and an independent reference to "the Awaze group". · retrieved 2026-09-09
• Novasol rental terms index (retrieved 2026-09-09, HTTP 200). Yielded no usable text: the page links to per-year PDF documents rather than publishing terms inline, so no booking-formation, agency or cancellation clause is cited on this page. · retrieved 2026-09-09
• Novasol privacy policy (retrieved 2026-09-09, HTTP 200, 54,075 bytes), the privacy URL Anthropic's directory records for this connector. Served with Awaze logo and favicon assets and referring to "the Awaze family", corroborating the ownership relationship. · retrieved 2026-09-09
• Novasol sitemap index (retrieved 2026-09-09, HTTP 200). Used to locate the FAQ and corporate pages by real slug rather than guessing; names eleven child sitemaps including property, destination and corporate sets. · retrieved 2026-09-09
• Awaze (retrieved 2026-09-09). Source of the "over 42,000 European homes" figure for Novasol, the "Europe's largest provider of holiday rentals" and "over 105,000 holiday properties across our brands" claims, and the brand list naming Novasol alongside cottages.com, Hoseasons, James Villas and Ardennes Etapes. · retrieved 2026-09-09
• https://alpic.ai/robots.txt (retrieved 2026-09-09, HTTP 200) — allows all user agents and explicitly welcomes GPTBot, ClaudeBot, PerplexityBot, GoogleOther and anthropic-ai. Recorded because Alpic is the connector's author of record. · retrieved 2026-09-09