OpenMandate
ai.openmandate/mcpVersion 0.6.1OpenMandate is in private development and is not accepting new mandates or integrations.
Status
Responds390 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:31 UTC
- Latency
- 390 ms
- Remotes responding
- 1 of 1
- Sign-in
- API key
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://mcp.openmandate.ai/mcpResponds390 msNo sign-in
Claude Code
claude mcp add --transport http openmandate https://mcp.openmandate.ai/mcp --header 'Authorization: Bearer <YOUR_TOKEN>'Replace <YOUR_TOKEN> before running.
Claude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: openmandate
Remote MCP server URL: https://mcp.openmandate.ai/mcp
This server expects the header Authorization.Cursor
{
"mcpServers": {
"openmandate": {
"url": "https://mcp.openmandate.ai/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Replace <YOUR_TOKEN> before running.
VS Code
code --add-mcp '{"name":"openmandate","type":"http","url":"https://mcp.openmandate.ai/mcp","headers":{"Authorization":"Bearer <YOUR_TOKEN>"}}'Replace <YOUR_TOKEN> before running.
Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
15 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
openmandate_add_contactAdd 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. | No | No | Not declared | Not declared |
openmandate_close_mandateClose (withdraw) a mandate. This is permanent — the mandate will stop matching and cannot be reopened. Only close if the user explicitly wants to withdraw. | Yes | No | Not declared | Not declared |
openmandate_create_mandateCreate 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. | No | No | Not declared | Not declared |
openmandate_delete_contactDelete a contact. If the deleted contact was primary, the next verified contact is automatically promoted. This is permanent. | Yes | No | Not declared | Not declared |
openmandate_get_mandateGet 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. | No | Yes | Not declared | Not declared |
openmandate_get_matchGet detailed information about a specific match, including compatibility grade, strengths, concerns, and — if both parties accepted — the counterparty's contact information. | No | Yes | Not declared | Not declared |
openmandate_list_contactsList 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. | No | Yes | Not declared | Not declared |
openmandate_list_mandatesList the user's open mandates. Returns non-closed mandates by default. Pass status to filter (e.g. status='closed' for history). | No | Yes | Not declared | Not declared |
openmandate_list_matchesList matches for the authenticated user. Returns matches with compatibility grade, strengths, and concerns. Check this periodically after a mandate becomes active. | No | Yes | Not declared | Not declared |
openmandate_resend_otpResend 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. | No | No | Not declared | Not declared |
openmandate_respond_to_matchAccept 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. | No | No | Not declared | Not declared |
openmandate_submit_answersSubmit 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. | No | No | Not declared | Not declared |
openmandate_submit_outcomeReport 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. | No | No | Not declared | Not declared |
openmandate_update_contactUpdate a contact's display label or set it as the primary contact. Setting a contact as primary will unset any other primary contact. | No | No | Not declared | Not declared |
openmandate_verify_contactVerify 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. | No | No | Not declared | Not declared |
Details
- Registry status
- Active
- Published
- Sep 2, 2026
- Updated
- Sep 2, 2026
- Repository
- Not given
- Categories
- Uncategorized
- GDPR
- Not declared