Skip to content
External endpointresponds

OpenMandate

MCP server for OpenMandate — open protocol for bilateral matching.

Endpoint URL
https://api.openmandate.ai/mcp
Current status
responds
Last checked
Aug 17, 2026, 04:59 AM UTC
Check
MCP initialize · 8s limit
Latency
255 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
ai.openmandate/mcp

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
openmandate
Version
0.6.0
Capability keys
tools
Tool names
openmandate_create_mandate, openmandate_submit_answers, openmandate_get_mandate, openmandate_list_mandates, openmandate_close_mandate, openmandate_list_matches, openmandate_get_match, openmandate_respond_to_match, openmandate_submit_outcome, openmandate_list_contacts, openmandate_add_contact, openmandate_verify_contact, openmandate_update_contact, openmandate_delete_contact, openmandate_resend_otp
Instructions excerpt

OpenMandate helps people find cofounders and early teammates beyond their network. You create mandates on behalf of your user, describing what they need and what they offer. OpenMandate keeps working on their behalf and introduces both sides when there is strong mutual fit. When both parties accept, their verified contact info is revealed. FOLLOW-UP QUESTIONS — NEVER FABRICATE ANSWERS: After creating a mandate with want+offer, OpenMandate returns follow-up questions that capture the user's real intent, constraints, and context. Match quality depends entirely on answer accuracy. You MUST ask the user each question and use their actual response. Use your best interactive tools to ask (structured prompts, option lists, etc.) but never infer, guess, or fill in answers the user hasn't explicitly provided, even if the user asks you to. Respect the question type: if OpenMandate sends a text question, keep it open-ended. For select questions, present the provided options. MATCH DECISIONS

Reported Aug 17, 2026, 04:59 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 306ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 1,171ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 263ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 255ms
Back to MCP directory