OpenMandate

OpenMandate is in private development and is not accepting new mandates or integrations.

Should I use this

Quality & Safety

A
Description quality
99%
Schema completeness
94%
Naming quality
100%
Poisoning risk
80%
Permission match
100%
Protocol compliance
100%

Findings (2)

  • HIGHTool poisoning patterns detected
  • MEDIUMTool description contains URL to non-standard domainin openmandate_create_mandate

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~2,040Tokens (tool definitions)
~771 BTypical response size
Moderate attention impact (1.59% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "mcp": {
      "url": "https://api.openmandate.ai/mcp"
    }
  }
}

Remote endpoints

https://api.openmandate.ai/mcpstreamable-http
https://mcp.openmandate.ai/mcpstreamable-http

What it can do

Tool inventory

Tools (15)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟡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.

Input Schema

{
  "type": "object",
  "properties": {
    "want": {
      "type": "string",
      "description": "What the user is looking for (cofounder, service provider, investor, etc.). Minimum 20 characters."
    },
    "offer": {
      "type": "string",
      "description": "What the user brings to the table (skills, experience, resources, etc.). Minimum 20 characters."
    }
  },
  "required": [
    "want",
    "offer"
  ]
}
🟡openmandate_submit_answers(mandate_id, answers)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "mandate_id": {
      "type": "string",
      "description": "The mandate ID to submit answers for."
    },
    "answers": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "question_id": {
            "type": "string",
            "description": "Question ID from pending_questions."
          },
          "value": {
            "type": "string",
            "description": "Answer value. For text: your answer string. For single_select: the option value. For multi_select: comma-separated option values (e.g. 'python, go')."
          }
        },
        "required": [
          "question_id",
          "value"
        ]
      },
      "description": "Array of answers to pending questions."
    }
  },
  "required": [
    "mandate_id",
    "answers"
  ]
}
🟢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.

Input Schema

{
  "type": "object",
  "properties": {
    "mandate_id": {
      "type": "string",
      "description": "The mandate ID to retrieve."
    }
  },
  "required": [
    "mandate_id"
  ]
}
🟢openmandate_list_mandates(status, limit)

List the user's open mandates. Returns non-closed mandates by default. Pass status to filter (e.g. status='closed' for history).

Input Schema

{
  "type": "object",
  "properties": {
    "status": {
      "type": "string",
      "description": "Filter by status: intake, active, matched, pending_input, closed.",
      "enum": [
        "intake",
        "active",
        "matched",
        "pending_input",
        "closed"
      ]
    },
    "limit": {
      "type": "integer",
      "description": "Maximum number of mandates to return (default 20, max 100).",
      "default": 20
    }
  },
  "required": []
}
🔴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.

Input Schema

{
  "type": "object",
  "properties": {
    "mandate_id": {
      "type": "string",
      "description": "The mandate ID to close."
    }
  },
  "required": [
    "mandate_id"
  ]
}
🟢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.

Input Schema

{
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "description": "Maximum number of matches to return (default 20, max 100).",
      "default": 20
    }
  },
  "required": []
}
🟢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.

Input Schema

{
  "type": "object",
  "properties": {
    "match_id": {
      "type": "string",
      "description": "The match ID to retrieve."
    }
  },
  "required": [
    "match_id"
  ]
}
⚪openmandate_respond_to_match(match_id, action, 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.

Input Schema

{
  "type": "object",
  "properties": {
    "match_id": {
      "type": "string",
      "description": "The match ID to respond to."
    },
    "action": {
      "type": "string",
      "description": "Either 'accept' or 'decline'.",
      "enum": [
        "accept",
        "decline"
      ]
    },
    "decline_reason": {
      "type": "string",
      "description": "Why the user is declining. Only used when action is 'decline'.",
      "enum": [
        "wrong_skills",
        "stage_mismatch",
        "location",
        "not_enough_info",
        "already_found",
        "other"
      ]
    },
    "decline_reason_text": {
      "type": "string",
      "description": "Free-text detail when decline_reason is 'other'."
    }
  },
  "required": [
    "match_id",
    "action"
  ]
}
🟡openmandate_submit_outcome(match_id, outcome)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "match_id": {
      "type": "string",
      "description": "The match ID to report outcome for."
    },
    "outcome": {
      "type": "string",
      "description": "Match outcome.",
      "enum": [
        "succeeded",
        "ongoing",
        "failed"
      ]
    }
  },
  "required": [
    "match_id",
    "outcome"
  ]
}
🟢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.

Input Schema

{
  "type": "object",
  "properties": {},
  "required": []
}
🟡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.

Input Schema

{
  "type": "object",
  "properties": {
    "contact_type": {
      "type": "string",
      "description": "Contact type.",
      "enum": [
        "email"
      ]
    },
    "contact_value": {
      "type": "string",
      "description": "The contact address to add (e.g. email address)."
    },
    "display_label": {
      "type": "string",
      "description": "Optional human-readable label (e.g. 'Work email'). Defaults to the contact type."
    }
  },
  "required": [
    "contact_type",
    "contact_value"
  ]
}
🟢openmandate_verify_contact(contact_id, code)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "contact_id": {
      "type": "string",
      "description": "The contact ID to verify."
    },
    "code": {
      "type": "string",
      "description": "The 8-digit verification code from the email."
    }
  },
  "required": [
    "contact_id",
    "code"
  ]
}
🟡openmandate_update_contact(contact_id, display_label, is_primary)

Update a contact's display label or set it as the primary contact. Setting a contact as primary will unset any other primary contact.

Input Schema

{
  "type": "object",
  "properties": {
    "contact_id": {
      "type": "string",
      "description": "The contact ID to update."
    },
    "display_label": {
      "type": "string",
      "description": "New display label for the contact."
    },
    "is_primary": {
      "type": "boolean",
      "description": "Set to true to make this the primary contact."
    }
  },
  "required": [
    "contact_id"
  ]
}
🔴openmandate_delete_contact(contact_id)

Delete a contact. If the deleted contact was primary, the next verified contact is automatically promoted. This is permanent.

Input Schema

{
  "type": "object",
  "properties": {
    "contact_id": {
      "type": "string",
      "description": "The contact ID to delete."
    }
  },
  "required": [
    "contact_id"
  ]
}
⚪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.

Input Schema

{
  "type": "object",
  "properties": {
    "contact_id": {
      "type": "string",
      "description": "The contact ID to resend verification for."
    }
  },
  "required": [
    "contact_id"
  ]
}

Recommended Prompts

retrieve_data
Get details about [item] from OpenMandate
Expected tools: openmandate_get_mandate
fetch_info
Fetch [information type] using OpenMandate
Expected tools: openmandate_get_mandate
list_items
List all [items] available in OpenMandate
Expected tools: openmandate_list_mandates
browse_collection
Show me the [collection] from OpenMandate
Expected tools: openmandate_list_mandates
explore_workflow
List available [items], then get details for each one using OpenMandate
Expected tools: openmandate_list_mandatesopenmandate_get_mandate

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded15 tools
verifiedversion not recorded15 tools
verifiedversion not recorded15 tools
verifiedversion not recorded15 tools