MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

Plexa

Claim this listing

com.joinplexa/plexa

joinplexa.com

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

Search & web data

OtherIs Plexa down?Alternatives

12 of 22 checks passed

  • Handshake
  • Tools listed
  • Updated recently

Responded

The server completed its last measured handshake. This is an observation, not a guarantee.

Connect to server
Median latency
399 ms
Uptime, 30 days
Not measured
Last checked

Measurement details

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 399 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name plexa.

  • Pass
    Lists tools

    tools/list returned 7 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 399 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 399 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    17 of 17 parameters have a description (100%). The bar is 80%.

  • Fail
    Safety hints

    7 tools set neither readOnlyHint nor destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Fail
    Website matches publisher

    The website host does not match the reverse-domain namespace.

  • Pass
    Source repo linked

    A repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-06-17T00:41:44.327265Z, within 180 days.

  • Not measured
    Open-source licence

    The GitHub licence lookup has not returned an OSI result yet.

Tools

  • contact_business

    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

    Measured

  • get_business

    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), and offerings (tours). An offering that has a book_url has a 'Reservar' (book) link: the booking is completed on Viator through a Plexa affiliate link, Plexa may earn a commission, and the price for the traveler is the same. 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")

    Measured

  • get_business_faqs

    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")

    Measured

  • get_business_hours

    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")

    Measured

  • get_business_services

    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")

    Measured

  • list_verticals

    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, transport, 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}, ...]

    Measured

  • search_businesses

    Find real local businesses in Mexico 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 ordered by tier (Connected/claimed first), then trust_score, then recency. 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 covers Mexico (businesses outside Mexico were archived in Nov 2026). `country` (ISO 3166-1 alpha-2, e.g. 'MX') is optional. - 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 Guadalajara" -> vertical=hospitality, city=Guadalajara

    Measured

Probe history

  • ok399 ms7 tools

Status and uptime

Add badge to your README

The image links back to this page. It shows checks passed, or uptime, and the colour follows the latest status. Responses are cached for 5 to 15 minutes.

MCP Heartbeat badge

Markdown

[![MCP Heartbeat](https://mcpheartbeat.com/badge/com.joinplexa/plexa.svg)](https://mcpheartbeat.com/s/com.joinplexa/plexa)

HTML

<a href="https://mcpheartbeat.com/s/com.joinplexa/plexa"><img alt="MCP Heartbeat" src="https://mcpheartbeat.com/badge/com.joinplexa/plexa.svg"></a>

Uptime markdown

[![MCP Heartbeat uptime](https://mcpheartbeat.com/badge/com.joinplexa/plexa.svg?kind=uptime)](https://mcpheartbeat.com/s/com.joinplexa/plexa)

Served from https://mcpheartbeat.com.

Related servers

All alternatives

Same function and industry, ranked by checks passed then median latency.

Connect to this server

Claude Code

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

Cursor .cursor/mcp.json

{
  "mcpServers": {
    "plexa": {
      "url": "https://api.joinplexa.com/mcp/"
    }
  }
}

VS Code .vscode/mcp.json

{
  "servers": {
    "plexa": {
      "type": "http",
      "url": "https://api.joinplexa.com/mcp/"
    }
  }
}