_ registry / mcp http-sse · checked 2h ago

plexa

https://api.joinplexa.com

Registry code: 9d7708d78680ed8b

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://api.joinplexa.com/mcp/
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is plexa live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is plexa free to use?
Yes — the hub reached it with no key and no payment.
What tools does plexa have?
7 tools: contact_business, get_business_services, search_businesses, get_business, get_business_faqs, get_business_hours, list_verticals.
Is plexa safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.5%

90 days 98.7%· all time 98.7%

latency
349ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 389 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • search local businesses in mexico and latin america
  • get business hours and services
  • get business contact information
takes → gives
text → data
tools
7 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 7 tools
6 open 1 never probed 6 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_business_services reads open 19h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "slug": {
          "type": "string",
          "description": "Business slug (required) from search_businesses results"
        }
      }
    }
    arguments 9 lines
  • search_businesses reads open 19h ago

    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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "city": {
          "type": "string",
          "description": "City name in Spanish (e.g. 'Tijuana', 'Ciudad de Mexico')"
        },
        "lang": {
          "type": "string",
          "description": "Filter by language the business operates in (e.g. 'en', 'es')"
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "description": "Max results (1-50)"
        },
        "query": {
          "type": "string",
          "description": "Free text search query (e.g. 'dentist', 'italian restaurant')"
        },
        "state": {
          "type": "string",
          "description": "State name (e.g. 'Baja California')"
        },
        "country": {
          "type": "string",
          "description": "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."
        },
        "latitude": {
          "type": "number",
          "description": "Latitude for geo search (requires longitude and radius_km)"
        },
        "vertical": {
          "type": "string",
          "description": "Business vertical slug. One of: dental, medical, veterinary, restaurant, realestate, professional, transport, insurance, tourism, wellness, events, automotive, hospitality, other. Invalid values return a self-healing error listing valid options."
        },
        "longitude": {
          "type": "number",
          "description": "Longitude for geo search"
        },
        "radius_km": {
          "type": "number",
          "default": 15,
          "description": "Search radius in km (default 15)"
        },
        "capabilities": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Required capabilities (e.g. ['book_appointment', 'check_availability'])"
        },
        "min_trust_score": {
          "type": "integer",
          "default": 0,
          "description": "Minimum trust score (0-100)"
        }
      }
    }
    arguments 59 lines
  • get_business reads open 16h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "slug": {
          "type": "string",
          "description": "Business slug (required, e.g. 'alegra-dental-care-tijuana'). Get it from search_businesses results."
        }
      }
    }
    arguments 9 lines
  • get_business_faqs reads open 16h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "slug": {
          "type": "string",
          "description": "Business slug (required) from search_businesses results"
        }
      }
    }
    arguments 9 lines
  • get_business_hours reads open 16h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "slug": {
          "type": "string",
          "description": "Business slug (required) from search_businesses results"
        }
      }
    }
    arguments 9 lines
  • list_verticals reads open 19h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • contact_business reads unknown never probed

    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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "slug": {
          "type": "string",
          "description": "Business slug (required) from search_businesses results"
        }
      }
    }
    arguments 9 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 9d7708d78680ed8b.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/9d7708d78680ed8b/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/9d7708d78680ed8b/badge.svg)](https://brick.blue/agent/9d7708d78680ed8b?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.