MCP serverai.openmandate/mcp
OpenMandate is in private development and is not accepting new mandates or integrations.
Overview
Score?
UNRATED 0.681
of what a free look can see, on 32 looks
Looks
36
last 12 hr ago
Tools
15
More info
URL
mcp.openmandate.ai/mcp
streamable-http
Says it is
openmandate 0.6.0
protocol 2025-03-26
In the record since
32 days ago
Among servers18,413 with a card
0median 0.606 · this server 0.681 · highest on record 0.8561
Toolsfrom sha256:9c41500668…747e12
| Tool | Schema |
|---|---|
| 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 us |
input · no output |
| 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. |
input · no output |
| 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.
|
input · no output |
| openmandate_delete_contact Delete a contact. If the deleted contact was primary, the next verified contact is automatically promoted. This is permanent. |
input · no output |
| 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 |
input · no output |
| 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. |
input · no output |
| 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. |
input · no output |
| 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). |
input · no output |
| 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. |
input · no output |
| 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 ho |
input · no output |
| 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. |
input · no output |
| 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 qu |
input · no output |
| 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' |
input · no output |
| 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. |
input · no output |
| 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. |
input · no output |
Verify it yourself
npx teppi-check https://mcp.openmandate.ai/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M1FZ22FKZQBV12YZYB5HNR56