Is the Joinplexa Plexa MCP server down?

mcp-registry/com.joinplexa/plexa · v1.29.1

healthy
Last checked 2026-10-18 22:52 UTC · handshake 381ms

As of 2026-10-18 22:52 UTC, the Joinplexa Plexa MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 11 outages in 90 days, with a median recovery of 6 minutes.

uptime (30d checks)
99.9%
checks observed
3,722
outages (90d)
11
tools
8

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

Install Joinplexa Plexa MCP server

Add to Cursor Add to VS Code

Claude Code

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (84/100)

B (84/100): 0 error(s), 2 warning(s) across 7 tool(s); ~1,733 tokens of tool definitions.
Scores higher than 45% of 15,338 MCP servers Glimind has audited.
Its tool list costs an agent ~1,733 tokens per session — lighter than 60% of servers.
84 → 84 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (3)

7 of 7 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: contact_business, get_business, get_business_faqs, get_business_hours, get_business_services and 2 more

Handshake + tools/list takes ~2,058 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 6 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.joinplexa%2Fplexa/fixes

get_business 1 change
{
  "name": "get_business",
  "description": "Retrieve the complete profile of a specific business by its slug.\n\nUSE WHEN:\n- You already know the business slug from a previous search result\n- User asks for details about a specific business: hours, services, prices, contact info\n- You need the full profile including services, specialties, description, and all capabilities with action URLs\n\nDO NOT USE WHEN:\n- You don't know the slug (use search_businesses first to find it)\n- You only need contact info (use contact_business — lighter response)",
  "inputSchema": {
    "type": "object",
    "properties": {
      "slug": {
        "type": "string",
        "description": "Business slug (required, e.g. 'alegra-dental-care-tijuana'). Get it from search_businesses results."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_business_faqs 1 change
{
  "name": "get_business_faqs",
  "description": "Get the owner-approved FAQs (frequently asked questions with answers) for a business.\n\nUSE WHEN:\n- 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?\")\n- You want authoritative, business-approved answers rather than inferring from other fields\n- User asks \"what do people usually ask about this place?\"\n\nDO NOT USE WHEN:\n- You already have faqs from get_business (it includes them)\n- The business has no",
  "inputSchema": {
    "type": "object",
    "properties": {
      "slug": {
        "type": "string",
        "description": "Business slug (required) from search_businesses results"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_business_hours 1 change
{
  "name": "get_business_hours",
  "description": "Get opening hours for a specific business by day of the week.\n\nUSE WHEN:\n- User asks \"are they open right now?\", \"what time do they close?\"\n- User needs to know hours for a specific day: \"open on Sunday?\"\n- Planning a visit and needs schedule info\n\nDO NOT USE WHEN:\n- You already have hours from get_business (it includes them)\n- You need more than just hours (use get_business for full profile)\n\nRETURNS: Opening hours organized by day, with open/close times. Includes today's hours highlighted.\n\nBE",
  "inputSchema": {
    "type": "object",
    "properties": {
      "slug": {
        "type": "string",
        "description": "Business slug (required) from search_businesses results"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.joinplexa/plexa"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.joinplexa/plexa"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.joinplexa%2Fplexa.svg)](https://glimind.com/server/mcp-registry%2Fcom.joinplexa%2Fplexa?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.joinplexa%2Fplexa?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.joinplexa%2Fplexa.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.joinplexa%2Fplexa.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.joinplexa%2Fplexa?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:047f87b8f900d489…, first seen 2026-10-17, included at leaf 2829 of 23,678. Version history · verify what your client received.

Tools (8)

Compare: most reliable communication servers · most reliable data servers · most reliable knowledge servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Joinplexa Plexa MCP server down right now?

As of 2026-10-18 22:52 UTC, the Joinplexa Plexa MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 11 outages in 90 days, with a median recovery of 6 minutes.

How many tools does Joinplexa Plexa MCP server provide?

Joinplexa Plexa MCP server advertises 8 tools, including contact_business, get_business, get_business_details, get_business_faqs, get_business_hours.

How do I install Joinplexa Plexa MCP server?

Point your MCP client at this streamable-http endpoint: https://api.joinplexa.com/mcp/

Is the Joinplexa Plexa MCP server safe to connect to an AI agent?

Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Joinplexa Plexa MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve