mcp server
OpenMandate
MCP server for OpenMandate — find cofounders and early teammates beyond your network. 15 tools.
Description as published by the maintainer. Source
- version 0.6.0
- slowing
slowing — Registry entry last updated 2026-04-15.
What this server can do
15 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
openmandate_add_contact(contact_type, contact_value, display_label)- 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. Required: contact_type, contact_value.
openmandate_close_mandate(mandate_id)- 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. Required: mandate_id.
openmandate_create_mandate(want, offer)- 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 answers before calling openmandate_submit_answers. Do not answer questions on the user's behalf. If the user has no verified contacts, they must add one first at https://openmandate.ai/settings or use openmandate_list_contacts to check. Required: want, offer.
openmandate_delete_contact(contact_id)- Delete a contact. If the deleted contact was primary, the next verified contact is automatically promoted. This is permanent. Required: contact_id.
openmandate_get_mandate(mandate_id)- 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. Required: mandate_id.
openmandate_get_match(match_id)- Get detailed information about a specific match, including compatibility grade, strengths, concerns, and — if both parties accepted — the counterparty's contact information. Required: match_id.
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_list_mandates(limit, status)- List the user's open mandates. Returns non-closed mandates by default. Pass status to filter (e.g. status='closed' for history).
openmandate_list_matches(limit)- List matches for the authenticated user. Returns matches with compatibility grade, strengths, and concerns. Check this periodically after a mandate becomes active.
openmandate_resend_otp(contact_id)- 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. Required: contact_id.
openmandate_respond_to_match(action, match_id, decline_reason, decline_reason_text)- 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. Required: match_id, action.
openmandate_submit_answers(answers, mandate_id)- 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 questions. Relay each round to the user until the mandate becomes active. Required: mandate_id, answers.
openmandate_submit_outcome(outcome, match_id)- 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 later. IMPORTANT: Always confirm the outcome with the user before submitting. This affects their mandate and matching status. Required: match_id, outcome.
openmandate_update_contact(contact_id, is_primary, display_label)- Update a contact's display label or set it as the primary contact. Setting a contact as primary will unset any other primary contact. Required: contact_id.
openmandate_verify_contact(code, contact_id)- 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. Required: contact_id, code.
Last successful function declaration observed on . Source: https://mcp.openmandate.ai/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://mcp.openmandate.ai/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.6.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-04-15 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-04-15 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 15 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | mcp.openmandate.ai | |
| mcp endpoint status | ok | The server listed 15 functions when asked. | as of probe | mcp.openmandate.ai |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json