Tu Lugar
REMOTE · TULUGAR.COM · SCANNED OCT 4
Search and manage Paraguay & LatAm real estate from any AI assistant.
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 Security63
- 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 connect, but we couldn't read the whole tool list to see what that exposes. View diagnostics → Unverified
- 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 Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Tu Lugar MCP server?
Tu Lugar is a hosted endpoint at https://tulugar.com/api/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 · tulugar.com
claude mcp add --transport http com-tulugar-tulugar 'https://tulugar.com/api/mcp'
{
"mcpServers": {
"com-tulugar-tulugar": {
"url": "https://tulugar.com/api/mcp"
}
}
} {
"servers": {
"com-tulugar-tulugar": {
"type": "http",
"url": "https://tulugar.com/api/mcp"
}
}
} [mcp_servers.com-tulugar-tulugar] url = "https://tulugar.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-tulugar-tulugar": {
"type": "remote",
"url": "https://tulugar.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-tulugar-tulugar --url 'https://tulugar.com/api/mcp' --transport streamable-http
mcp_servers:
com-tulugar-tulugar:
url: "https://tulugar.com/api/mcp" {
"McpServers": {
"com-tulugar-tulugar": {
"Transport": "http",
"Url": "https://tulugar.com/api/mcp"
}
}
} assistant mcp add com-tulugar-tulugar -t streamable-http -u 'https://tulugar.com/api/mcp'
{
"mcpServers": {
"com-tulugar-tulugar": {
"type": "http",
"url": "https://tulugar.com/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.
- 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
- 26 Aug 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
- 11 Aug 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
- 9 Aug 26 0
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- 8 Aug 26 0
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- 7 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.37 → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 5 Aug 26 0
- HSTS header: fail → pass ▲ security
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 6 Oct 2026 · Probed https://tulugar.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tulugar.com | CN=WE1,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 1f7df5efaa7a28b213e829cb51f5bde0 |
| SANs: tulugar.com, *.tulugar.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 tulugar.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| tulugar.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tulugar.com/api/mcp | Unreachable | ||
| http (plaintext) | http://tulugar.com/api/mcp | HTTPS enforced | 301 | https://tulugar.com/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. 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 →
account_status Account Status ~130
REPORT-ONLY status check: returns whether the user's Tu Lugar account is connected and whether they can publish (needs a verified WhatsApp number). It does NOT and CANNOT start a connection. If the user asks to connect / authorize / log in / sign in, or wants to create a listing while not connected, call `connect_account` instead — that is the tool that opens the Approve prompt. Use account_status only when you purely want to know the current state. Never tell the user to merely visit the login page to authorize Claude — connecting is a one-time Approve, not a website login.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
buy_promotional_credits Buy Promotional Credits ~104
Start a purchase of a promotional-credit pack for the connected account. Returns a secure Stripe checkout link that the USER opens to pay — you never handle card details, and payment happens on Stripe's page, not here. After they pay, the credits are added to their account and can be spent with promote_listing. One pack = 5 credits (each promotes one property for ~14 days).
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Language for the checkout page (default es) |
No output schema declared.
No examples provided.
close_listing ~114
Close (retire) one of the authenticated agent's OWN listings — use when a property is sold, rented, or withdrawn from the market. It disappears from public results. This is NOT reversible (a closed listing cannot be reopened), so confirm with the user before calling. Pass the id from my_listings. Also works on SYNCED listings (synced:true): closing one stops the portal sync from reopening it.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | ID of the agent's own listing to close (from my_listings) |
No output schema declared.
No examples provided.
closing_costs Closing Costs (Paraguay) ~128
Official TuLugar closing-costs breakdown for buying property in PARAGUAY: transfer tax, municipal fees, notary/registry, optional mortgage fixed costs, seller broker fee. Use when the user asks what buying costs beyond the price, or to budget cash-at-closing for a concrete price.
| Name | Type | Req | Description |
|---|---|---|---|
| include_mortgage_costs | boolean | – | Include bank appraisal/title/notary fixed fees (default true) |
| price_gs | number | – | Property price in guaraníes |
| price_usd | number | – | Property price in USD (use this OR price_gs) |
No output schema declared.
No examples provided.
connect_account Connect Tu Lugar Account ~174
THE tool to connect/authorize the user's Tu Lugar account. Call this IMMEDIATELY (without first calling account_status) whenever the user asks to "connect", "authorize", "link", "log in to", or "sign in to" Tu Lugar, or wants to create/manage a listing while not connected — do NOT wait for them to create a listing first. When not connected, it returns a clickable "Connect your Tu Lugar account" link — show that link to the user verbatim and tell them to open it (one click if they are already signed in at tulugar.com; no separate Approve step). After they open it they are connected — they can then ask you again. If already connected, it confirms who they are connected as. account_status only REPORTS status and can never start this.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_lead Contact Agent ~174
Send an inquiry on behalf of the user to the advertiser of a listing, a development project, or a real-estate company. Notifies them (email + WhatsApp) and starts a conversation. Works without an account. This sends a real message to real people — confirm the details with the user before calling.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | – | Company/agency to contact directly |
| string | – | Buyer email (email or phone required) | |
| listing_id | string | – | Listing to inquire about (exactly one of listing_id / project_id / company_id) |
| message | string | yes | The inquiry message |
| name | string | yes | Buyer name |
| phone | string | – | Buyer phone / WhatsApp (email or phone required) |
| project_id | string | – | Development project to inquire about |
No output schema declared.
No examples provided.
create_listing Create Listing ~418
Create a real estate listing for the authenticated agent. Always creates a private DRAFT — it is NOT visible publicly. A city or neighborhood is enough to start; NEVER invent coordinates (fabricated pins are discarded). The response returns an edit-page link with a map: ask the user to open it and drop the pin on the exact property location, and wait for their confirmation before publish_listing — publishing is blocked until a human sets the pin and at least one photo. Requires a CONNECTED account with a verified WhatsApp number — if unsure, call account_status FIRST and, if not connected, share the connect steps it returns instead of attempting to create.
| Name | Type | Req | Description |
|---|---|---|---|
| apartment_details | object | – | Bedrooms/bathrooms/area for the property. |
| commercial_details | object | – | Bedrooms/bathrooms/area for the property. |
| description | string | – | – |
| house_details | object | – | Bedrooms/bathrooms/area for the property. |
| images | array | – | Up to 25 image URLs. Optional for a draft; at least one is required to publish. |
| land_details | object | – | Bedrooms/bathrooms/area for the property. |
| listing_type | string | yes | – |
| location | object | yes | Listing location. The country/market is inferred from the city and coordinates — use real place names so it resolves correctly (e.g. Asunción → Paraguay, Montevideo → Uruguay, Buenos Aires → Argentin… |
| price_amount | number | yes | Price (positive number) |
| price_currency | string | – | Use the currency local to the market (e.g. PYG in Paraguay, UYU or USD in Uruguay, ARS in Argentina, BRL in Brazil). Defaults to PYG if omitted. |
| property_type | string | yes | – |
| source_language | string | yes | Language the title/description are written in |
No output schema declared.
No examples provided.
delete_saved_search ~41
Delete one of the connected user's saved searches by id (stops its alerts).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Saved search id (from my_saved_searches) |
No output schema declared.
No examples provided.
edit_listing Edit Listing ~215
Update one of the authenticated agent's listings. Pass only the fields to change. Editing images/title/description counts against the edit quota and re-triggers review. Also works on SYNCED listings (auto-imported from the agent's portal, marked synced:true in my_listings): everything is editable, and changing the price makes it stop auto-syncing — the agent's price then always wins over the portal's. Publish state of synced listings cannot be changed here (use close_listing).
| Name | Type | Req | Description |
|---|---|---|---|
| apartment_details | object | – | Bedrooms/bathrooms/area for the property. |
| commercial_details | object | – | Bedrooms/bathrooms/area for the property. |
| description | string | – | – |
| house_details | object | – | Bedrooms/bathrooms/area for the property. |
| id | string | yes | Listing ID to update |
| images | array | – | – |
| land_details | object | – | Bedrooms/bathrooms/area for the property. |
| price_amount | number | – | – |
| price_currency | string | – | – |
No output schema declared.
No examples provided.
fetch Fetch ~55
Retrieve the full content of a single Tu Lugar listing by its id (from a `search` result). Returns title, full text description, specs, and the canonical URL.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Listing id returned by `search`. |
No output schema declared.
No examples provided.
get_agent ~43
Get details about one real estate agent by id or slug: profile, rating, reviews, specialties, and contact info.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Agent id or slug |
No output schema declared.
No examples provided.
get_company ~51
Get details about one agency or developer by id or slug (from search_companies): profile, rating, specialties, languages, service areas, and contact info.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Company id or slug |
No output schema declared.
No examples provided.
get_guide TuLugar Guides ~111
Curated TuLugar guides (general education, kept current): buying-process (step-by-step + documents), foreigners (rights + restrictions for non-Paraguayans), closing-costs (what fees exist), renting (contracts, deposits, garante), publishing (listing tips), airbnb (short-term rental basics). ALWAYS use this for "how does buying/renting work" / process / documents questions — the content IS in scope to share; only personalized legal advice is not.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | – |
No output schema declared.
No examples provided.
get_listing Get Listing ~24
Get full listing detail by ID or slug.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_market_summary Market Summary ~76
Market stats: avg price, median, price/m². Scope with neighborhood for zone-level numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| country | string | – | – |
| listing_type | string | – | – |
| neighborhood | string | – | Neighborhood/barrio name for zone-scoped stats |
| property_type | string | – | – |
No output schema declared.
No examples provided.
get_project Get Project ~23
Get project detail with units and prices.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_str_data Short-Term Rental Data ~81
Airbnb/STR city-level data: nightly rates, occupancy.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City name or slug, accents optional (e.g. "Asunción" or "asuncion") |
| country | string | – | Country name or slug — disambiguates duplicate city names across countries |
| neighborhood | string | – | Neighborhood name for specific area stats |
No output schema declared.
No examples provided.
link_email Link Email to Account ~118
Attach a real email address to the signed-in user's phone-keyed TuLugar account (accounts created via WhatsApp have no usable email). Sends a confirmation link TO that email; the user must open it — the link proves they own the address. Ask for the email, confirm it back to them, then call this. Only works for accounts that do not have a real email yet; if the email belongs to another account, the tool explains the options (never merges silently).
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address the user wants to attach |
No output schema declared.
No examples provided.
list_locations List Locations ~59
List countries, cities, or neighborhoods with listing counts.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City name for neighborhoods (alternative to parent_id) |
| parent_id | string | – | country_id for cities, city_id for neighborhoods |
| type | string | yes | – |
No output schema declared.
No examples provided.
mortgage_calculator Mortgage Calculator ~127
Estimate a monthly mortgage payment and total interest for a buyer. Currency-agnostic. Optionally pass monthly_income for a debt-to-income ratio. This is an informational arithmetic estimate only — not financial advice, a loan offer, or a rate quote.
| Name | Type | Req | Description |
|---|---|---|---|
| annual_rate | number | yes | Annual interest rate, as a decimal (0.065) or percent (6.5) |
| monthly_income | number | – | Optional — enables a debt-to-income ratio |
| principal | number | yes | Loan amount |
| term_years | number | yes | Loan term in years (1–50) |
No output schema declared.
No examples provided.
my_inquiries My Inquiries ~41
List buyer inquiries (leads) received on the authenticated agent's listings, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max 100 (default 50) |
No output schema declared.
No examples provided.
my_listings My Listings ~122
List the authenticated agent's own listings across all statuses (draft, pending review, active, closed), so they can see what is live and what is awaiting moderation. Includes SYNCED listings (auto-imported from the agent's portal and kept up to date automatically) — those carry synced:true plus a sync block with the source platform, source URL and last check time. Synced listings can be edited, promoted and closed like any other.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max 100 (default 50) |
| status | string | – | Optional status filter |
No output schema declared.
No examples provided.
my_saved_searches ~21
List the connected user's saved searches and their alert settings.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
neighborhood_guide Neighborhood Guide ~107
What a neighborhood/zone is actually like, grounded in live data: sale + rent prices, listing counts, Airbnb occupancy when available, plus curated local context. ALWAYS use this for "¿cómo es <barrio>?" / "is X a good area?" questions instead of answering from memory.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City the neighborhood belongs to (recommended) |
| country | string | – | – |
| neighborhood | string | yes | Neighborhood/barrio name (accents optional) |
No output schema declared.
No examples provided.
open_web_session Open Signed-in Web Session ~118
Give the signed-in user a ONE-TAP link that opens tulugar.com already logged in to their account — no code, no password. Use when a WhatsApp user needs the website: upload photos, finish a listing in the wizard, manage their account. The link is single-use and expires in 10 minutes; share it verbatim. Only works for accounts with a verified WhatsApp number.
| Name | Type | Req | Description |
|---|---|---|---|
| return_to | string | – | Optional site path to land on (e.g. "/es/account/listings"). Defaults to the account home. |
No output schema declared.
No examples provided.
promote_listing Promote Listing ~134
Promote (feature) one of the authenticated agent's OWN listings by spending ONE promotional credit. A featured listing is highlighted and ranked ahead of regular results for ~14 days (extends the window if already featured). This SPENDS a paid credit, so confirm with the user before calling. If the account has no credits, this returns a message telling the user to buy some — use buy_promotional_credits for that. Pass listing_id from my_listings. Synced listings (synced:true) are promotable too.
| Name | Type | Req | Description |
|---|---|---|---|
| listing_id | string | yes | ID of the agent's own listing to feature (from my_listings) |
No output schema declared.
No examples provided.
publish_listing Publish Listing ~51
Submit a draft listing for moderation review, making it eligible to go public once approved. This is an irreversible submission — confirm with the user before calling.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Listing ID to submit for review |
No output schema declared.
No examples provided.
rental_yield Rental Yield ~109
Gross rental yield for a zone, computed from live medians (sale vs long-term rent, plus Airbnb when available). Zone-level market reference ONLY — never a valuation of a specific property. Use for "¿conviene invertir?" / rentabilidad / yield questions.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City (required) |
| country | string | – | – |
| neighborhood | string | – | Optional neighborhood scope; falls back to the city when data is thin |
| property_type | string | – | Default apartment |
No output schema declared.
No examples provided.
reply_to_inquiry ~127
Reply to a buyer inquiry (lead) on one of the agent's listings. Compose a helpful, professional reply as `message`, and this returns a one-tap WhatsApp link (wa.me) to the buyer with your message pre-filled — share that link with the agent to tap and send. Pass inquiry_id from my_inquiries. If the buyer left only an email, it returns the email to reply to instead.
| Name | Type | Req | Description |
|---|---|---|---|
| inquiry_id | string | yes | The inquiry/lead id (from my_inquiries) |
| message | string | yes | The reply to send to the buyer |
No output schema declared.
No examples provided.
save_search ~163
Save a property search for the connected user so they get alerts when new matching listings appear (e.g. "2-bed apartments for rent under $800 in Villa Morra"). Requires a connected account — if not connected, use connect_account first. Uses the same filters as search_listings. Returns the saved id.
| Name | Type | Req | Description |
|---|---|---|---|
| alert_frequency | string | – | How often to be alerted about new matches (default daily) |
| bedrooms | number | – | – |
| city | string | – | – |
| currency | string | – | – |
| listing_type | string | yes | – |
| max_price | number | – | – |
| min_price | number | – | – |
| name | string | – | Optional label for the saved search |
| neighborhood | string | – | – |
| property_type | string | – | – |
No output schema declared.
No examples provided.
search Search ~77
Search Tu Lugar real estate listings by free-text query (location, neighborhood, or keywords). Returns a list of matching listings with id, title, and URL. Use `fetch` to get a listing's full content.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search phrase, e.g. "apartment in Villa Morra" or "Encarnación" |
No output schema declared.
No examples provided.
search_agents ~97
Search REGISTERED real-estate agents and professionals on Tu Lugar by name, city, or company. Only covers people who created a public profile on the platform — there is no data about anyone else.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| company_id | string | – | – |
| limit | number | – | Max 20 |
| q | string | – | Agent name (or part of it) |
| verified | boolean | – | Only verified agents |
No output schema declared.
No examples provided.
search_companies Search Agencies & Developers ~147
Search agencies and developers BY NAME (or city/type). Use `q` with the company/agency name — e.g. q="RE/MAX Urbana" — punctuation and accents are ignored. This is how you answer "properties by <agency>" (find the company here, then search_listings with company set to its name; for a DEVELOPER also check search_projects with company set — developer inventory is usually projects/units, not listings).
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| limit | number | – | – |
| q | string | – | Company/agency name (partial ok; punctuation/accents ignored) |
| type | string | – | – |
| verified | boolean | – | – |
No output schema declared.
No examples provided.
search_listings Search Listings ~323
Search real estate listings. Filter by city, price, bedrooms, property type, or a specific agency/company.
| Name | Type | Req | Description |
|---|---|---|---|
| amenities | string | – | Comma-separated amenities/features the property must have, in the user's own words and language, e.g. "piscina, cochera" or "pool, gym". Common ones: pool/piscina, gym/gimnasio, garden/jardín, balcon… |
| bedrooms | number | – | – |
| building | string | – | Building/tower NAME to list the actual units for sale/rent in it, e.g. "Petra Tower" (punctuation/accents ignored). Use this — not search_projects — when the user wants the real listings in a named b… |
| city | string | – | City name, e.g. "Asunción" |
| company | string | – | Agency/company NAME to list only their properties, e.g. "RE/MAX Urbana" (resolved automatically; punctuation/accents ignored). |
| limit | number | – | Max 20 |
| listing_type | string | – | – |
| max_price | number | – | – |
| min_price | number | – | – |
| neighborhood | string | – | – |
| property_type | string | – | apartment, house, land, commercial |
| sort | string | – | – |
No output schema declared.
No examples provided.
search_projects Search Projects ~210
Search development projects/buildings BY NAME (or city, or DEVELOPER). Use `q` with the project or building name — e.g. q="Petra Tower" — punctuation/accents ignored, and a name lookup also finds completed/sold-out buildings. This is how you answer "apartments in <building/tower name>" and "is there a project called X". For "projects by <developer>" use `company` with the developer's name (NOT `q` — project names rarely contain the developer).
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| company | string | – | Developer/company name to list that developer's projects, e.g. "Pro Invest" |
| limit | number | – | – |
| max_price | number | – | – |
| min_price | number | – | – |
| q | string | – | Project/building name (partial ok; punctuation/accents ignored) |
| sort | string | – | – |
| status | string | – | – |
| verified | boolean | – | – |
No output schema declared.
No examples provided.
send_whatsapp_verification ~103
Send a WhatsApp verification code to the agent's mobile number. Publishing listings requires a verified WhatsApp number — if account_status shows can_publish=false, use this to start verification. A 6-digit code is delivered to the number over WhatsApp; then call verify_whatsapp_code with it.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Message language (default es) |
| phone | string | yes | Mobile number in international format, e.g. +595981234567 |
No output schema declared.
No examples provided.
share_listing_whatsapp Share Listing on WhatsApp ~207
Generate a ready-to-send WhatsApp message for one of the authenticated agent's OWN listings: a polished, WhatsApp-tuned caption + a one-tap wa.me link (optionally pre-addressed to a client phone) + the property's main photo to attach. Use whenever the agent wants to send, share, or forward a listing to a client (or to their WhatsApp status). Pass listing_id (from my_listings); optionally client_phone to pre-address the chat. After calling, you can personalize the message for a specific client and rebuild the wa.me link yourself (URL-encode the new text into https://wa.me/<number>?text=...).
| Name | Type | Req | Description |
|---|---|---|---|
| client_phone | string | – | Optional client phone, international format (e.g. +595981234567), to pre-address the WhatsApp chat |
| listing_id | string | yes | ID of the agent's own listing (from my_listings) |
| locale | string | – | Message language (default es) |
No output schema declared.
No examples provided.
upload_listing_image Upload Listing Image ~68
Upload a listing image by URL. Fetches the image, optimizes it, and returns hosted Tu Lugar image URLs to pass into create_listing.images[] or edit_listing.images[]. Rejected if the image fails property-photo moderation.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public https URL of the source image |
No output schema declared.
No examples provided.
verify_whatsapp_code ~61
Complete WhatsApp verification by submitting the 6-digit code the agent received on WhatsApp (after send_whatsapp_verification). On success the account can publish listings.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The 6-digit code sent to the WhatsApp number |
No output schema declared.
No examples provided.
What is the Tu Lugar MCP server?
Tu Lugar is an MCP server listed in the public MCP registry as com.tulugar/tulugar. Search and manage Paraguay & LatAm real estate from any AI assistant. This page covers its hosted endpoint (https://tulugar.com/api/mcp).
Is the Tu Lugar MCP server safe to use?
Tu Lugar scores 35 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 Tu Lugar MCP server expose?
Tu Lugar exposes 39 tools: search_listings, get_listing, search, fetch, search_projects, and 34 more. Their descriptions and schemas cost roughly 4,552 tokens of context every time the server is loaded.
Does the Tu Lugar MCP server require authentication?
No. We connected to Tu Lugar without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Tu Lugar MCP server still maintained?
Tu Lugar is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.