Skip to content

Plexa MCP server

com.joinplexa/plexajoinplexa.comstreamable-httpv1.0.0Scanned

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

7 tools: 7 only read.

Tools: 0 delete, 0 irreversible, 0 write, 7 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Plexa MCP server can do

The Plexa MCP server is published by joinplexa.com, a domain the MCP Registry verified. It has 7 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

1 tool reads private data (contact_business).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 10, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Only reads 7Show 7 read-only tools
  • contact_businessGet all contact information and actionable capabilities for a business.Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.

    What it can reach

    • private-dataThe name "contact_business" says "contact": it reads contacts.
    • private-dataThe description's first sentence says "get" and "contact": it reads contacts.
    Description, as the server wrote it
    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_businessRetrieve the complete profile of a specific business by its slug.No findings

    Why it is in this group

    • The name "get_business" says "get": a word for reading.
    Description, as the server wrote it
    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")
  • get_business_faqsGet the owner-approved FAQs (frequently asked questions with answers) for a business.No findings

    Why it is in this group

    • The name "get_business_faqs" says "get": a word for reading.
    Description, as the server wrote it
    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_hoursGet opening hours for a specific business by day of the week.No findings

    Why it is in this group

    • The name "get_business_hours" says "get": a word for reading.
    Description, as the server wrote it
    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_servicesGet the list of services offered by a business, with prices and duration when available.No findings

    Why it is in this group

    • The name "get_business_services" says "get": a word for reading.
    Description, as the server wrote it
    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_verticalsList all available business verticals (categories) with the count of businesses in each.No findings

    Why it is in this group

    • The name "list_verticals" says "list": a word for reading.
    Description, as the server wrote it
    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}, ...]
  • search_businessesFind real local businesses in Mexico by location, vertical, and capabilities.No findings

    Why it is in this group

    • The name "search_businesses" says "search": a word for reading.
    Description, as the server wrote it
    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

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:41 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
yes
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools3 changed.~3 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__plexa__search_businesses",
      "mcp__plexa__get_business",
      "mcp__plexa__get_business_hours",
      "mcp__plexa__get_business_services",
      "mcp__plexa__get_business_faqs",
      "mcp__plexa__contact_business",
      "mcp__plexa__list_verticals"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as plexa. Review it before you use it.

Capability tags behind 1 rule
  • mcp__plexa__contact_business private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.joinplexa/plexa/verify?hash=54e51e1863bcfb08c2c0f86e755c4619c850658d62c7abce83a9294bae7c934b" | jq -e '.changed == false'

Pinned hash 54e51e1863bc, from Nov 10, 2026, 19:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.joinplexa/plexa/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.joinplexa/plexa
[![Anlyon Radar](https://radar.anlyon.com/badge/com.joinplexa/plexa.svg)](https://radar.anlyon.com/servers/com.joinplexa/plexa)

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:57 UTC.

Plexa MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Plexa MCP server safe?

No scan can promise that. What its definitions show: 7 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the Plexa MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Plexa MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Plexa MCP server have?

7 tools: 7 read. search_businesses, get_business, get_business_hours, get_business_services, get_business_faqs, contact_business and list_verticals.

Does the Plexa MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Plexa MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Plexa MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.