Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

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

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

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

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

{
  "mcpServers": {
    "plexa": {
      "type": "http",
      "url": "https://api.joinplexa.com/mcp/"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=plexa&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYXBpLmpvaW5wbGV4YS5jb20vbWNwLyJ9"
}

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

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

extensions:
  "plexa":
    enabled: true
    name: "plexa"
    type: streamable_http
    uri: "https://api.joinplexa.com/mcp/"
    timeout: 300

Quality 76 / 100good

protocol75 · weight 25

warn
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
n/a
protocol.statelessonly applies to 2026-07-28 servers
pass
protocol.transportstreamable HTTP
n/a
protocol.list_ttlonly applies to 2026-07-28 servers

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene64 · weight 30

pass
tools.descriptionsevery tool has a description
warn
tools.description_length5 tools have descriptions over 1,024 characters, which crowds the context
pass
tools.schemasevery tool has an object input schema
fail
tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
fail
tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: get_business_services (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_business (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); contact_business (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
pass
tools.token_costabout 2,626 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability100 · weight 15

pass
stability.changesno tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

7 tools, about 2,626 tokens to load them all · tool set 542c86e3c815 · checked 2026-10-19 10:52 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 86 / 100

provenance75

liveness100

freshness65

hygiene100

+repository +dns-namespace +reachable +uptime-100% ~updated-124d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://api.joinplexa.com/mcp/` streamable-http	none	yes	100%	229 ms	2025-11-25	2026-10-19
`https://api.joinplexa.com/mcp/sse` sse	none	yes	98%	210 ms	2025-11-25	2026-10-19

Tools (7)

`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
`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). 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")
`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")
`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")
`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")
`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, 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}, ...]
`search_businesses`	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

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "com.joinplexa/plexa",
  "title": "Plexa",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://api.joinplexa.com/mcp/",
      "type": "streamable-http"
    },
    {
      "url": "https://api.joinplexa.com/mcp/sse",
      "type": "sse"
    }
  ],
  "version": "1.0.0",
  "repository": {
    "url": "https://github.com/incrematica/plexa-mcp",
    "source": "github"
  },
  "description": "Agentic directory of real businesses in Mexico & LATAM. Search by vertical and city."
}