OpenMandate is in private development and is not accepting new mandates or integrations.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://mcp.openmandate.ai/mcp15 tools · 135msopenmandate_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.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.
No input schema was published for this tool.
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.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.
No input schema was published for this tool.
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.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.
No input schema was published for this tool.
openmandate_list_mandatesList the user's open mandates. Returns non-closed mandates by default. Pass status to filter (e.g. status='closed' for history).List the user's open mandates. Returns non-closed mandates by default. Pass status to filter (e.g. status='closed' for history).
No input schema was published for this tool.
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.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.
No input schema was published for this tool.
openmandate_list_matchesList matches for the authenticated user. Returns matches with compatibility grade, strengths, and concerns. Check this periodically after a mandate becomes active.List matches for the authenticated user. Returns matches with compatibility grade, strengths, and concerns. Check this periodically after a mandate becomes active.
No input schema was published for this tool.
openmandate_get_matchGet detailed information about a specific match, including compatibility grade, strengths, concerns, and — if both parties accepted — the counterparty's contact information.Get detailed information about a specific match, including compatibility grade, strengths, concerns, and — if both parties accepted — the counterparty's contact information.
No input schema was published for this tool.
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.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.
No input schema was published for this tool.
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.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.
No input schema was published for this tool.
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.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.
No input schema was published for this tool.
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.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.
No input schema was published for this tool.
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.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.
No input schema was published for this tool.
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.Update a contact's display label or set it as the primary contact. Setting a contact as primary will unset any other primary contact.
No input schema was published for this tool.
openmandate_delete_contactprivilegedDelete a contact. If the deleted contact was primary, the next verified contact is automatically promoted. This is permanent.Delete a contact. If the deleted contact was primary, the next verified contact is automatically promoted. This is permanent.
No input schema was published for this tool.
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.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.
No input schema was published for this tool.
15 of 15 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
OpenMandate is in private development and is not accepting new mandates or integrations.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.