OpenMandate MCP server
OpenMandate is in private development and is not accepting new mandates or integrations.
Little public usage data yet
Reviews
Write oneNobody has reviewed OpenMandate yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
OpenMandate tools (15, 5 write)
write = sends, deletes, buys or postsopenmandate_add_contactFreeAdd 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_close_mandateFreeClose (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_create_mandatewrite actionFreeCreate 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.
openmandate_delete_contactwrite actionFreeDelete a contact. If the deleted contact was primary, the next verified contact is automatically promoted. This is permanent.
openmandate_get_mandateFreeGet 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_get_matchFreeGet detailed information about a specific match, including compatibility grade, strengths, concerns, and — if both parties accepted — the counterparty's contact information.
openmandate_list_contactsFreeList 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_mandatesFreeList the user's open mandates. Returns non-closed mandates by default. Pass status to filter (e.g. status='closed' for history).
openmandate_list_matchesFreeList matches for the authenticated user. Returns matches with compatibility grade, strengths, and concerns. Check this periodically after a mandate becomes active.
openmandate_resend_otpFreeResend 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.
openmandate_respond_to_matchFreeAccept 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_answerswrite actionFreeSubmit 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.
openmandate_submit_outcomewrite actionFreeReport 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.
openmandate_update_contactwrite actionFreeUpdate a contact's display label or set it as the primary contact. Setting a contact as primary will unset any other primary contact.
openmandate_verify_contactFreeVerify 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.
Public scan report
scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 737ms20/20
- Tool poisoning15 tool descriptions checked15/15
- Auth qualityAPI key sent as a header8/15
- Maintenanceno repository listed3/15
- Maintainer identityverified namespace with website, no repo4/10
Findings (1)
- lowNo source repository listed
maint.no-repo
Install directly
claude mcp add --transport http mcp https://mcp.openmandate.ai/mcp
OpenMandate: common questions
- Is OpenMandate MCP server safe?
- With care: it is graded C, so read the findings first (67/100). Read the OpenMandate safety report
- How do I install OpenMandate?
- It runs remotely at mcp.openmandate.ai. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does OpenMandate need an API key?
- Yes. The registry entry asks for
Authorization. - Is OpenMandate maintained?
- The latest release is v0.6.1.
- Is OpenMandate up?
- 100% of our last 6 checks got an answer. We check remote servers about four times a day.