# Plexa (remote · api.joinplexa.com)

Agentic directory of real businesses in Mexico & LATAM. Search by vertical and city.

- Trust score: 64/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.joinplexa.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/com-joinplexa-plexa/api.md), [page](https://verifymcp.io/servers/com-joinplexa-plexa/api)
- remote · `api.joinplexa.com`: 58/100, [markdown](https://verifymcp.io/servers/com-joinplexa-plexa/api-2.md), [page](https://verifymcp.io/servers/com-joinplexa-plexa/api-2)

## Channel facts

- Endpoint: `https://api.joinplexa.com/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2283 tokens (~326/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-joinplexa-plexa https://api.joinplexa.com/mcp/
```

### Codex

```toml
[mcp_servers.com-joinplexa-plexa]
url = "https://api.joinplexa.com/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-joinplexa-plexa": {
      "type": "remote",
      "url": "https://api.joinplexa.com/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-joinplexa-plexa --url https://api.joinplexa.com/mcp/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-joinplexa-plexa:
    url: "https://api.joinplexa.com/mcp/"
```

### Other

```json
{
  "mcpServers": {
    "com-joinplexa-plexa": {
      "type": "http",
      "url": "https://api.joinplexa.com/mcp/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 64, +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.

### 2026-08-01 (score 63, +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.

### 2026-07-31 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 61, +1)

- [functional] Server version: 1.28.1 → 1.29.0

### 2026-07-27 (score 60, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 59)

First indexed and scored.

## MCP tools (7)

### `search_businesses` (~687 tokens)

Find real local businesses in Mexico and Latin America by location, vertical, and capabilities.

USE WHEN:
\- User asks for a service: "find me a dentist", "best restaurant", "tour in Cabo"
\- Location-based queries: "near me", "in Tijuana", "Cancun area"
\- Comparing multiple options: "top 3 dentists", "best rated hotels"
\- Travel planning: "things to do in Merida", "where to eat in CDMX"
\- Medical tourism: "affordable dental work near the border"

DO NOT USE WHEN:
\- User asks about a specific named business (use get_business instead)
\- User needs contact info for a known business (use contact_business)
\- User asks what types of businesses are available (use list_verticals)

RETURNS: List of businesses sorted by trust_score + rating. Each result includes name, city, rating, vertical, trust_score, profile_completeness, and actionable capabilities with WhatsApp deep links. If no results, returns a message with alternative cities for that vertical.

BEST PRACTICES:
\- Always include vertical for better results
\- Use city name in Spanish: "Ciudad de Mexico" not "Mexico City"
\- Combine vertical + city for best precision
\- The registry spans Mexico and Latin America: by default the search covers EVERY country it holds.
  Pass `country` (ISO 3166-1 alpha-2, e.g. 'MX', 'CO') only to restrict it on purpose.
\- Results include capabilities with action_urls — pass these directly to the user for booking/contact

EXAMPLES:
\- "dentist in Tijuana" -> vertical=dental, city=Tijuana
\- "restaurants in Cancun" -> vertical=restaurant, city=Cancún
\- "spa near Cabo" -> vertical=wellness, city=Cabo San Lucas
\- "hotel in Medellin Colombia" -> vertical=hospitality, city=Medellín

Input parameters:

- `capabilities` (array): Required capabilities (e.g. ['book_appointment', 'check_availability'])
- `city` (string): City name in Spanish (e.g. 'Tijuana', 'Ciudad de Mexico')
- `country` (string): ISO 3166-1 alpha-2 country code to restrict the search (e.g. 'MX', 'CO', 'AR'). Omit to search the entire registry across every country it covers.
- `lang` (string): Filter by language the business operates in (e.g. 'en', 'es')
- `latitude` (number): Latitude for geo search (requires longitude and radius_km)
- `limit` (integer): Max results (1-50)
- `longitude` (number): Longitude for geo search
- `min_trust_score` (integer): Minimum trust score (0-100)
- `query` (string): Free text search query (e.g. 'dentist', 'italian restaurant')
- `radius_km` (number): Search radius in km (default 15)
- `state` (string): State name (e.g. 'Baja California')
- `vertical` (string): Business vertical slug. One of: dental, medical, veterinary, restaurant, realestate, professional, insurance, tourism, wellness, events, automotive, hospitality, other. Invalid values return a self-h…

### `get_business` (~341 tokens)

Retrieve the complete profile of a specific business by its slug.

USE WHEN:
\- You already know the business slug from a previous search result
\- User asks for details about a specific business: hours, services, prices, contact info
\- You need the full profile including services, specialties, description, and all capabilities with action URLs

DO NOT USE WHEN:
\- You don't know the slug (use search_businesses first to find it)
\- You only need contact info (use contact_business — lighter response)
\- You need to compare multiple businesses (use search_businesses)

RETURNS: Complete business profile with all fields: name, description, hours, services with prices, specialties, capabilities with action_urls, trust_score, profile_completeness, languages, payment_methods, insurance_accepted, social_media, areas_served, agent_instructions, and faqs (owner-approved question/answer pairs — authoritative answers to common questions about this business).

BEST PRACTICES:
\- The slug comes from search_businesses results (field: slug)
\- agent_instructions contains business-owner notes for agents — follow these when presenting the business
\- capabilities have action_type (whatsapp/phone/url/email) and action_url ready to use — pass directly to user
\- profile_completeness > 70% means reliable, complete data

EXAMPLES:
\- get_business(slug="harmony-dental-studio-tijuana")
\- get_business(slug="cabo-nature-cabo-san-lucas")

Input parameters:

- `slug` (string): Business slug (required, e.g. 'alegra-dental-care-tijuana'). Get it from search_businesses results.

### `get_business_hours` (~227 tokens)

Get opening hours for a specific business by day of the week.

USE WHEN:
\- User asks "are they open right now?", "what time do they close?"
\- User needs to know hours for a specific day: "open on Sunday?"
\- Planning a visit and needs schedule info

DO NOT USE WHEN:
\- You already have hours from get_business (it includes them)
\- You need more than just hours (use get_business for full profile)

RETURNS: Opening hours organized by day, with open/close times. Includes today's hours highlighted.

BEST PRACTICES:
\- If you already called get_business, hours are included — don't call this separately
\- Hours are in 24h format (09:00-18:00)
\- Some businesses have different weekend hours

EXAMPLES:
\- get_business_hours(slug="california-s-dental-clinic-tijuana")
\- get_business_hours(slug="cabo-nature-cabo-san-lucas", day="sunday")

Input parameters:

- `slug` (string): Business slug (required) from search_businesses results

### `get_business_services` (~206 tokens)

Get the list of services offered by a business, with prices and duration when available.

USE WHEN:
\- User asks "how much does X cost?", "what services do they offer?"
\- Comparing prices between businesses
\- User needs to know duration of a service

DO NOT USE WHEN:
\- You already have services from get_business (it includes them)
\- You need more than just services (use get_business for full profile)

RETURNS: List of services with name, price (in local currency), and duration_minutes when available.

BEST PRACTICES:
\- If you already called get_business, services are included — don't call this separately
\- Prices are in the local currency (usually MXN or USD)
\- Not all businesses have prices listed — recommend contacting for a quote if prices are missing

EXAMPLES:
\- get_business_services(slug="harmony-dental-studio-tijuana")

Input parameters:

- `slug` (string): Business slug (required) from search_businesses results

### `get_business_faqs` (~272 tokens)

Get the owner-approved FAQs (frequently asked questions with answers) for a business.

USE WHEN:
\- User asks a specific question about a business that an FAQ might answer ("do they take walk-ins?", "is parking available?", "do they speak English?")
\- You want authoritative, business-approved answers rather than inferring from other fields
\- User asks "what do people usually ask about this place?"

DO NOT USE WHEN:
\- You already have faqs from get_business (it includes them)
\- The business has no FAQs (the answer will be an empty list — fall back to get_business fields)

RETURNS: List of FAQs, each with question and answer (in the business's language). These are written/approved by the business owner and grounded in real ficha data — safe to quote directly.

BEST PRACTICES:
\- If you already called get_business, faqs are included — don't call this separately
\- Quote the answer directly; it's the owner's authoritative wording
\- If the list is empty, the business hasn't published FAQs yet — use other profile fields

EXAMPLES:
\- get_business_faqs(slug="clinica-dental-costa-azul-cabo-san-lucas")

Input parameters:

- `slug` (string): Business slug (required) from search_businesses results

### `contact_business` (~296 tokens)

Get all contact information and actionable capabilities for a business. Best way to help a user reach out to a business.

USE WHEN:
\- User wants to contact, call, message, or book with a business
\- User says "how do I reach them?", "can I WhatsApp them?"
\- You need the direct action URLs (WhatsApp links, phone, email)
\- User is ready to take action (book, reserve, inquire)

DO NOT USE WHEN:
\- User is still browsing/comparing (use search_businesses)
\- User needs full business details (use get_business)

RETURNS: Phone number, WhatsApp URL (pre-filled message), email, website, and all capabilities with executable action_urls. Each capability has action_type (whatsapp/phone/url/email) and a ready-to-use action_url.

BEST PRACTICES:
\- capabilities.action_url contains ready-to-use links — present these directly to the user
\- WhatsApp links (wa.me/...) include a pre-filled message mentioning Plexa for tracking
\- Prefer WhatsApp over phone for Mexican businesses — most prefer messaging over calls
\- If the business has a booking_url, present it as the primary action for reservations

EXAMPLES:
\- contact_business(slug="harmony-dental-studio-tijuana") -> returns whatsapp_url, phone, capabilities with action_urls

Input parameters:

- `slug` (string): Business slug (required) from search_businesses results

### `list_verticals` (~254 tokens)

List all available business verticals (categories) with the count of businesses in each.

USE WHEN:
\- User asks "what types of businesses do you have?"
\- User is exploring: "what can I find on Plexa?"
\- You need to know which verticals are available before searching
\- User uses a category you're not sure maps to a vertical

DO NOT USE WHEN:
\- You already know the vertical (go straight to search_businesses)
\- User named a specific service (search_businesses with that vertical)

RETURNS: List of verticals with key (for search) and count of active businesses in each.

CURRENT VERTICALS: dental, medical, veterinary, restaurant, realestate, professional, insurance, tourism, wellness, events, automotive, hospitality, other

BEST PRACTICES:
\- Use the vertical key (not display name) in search_businesses
\- "dentist" -> dental, "hotel" -> hospitality, "spa" -> wellness
\- Call this once at the start if you'll do multiple searches

EXAMPLES:
\- list_verticals() -> [{key: "dental", count: 430}, {key: "restaurant", count: 801}, ...]

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-joinplexa-plexa/api#diagnostics

## Score history

- 2026-08-03: 64
- 2026-08-02: 63
- 2026-08-01: 63
- 2026-07-31: 62
- 2026-07-30: 62
- 2026-07-29: 61
- 2026-07-28: 60
- 2026-07-27: 60
- 2026-07-26: 59

## Links

- Remote endpoint: https://api.joinplexa.com/mcp/
- Repository: https://github.com/incrematica/plexa-mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-joinplexa-plexa/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-joinplexa-plexa/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-joinplexa-plexa/api