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.

Plexa

REMOTE · API.JOINPLEXA.COM · 2 COMPONENTS · SCANNED SEP 25

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

0 this week 77 Trust /100
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 Security57
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2293 tokens (~327/item across 7 items; 7 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
Install

How do I install the Plexa MCP server?

Plexa is a hosted endpoint at https://api.joinplexa.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 · api.joinplexa.com

# add to Claude Code
claude mcp add --transport http com-joinplexa-plexa 'https://api.joinplexa.com/mcp/'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-joinplexa-plexa": {
      "url": "https://api.joinplexa.com/mcp/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-joinplexa-plexa": {
      "type": "http",
      "url": "https://api.joinplexa.com/mcp/"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add com-joinplexa-plexa --url 'https://api.joinplexa.com/mcp/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-joinplexa-plexa:
    url: "https://api.joinplexa.com/mcp/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-joinplexa-plexa": {
      "Transport": "http",
      "Url": "https://api.joinplexa.com/mcp/"
    }
  }
}
# add to Vellum
assistant mcp add com-joinplexa-plexa -t streamable-http -u 'https://api.joinplexa.com/mcp/'
// mcp.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 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.

  • 26 Aug 26 77
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
    • Server version: 1.29.0 → 1.29.1 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
  • 7 Aug 26 0
    • The server no longer declares the “experimental” capability functional
  • 5 Aug 26 0
    • Tool “search_businesses” rewrote its description, which is the text the model reads security
  • 31 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
  • 30 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
  • 29 Jul 26 0
    • Server version: 1.28.1 → 1.29.0 functional
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 24 Sept 2026 · Probed https://api.joinplexa.com/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.joinplexa.com CN=YR2,O=Let's Encrypt,C=US 5 Aug 2026 3 Nov 2026 RSA 4096 SHA256-RSA 63c8c901caf6a8742753a80cd24278aced8
SANs: api.joinplexa.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.joinplexa.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
joinplexa.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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.joinplexa.com/mcp/ Verified 200
http (plaintext) http://api.joinplexa.com/mcp/ HTTPS enforced 302 https://api.joinplexa.com/mcp/
MCP tools · 7 exposed · ~2,293 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
contact_business ~296

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

NameTypeReqDescription
slugstring–Business slug (required) from search_businesses results

No output schema declared.

No examples provided.

get_business ~341

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

NameTypeReqDescription
slugstring–Business slug (required, e.g. 'alegra-dental-care-tijuana'). Get it from search_businesses results.

No output schema declared.

No examples provided.

get_business_faqs ~272

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

NameTypeReqDescription
slugstring–Business slug (required) from search_businesses results

No output schema declared.

No examples provided.

get_business_hours ~227

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

NameTypeReqDescription
slugstring–Business slug (required) from search_businesses results

No output schema declared.

No examples provided.

get_business_services ~206

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

NameTypeReqDescription
slugstring–Business slug (required) from search_businesses results

No output schema declared.

No examples provided.

list_verticals ~254

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_businesses ~697

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

NameTypeReqDescription
capabilitiesarray–Required capabilities (e.g. ['book_appointment', 'check_availability'])
citystring–City name in Spanish (e.g. 'Tijuana', 'Ciudad de Mexico')
countrystring–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.
langstring–Filter by language the business operates in (e.g. 'en', 'es')
latitudenumber–Latitude for geo search (requires longitude and radius_km)
limitinteger–Max results (1-50)
longitudenumber–Longitude for geo search
min_trust_scoreinteger–Minimum trust score (0-100)
querystring–Free text search query (e.g. 'dentist', 'italian restaurant')
radius_kmnumber–Search radius in km (default 15)
statestring–State name (e.g. 'Baja California')
verticalstring–Business vertical slug. One of: dental, medical, veterinary, restaurant, realestate, professional, insurance, tourism, wellness, events, automotive, hospitality, other. Invalid values return a self-h…

No output schema declared.

No examples provided.

Common questions

What is the Plexa MCP server?

Plexa is an MCP server listed in the public MCP registry as com.joinplexa/plexa. Agentic directory of real businesses in Mexico & LATAM. Search by vertical and city. This page covers its hosted endpoint (https://api.joinplexa.com/mcp/).

Is the Plexa MCP server safe to use?

Plexa scores 77 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 Plexa MCP server expose?

Plexa exposes 7 tools: search_businesses, get_business, get_business_hours, get_business_services, get_business_faqs, and 2 more. Their descriptions and schemas cost roughly 2,293 tokens of context every time the server is loaded.

Does the Plexa MCP server require authentication?

No. We connected to Plexa without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Plexa MCP server still maintained?

Plexa is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.