ai.openmandate/mcp · v0.6.1 · sales-and-crm
OpenMandate is healthy: it completed an MCP handshake in 648 ms and exposes 15 tools. It scores 63/100.
OpenMandate is in private development and is not accepting new mandates or integrations.
Endpoint: https://mcp.openmandate.ai/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| health | 23.4 / 25 |
| authEase | 15 / 15 |
| toolQuality | 15 / 15 |
| maintenance | 5 / 15 |
| adoption | 0 / 10 |
| usage | 0 / 10 |
| security | 5 / 10 |
Scoring v0.3, computed 2026-10-15T08:34:03.987Z.
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-14T10:15:31.956Z | Healthy | 648 |
openmandate_create_mandate | Create a new mandate on OpenMandate. Provide what the user is looking for (want) and what they bring to the table (offer). The user's verified contacts are automatically attached. Returns the mandate with follow-up questions. You MUST relay these questions to the user and collect their actual answe |
openmandate_submit_answers | Submit the user's answers to pending intake questions. The mandate must be in 'intake' status with pending questions. IMPORTANT: Before calling this, you must show each pending question to the user and collect their real answer. Never fabricate or infer answers. OpenMandate may return additional qu |
openmandate_get_mandate | Get a mandate by ID. Returns the mandate's current status, any pending intake questions, and summary once active. Use this to check progress or retrieve questions after creating a mandate. |
openmandate_list_mandates | List the user's open mandates. Returns non-closed mandates by default. Pass status to filter (e.g. status='closed' for history). |
openmandate_close_mandate | Close (withdraw) a mandate. This is permanent — the mandate will stop matching and cannot be reopened. Only close if the user explicitly wants to withdraw. |
openmandate_list_matches | List matches for the authenticated user. Returns matches with compatibility grade, strengths, and concerns. Check this periodically after a mandate becomes active. |
openmandate_get_match | Get detailed information about a specific match, including compatibility grade, strengths, concerns, and — if both parties accepted — the counterparty's contact information. |
openmandate_respond_to_match | Accept or decline a match. If you accept and the other party also accepts, contact info is revealed to both sides. Declining is permanent for this match. |
openmandate_submit_outcome | Report how a confirmed match went. Available after both parties accepted and contact info was revealed. Outcomes: - 'succeeded': Found the right person. Mandate closes. - 'failed': Didn't work out. Mandate reactivates for new matches. - 'ongoing': Still in conversation. OpenMandate checks back late |
openmandate_list_contacts | List the user's verified contacts. These are the contacts revealed to the other party on match confirmation. Each contact has an ID, type, display label, and verification status. |
openmandate_add_contact | Add a new contact for the user. A verification code (OTP) will be sent to the contact address. The user must verify the contact using openmandate_verify_contact before it can be used on mandates. The first contact added becomes the primary contact automatically. |
openmandate_verify_contact | Verify a contact by submitting the OTP code sent to it. The user must check their email for the 8-digit code. After verification, the contact can be used on mandates. |
openmandate_update_contact | Update a contact's display label or set it as the primary contact. Setting a contact as primary will unset any other primary contact. |
openmandate_delete_contact | Delete a contact. If the deleted contact was primary, the next verified contact is automatically promoted. This is permanent. |
openmandate_resend_otp | Resend the verification code for a pending contact. Use this if the user didn't receive the code or it expired (codes expire after 10 minutes). Rate limited to 3 per contact per hour. |