Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Livuma — Bali rental & property search

REMOTE · LIVUMA.COM

Search Bali villas, apartments and homes for rent or sale; live availability and prices.

Available components

+3 this week 74 Trust /100

Last scanned (16 hours ago)

Scores higher than 61% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
Schema Quality & AI Usability61
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1186 tokens (~296/item across 4 items; 4 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 Management23
  • Stability observed for 7 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 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.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 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.

  • 16 Nov 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.

  • 15 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 14 Nov 26 71

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://livuma.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=livuma.com CN=WE1,O=Google Trust Services,C=US 11 Nov 2026 9 Feb 2027 ECDSA 256 ECDSA-SHA256 eca3bd38d25a25290e9389654dafa888
SANs: livuma.com, *.livuma.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of livuma.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
livuma.com. No DS 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=2592000
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://api.mapbox.com https://events.mapbox.com https://www.googletagmanager.com https://cdn.jsdelivr.net https://static.cloudflareinsights.com https://editor.unlayer.com https://assets.xendit.co https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline' https://api.mapbox.com https://editor.unlayer.com; font-src 'self' https://editor.unlayer.com https://assets.xendit.co; img-src 'self' data: blob: https://*.blob.core.windows.net https://cdn.livuma.com https://api.mapbox.com https://www.googletagmanager.com https://editor.unlayer.com https://assets.unlayer.com https:; connect-src 'self' wss: https://api.mapbox.com https://events.mapbox.com https://*.blob.core.windows.net https://www.google-analytics.com https://*.google-analytics.com https://analytics.google.com https://*.analytics.google.com https://www.googletagmanager.com https://www.google.com https://googleads.g.doubleclick.net https://stats.g.doubleclick.net https://td.doubleclick.net https
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://livuma.com/mcp Verified 200
http (plaintext) http://livuma.com/mcp HTTPS enforced 301 https://livuma.com/mcp
MCP tools · 4 exposed · ~1,186 tokens

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 →

Tool Tokens
check_availability ~253

Checks whether a listing can be booked for given dates, at which rate and for how much — the same answer the listing page gives a visitor. Returns { available, reason, recommendedRate, options, bookedRanges, bookingUrl }. Each option states whether that rate is eligible (and why not), the rate per period, the first payment and the full payment schedule. Livuma charges guests no service fee, so the amounts are what the guest pays. `bookingUrl` opens the listing on livuma.com with these dates selected; the booking itself (card authorisation, 3-D Secure, identity verification) is completed there by the guest.

NameTypeReqDescription
checkInDatestringyesCheck-in date, yyyy-MM-dd. Required.
checkOutDatestring|null–Check-out date, yyyy-MM-dd. Omit for open_ended and yearly.
listingIdstringyesThe listing's "id" from search results (GUID), a short /s/{id} id, or the listing URL.
rentalModestring|null–"dates" (default), "open_ended" (no end date, monthly) or "yearly" (fixed 12-month term).

No output schema declared.

No examples provided.

get_listing_details ~212

Returns what the public listing page shows for one listing: description, photos, all rates and minimum stays, amenities and included services, seasonal nightly pricing, published guest reviews, host verification, the booked/blocked calendar and the canonical url. With checkInDate (and checkOutDate, or a rentalMode) the response also includes a live availability quote for those dates.

NameTypeReqDescription
checkInDatestring|null–Optional check-in date, yyyy-MM-dd — adds a live quote for the stay.
checkOutDatestring|null–Optional check-out date, yyyy-MM-dd.
currencystring|null–"IDR" (default), "USD", or "EUR".
listingIdstringyesThe listing's "id" from search results (GUID). The short id from a /s/{id} link, or the listing URL itself, also work.
rentalModestring|null–"dates" (default), "open_ended" or "yearly".

No output schema declared.

No examples provided.

get_search_options ~44

Returns the valid listing-search values: property types, ownership types, common areas, currencies, rental modes and amenity names, plus notes on paging, budgets and bookability.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_listings ~677

Searches Livuma's live Bali rental and property-sale inventory with the same results, filters and prices as the livuma.com search page. Returns { items, page, pageSize, total, hasMore, filteredAfterPaging }. Each item has the canonical url, the primary photo, the price for this search (the stay total when dates are given, otherwise the per-period rate), the host's rates and minimum stays, amenities, rating, coordinates and isBookable. `total` is the number of database matches. When `filteredAfterPaging` is true, the exact per-stay price was applied after paging, so a page can hold fewer items than pageSize while `hasMore` is still true. One area is searched per request. Search results are not a booking quote: availability, the applicable rate and the exact price are confirmed only by the availability check for specific dates.

NameTypeReqDescription
amenitiesarray|null–Amenity filters, e.g. ["pool","wifi","pet_friendly"].
areastring|null–One area name, e.g. "Canggu". Free text, geocoded server-side.
areaRadiusKmnumber|null–Search radius in km around the area or the coordinates (default 10, max 20).
checkInDatestring|null–Check-in date, yyyy-MM-dd.
checkOutDatestring|null–Check-out date, yyyy-MM-dd. Omit for open_ended and yearly.
currencystring|null–"IDR" (default), "USD", or "EUR".
excludeIdsarray|null–Listing GUIDs to exclude, e.g. results already shown to the user.
includeInsightsboolean–Include AI-extracted photo and description insights. Off by default — they are large.
latitudenumber|null–Center latitude for coordinate-based location filtering (use with longitude; alternative to area).
longitudenumber|null–Center longitude for coordinate-based location filtering (use with latitude).
maxPricenumber|null–Budget in `currency`, compared against the price shown for this search: the stay TOTAL when check-in and check-out are given, otherwise the monthly rate (yearly in yearly mode) or the asking price fo…
minPricenumber|null–Minimum budget in `currency`, same unit rules as maxPrice.
minRoomsinteger|null–Minimum number of bedrooms.
offerstring|null–"rent" or "sale". Omit for both.
ownershipTypestring|null–Ownership type for sales, e.g. "Freehold". Not used for rentals.
pageinteger|null–1-based page number.
pageSizeinteger|null–Results per page, 1-100 (default 20).
propertyTypestring|null–Property type name, e.g. "Villa", "Apartment".
rentalModestring|null–How a rental stay is priced: "dates" (default — give checkInDate + checkOutDate, or neither to browse monthly rates), "open_ended" (checkInDate only, monthly rate, no end date), "yearly" (checkInDate…

No output schema declared.

No examples provided.

Install

How do I install the Livuma — Bali rental & property search MCP server?

Livuma — Bali rental & property search is a hosted endpoint at https://livuma.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 · livuma.com

# add to Claude Code
claude mcp add --transport http com-livuma-homes 'https://livuma.com/mcp'
Common questions

What is the Livuma — Bali rental & property search MCP server?

Livuma — Bali rental & property search is an MCP server listed in the public MCP registry as com.livuma/homes. Search Bali villas, apartments and homes for rent or sale; live availability and prices. This page covers its hosted endpoint (https://livuma.com/mcp).

Is the Livuma — Bali rental & property search MCP server safe to use?

Livuma — Bali rental & property search scores 74 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 Livuma — Bali rental & property search MCP server expose?

Livuma — Bali rental & property search exposes 4 tools: search_listings, check_availability, get_search_options, get_listing_details. Their descriptions and schemas cost roughly 1,186 tokens of context every time the server is loaded.

Does the Livuma — Bali rental & property search MCP server require authentication?

No. We connected to Livuma — Bali rental & property search without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Livuma — Bali rental & property search MCP server still maintained?

Livuma — Bali rental & property search is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Livuma — Bali rental & property search MCP server?

VerifyMCP ran 13 checks on Livuma — Bali rental & property search, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.