Camping Australia
REMOTE · APP.TRIP-PLANNER.COM.AU · SCANNED AUG 3
Search Australian campsites, caravan parks and free camps; weather, gear, road trips and booking.
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 →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (bk_cart_checkout). See how to fix → View diagnostics → Fail
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3713 tokens (~206/item across 18 items; 18 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 Management27
- Stability observed for 8 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · app.trip-planner.com.au
claude mcp add --transport http au-com-trip-planner-camping-australia https://app.trip-planner.com.au/api/mcp
[mcp_servers.au-com-trip-planner-camping-australia] url = "https://app.trip-planner.com.au/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"au-com-trip-planner-camping-australia": {
"type": "remote",
"url": "https://app.trip-planner.com.au/api/mcp",
"enabled": true
}
}
} openclaw mcp add au-com-trip-planner-camping-australia --url https://app.trip-planner.com.au/api/mcp --transport streamable-http
mcp_servers:
au-com-trip-planner-camping-australia:
url: "https://app.trip-planner.com.au/api/mcp" {
"mcpServers": {
"au-com-trip-planner-camping-australia": {
"type": "http",
"url": "https://app.trip-planner.com.au/api/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.
- 3 Aug 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.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 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.
- 31 Jul 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
- 30 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 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
- 26 Jul 26 62
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 3 Aug 2026 · Probed https://app.trip-planner.com.au/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.trip-planner.com.au | CN=YE2,O=Let's Encrypt,C=US | 10 Jul 2026 | 8 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5c25579493d605515a9cd1cb7159c54e036 |
| SANs: app.trip-planner.com.au | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 |
DNSSEC insecure
Validation of app.trip-planner.com.au. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| au. | present | 26642, 32902 | 8, 8 | Verified |
| com.au. | present | 14185 | 8 | Verified |
| trip-planner.com.au. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.trip-planner.com.au/api/mcp | Verified | 200 | |
| http (plaintext) | http://app.trip-planner.com.au/api/mcp | HTTPS enforced | 308 | https://app.trip-planner.com.au/api/mcp |
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.
bk_cart_add Add a stay to the booking cart ~335
Add a product to the Bookeasy booking cart, OR answer a booking question. This is SERVER-DRIVEN and stateful: - First add: omit session_key to start a new cart; pass operator_id, product_id, check_in, check_out, adults/children, and quoted_price (the price from bk_operator_availability). - The response status is 'added' (item is in the cart) OR 'question_pending' — in which case it returns ONE question and a pending_token. Ask the user EXACTLY that one question, then call bk_cart_add again with the same session_key, the pending_token, and answer={field_id, value}. Repeat until status is 'added'. Always reuse the session_key returned by the previous cart call — never invent one.
| Name | Type | Req | Description |
|---|---|---|---|
| adults | integer | — | Adults (default 2) |
| answer | object | — | Answer to the pending booking question |
| check_in | string | — | Check-in date YYYY-MM-DD |
| check_out | string | — | Check-out date YYYY-MM-DD |
| children | integer | — | Children (default 0) |
| operator_id | integer | — | Bookeasy operator id (for a new product add) |
| pending_token | string | — | Token from a prior 'question_pending' response (when answering a booking question) |
| product_id | integer | — | Product id from bk_operator_availability |
| quoted_price | number | — | The price quoted by bk_operator_availability for this product |
| session_key | string | — | Cart session key from a prior cart call. Omit on the very first add to open a new cart. |
No output schema declared.
No examples provided.
bk_cart_checkout Complete booking checkout ~218
Finalise the Bookeasy cart and get the SINGLE checkout URL the user uses to complete payment. TWO-STEP, human-in-the-loop: 1. Call WITHOUT confirm — this returns the booking summary + total price and NO payment link. Show the traveller the full summary (property, dates, guests, total) and ask them to confirm. 2. Only after they EXPLICITLY agree, call again with confirm=true to get the secure payment link. Never set confirm=true yourself without the traveller's clear yes. Payment happens on Bookeasy's page — never tell the user the booking is 'confirmed' from chat; it's pending until they pay. Only call once the cart is ready (no pending questions) and bk_cart_guest has set the lead guest. The checkout URL covers the whole cart.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | — | Set true ONLY after the traveller has seen the full summary + total and explicitly agreed. Without it, the payment link is withheld and only the summary is returned. |
| session_key | string | yes | The cart session key |
No output schema declared.
No examples provided.
bk_cart_guest Set booking guest details ~151
Attach the lead guest's contact details to the Bookeasy cart. Bookeasy requires a name and email to issue a booking. For a signed-in customer, any of first_name / surname / email you omit are prefilled from their account — so you can call this with just the session_key and confirm the prefilled details with them, or pass explicit values to override. Call once the cart has items and before bk_cart_checkout.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Guest email (booking confirmation goes here) | |
| first_name | string | yes | Guest first name |
| phone | string | — | Optional contact phone |
| session_key | string | yes | The cart session key |
| surname | string | yes | Guest surname |
No output schema declared.
No examples provided.
bk_cart_promo Apply a promo code ~96
Apply (or remove) a promo / discount code on the Bookeasy cart. Use when the user gives a promo code; call before bk_cart_checkout so the discounted total shows. Set remove=true to take a code off.
| Name | Type | Req | Description |
|---|---|---|---|
| promo_code | string | yes | The promo / discount code |
| remove | boolean | — | True to remove the code instead of applying it |
| session_key | string | yes | The cart session key |
No output schema declared.
No examples provided.
bk_operator_availability Live park availability and prices ~132
Get LIVE products, pricing and availability for a Bookeasy operator for specific dates. Returns bookable products each with a product_id, price, max_guests and an available flag. Call this (using an operator_id from bk_search_operators) before bk_cart_add.
| Name | Type | Req | Description |
|---|---|---|---|
| adults | integer | — | Number of adults (default 2) |
| check_in | string | yes | Check-in date YYYY-MM-DD |
| check_out | string | yes | Check-out date YYYY-MM-DD |
| children | integer | — | Number of children (default 0) |
| operator_id | integer | yes | Bookeasy operator id |
No output schema declared.
No examples provided.
bk_search_content Caravan park booking info ~111
Search curated tourism content (attractions, things to do, local experiences, events) via Bookeasy. Use this for 'what's on / things to do near X' style questions — this is content we do NOT have in our own directory. NOT for campsite/accommodation booking (use the other bk_ tools for that).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | Max results (default 6) |
| query | string | yes | What to search for (e.g. 'things to do near Jervis Bay') |
No output schema declared.
No examples provided.
bk_search_operators Search bookable caravan parks ~161
Find LIVE-BOOKABLE accommodation operators near a location via the Bookeasy booking platform (real-time inventory). Use this when the user wants to actually BOOK and needs live availability/pricing — this is DIFFERENT from search_campsites (our own directory). Returns operator_id values that the other bk_ tools need. Prefer this when the user says things like 'book', 'reserve', 'is it available', or asks for real prices for specific dates.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | Latitude to search around |
| limit | integer | — | Max operators (default 15, max 50) |
| longitude | number | yes | Longitude to search around |
| within_km | number | — | Search radius in km (default 30, max ~50) |
No output schema declared.
No examples provided.
find_nearest_toilets Find nearest public toilets ~217
Find the nearest PUBLIC TOILETS to a location (from the National Public Toilet Map). Use this for questions like 'where's the closest toilet to me', 'nearest public toilet', 'is there an RV dump point near here', or 'closest accessible toilet'. Returns toilets sorted by distance with name, address, distance, opening hours, facilities (wheelchair access, baby change, RV dump point, showers, drinking water, etc.) and a directions link. Provide the user's latitude/longitude. If the user says 'near me' and you already have their location from the conversation/context, pass it; otherwise ask for their location or a nearby place name.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | Latitude of the search location. |
| limit | integer | — | Max results to return (default 5, max 25). |
| longitude | number | yes | Longitude of the search location. |
| radius_km | number | — | Search radius in km (default 15). If none are within radius, the closest are returned anyway. |
No output schema declared.
No examples provided.
get_accommodation_types List accommodation types ~63
List all accommodation types offered by a specific entity (e.g. powered sites, unpowered sites, cabins, hotel rooms). Returns pricing, capacity, amenities, and vehicle access info.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | integer | yes | The entity ID to get accommodation types for |
No output schema declared.
No examples provided.
get_campervan_booking_link Campervan booking link ~165
Get the DriveAway booking deep-link to complete a campervan / motorhome hire for a pickup city and dates. The user finishes the booking on DriveAway's site (we don't take payment). Use this to hand the user a 'book now' link once they've chosen dates — no search needed. Returns a single booking_url. Australia only.
| Name | Type | Req | Description |
|---|---|---|---|
| driver_age | integer | — | Driver age (18–99). Default 35. |
| dropoff_date | string | yes | Drop-off date, YYYY-MM-DD. |
| passengers | integer | — | Number of travellers (1–8). Default 2. |
| pickup_city | string | yes | Pickup depot city, e.g. 'Brisbane'. |
| pickup_date | string | yes | Pickup date, YYYY-MM-DD. |
No output schema declared.
No examples provided.
get_campsite_details Campsite details ~62
Get full details for a specific campsite or accommodation by its ID. Returns description, all features/amenities, address, photos, rating, accommodation types offered, and booking information.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | integer | yes | The unique entity ID of the campsite |
No output schema declared.
No examples provided.
get_features List campsite features ~66
Get the full list of available features/amenities that campsites can have. Use this to help users understand what filters are available or to clarify what a feature means.
| Name | Type | Req | Description |
|---|---|---|---|
| feature_type | string | — | Filter by feature category (e.g. 'Campsite Type', 'Amenities') |
No output schema declared.
No examples provided.
get_regions List camping regions ~62
List available camping/accommodation regions, optionally filtered by state. Returns region names with entity counts. Use this when the user wants to browse by area or doesn't have a specific location.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | — | Filter regions by state (e.g. 'NSW') |
No output schema declared.
No examples provided.
get_weather_forecast Weather forecast ~209
Get a 14-day weather forecast for a campsite or location. Use this when the user asks about weather, temperature, rain, wind, or UV conditions at a campsite or destination. You can provide EITHER: - campsite_name: The name (or partial name) of a campsite to look up its GPS coordinates automatically, OR - latitude + longitude: Direct coordinates if already known Returns daily forecasts with max/min temperature, rain chance, precipitation amount, wind speed, UV index, and a weather description for each day.
| Name | Type | Req | Description |
|---|---|---|---|
| campsite_name | string | — | Name or partial name of a campsite to look up (e.g. 'Byron Bay', 'Big4 Morisset'). The tool will search Neo4j for the campsite and use its GPS coordinates. |
| latitude | number | — | Latitude of the location (e.g. -33.8688 for Sydney) |
| longitude | number | — | Longitude of the location (e.g. 151.2093 for Sydney) |
No output schema declared.
No examples provided.
recommend_gear Recommend camping gear ~99
Recommend relevant products and gear for a specific campsite based on its features and type. For example, a campsite with fishing will return fishing gear; a 4WD-access campsite will return recovery equipment. Use this when a user asks what to bring or buy for a particular campsite.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | integer | yes | The campsite entity ID to recommend gear for |
| limit | integer | — | Max products to return (default 6, max 12) |
No output schema declared.
No examples provided.
search_campervans Search campervan hire ~226
Search live campervan / motorhome hire availability and pricing for a pickup city and travel dates (via DriveAway). Use this when the user wants to RENT a campervan, motorhome or RV (NOT the same as search_campsites, which finds places to camp). Returns matching vehicles with brand, name, category, sleeps/seats, 4WD, nightly and total AUD price, and a booking_url deep-link to complete the hire. Australia only. Each result already includes full vehicle details (so there is no separate 'resolve' step) and the booking link.
| Name | Type | Req | Description |
|---|---|---|---|
| driver_age | integer | — | Driver age (18–99). Default 35. |
| dropoff_date | string | yes | Drop-off date, YYYY-MM-DD. Must be after pickup_date. |
| passengers | integer | — | Number of travellers (1–8). Default 2. |
| pickup_city | string | yes | Pickup depot city, e.g. 'Melbourne', 'Cairns', 'Perth'. |
| pickup_date | string | yes | Pickup date, YYYY-MM-DD. |
No output schema declared.
No examples provided.
search_campsites Search campsites ~1,218
Search for campsites, caravan parks, or accommodation by location, features, and other criteria. Use this when the user asks to find a place to stay, camp, or explore. Returns a list of matching entities with names, locations, ratings, features, and images. COVERAGE: Australia (default), the United States (federal, BLM, national-forest campgrounds + free camping), Canada, New Zealand, Argentina AND Chile (campgrounds + free camping). Set the 'country' parameter to 'US' for United States, 'CA' for Canada, 'NZ' for New Zealand, 'AR' for Argentina, 'CL' for Chile, 'AU' for Australia — results never mix countries. IMPORTANT — Feature filtering: When users mention specific requirements (pets, pools, toilets, etc.), you MUST pass the correct feature name(s) in the 'features' array. Only campsites that have ALL requested features will be returned. AVAILABLE FEATURE NAMES (use these exact strings): Amenities: Toilets, Showers, Hot Showers, Drinking Water, Power, WiFi Internet, Laundromat, Dump Point, Camp Kitchen Activities: Fishing Spot, Beach Fishing, Swimming, Walking, Boating, Boat Ramp, Bird Watching Accommodation: Caravans, Caravan Park, Tent Site, Campground, Cabins, Free Camping, Showground Facilities: BBQ, Fire Place, Shade, Picnic Tables, Children's Play Facility, Swimming Pool Rules: Pets Welcome, No Pets, Accessible, Camping Fee, Mobile Phone Coverage CRITICAL — Pet policy: - 'dog friendly' / 'pets allowed' / 'pet friendly' → use feature 'Pets Welcome' - NEVER recommend a campsite with 'No Pets' feature to someone wanting pets - If the user asks for pet-friendly, ALWAYS include 'Pets Welcome' in features array
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | — | Which country's campsites to search. Set 'US' for United States, 'CA' for Canada, 'NZ' for New Zealand, 'AR' for Argentina, 'CL' for Chile, 'AU' for Australia. Defaults to 'AU'. Results NEVER mix cou… |
| entity_type | string | — | Filter by listing type. Use when the user specifies what kind of place they want: - 'free_camping' — free bush camps, rest areas with overnight stays - 'caravan_park' — caravan parks with powered/unp… |
| features | array | — | REQUIRED features the campsite MUST have. Use exact feature names from the list above. e.g. ['Pet Friendly', 'Toilets', 'Swimming Pool']. All listed features must be present on a campsite for it to b… |
| limit | integer | — | Max results to return (default 6, max 20) |
| near_latitude | number | — | Latitude for proximity search. AU: -33.8688 Sydney. US: 38.5733 Moab, 37.8651 Yosemite Valley. CA: 51.1784 Banff, 49.2827 Vancouver. NZ: -45.0312 Queenstown, -38.1368 Rotorua, -43.5321 Christchurch,… |
| near_longitude | number | — | Longitude for proximity search. AU: 151.2093 Sydney. US: -109.5498 Moab, -119.5383 Yosemite Valley. CA: -115.5708 Banff, -123.1207 Vancouver. NZ: 168.6626 Queenstown, 176.2497 Rotorua, 172.6362 Chris… |
| query | string | — | Free-text search for campsite name or location (e.g. 'Byron Bay', 'Moab', 'Banff', 'Queenstown', 'Bariloche', 'Torres del Paine', 'Central Coast'). Do NOT put feature requirements here — use the 'fea… |
| radius_km | number | — | Search radius in kilometres (default 50, use 100-150 for broader search) |
| region | string | — | Region name to search within (e.g. 'South Coast', 'Blue Mountains') |
| state | string | — | AUSTRALIA ONLY — state abbreviation (e.g. 'NSW', 'VIC', 'QLD'). For US/CA/NZ searches use 'query' or near_latitude/near_longitude instead. |
No output schema declared.
No examples provided.
search_products Search camping gear store ~122
Search for camping gear, outdoor products, and accessories available in the Camping Australia store. Use this when a user asks about gear, equipment, products, or what to buy/bring.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | Max results to return (default 6, max 12) |
| product_type | string | — | Product category to filter by (e.g. 'Tents', 'Outdoor Recreation > Fishing', 'Caravan Accessories') |
| query | string | — | Free-text search query (e.g. 'fishing rod', 'tent', 'caravan accessories') |
No output schema declared.
No examples provided.