Productivity

openmandate.ai

Manage mandates by creating, submitting answers, retrieving, listing, and closing them.

1 endpoint15 known toolsFirst detected May 10, 2026Last detected August 29, 2026

ENDPOINT 1

https://mcp.openmandate.ai/mcp

No auth detected

MCP server metadata

Name: openmandate
Version: 0.6.0

Capabilities

tools

Server instructions

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 — ALWAYS CONFIRM WITH USER: Accepting a match reveals the user's verified contact info to a third party. Declining is permanent. Always show the user the match details and get explicit confirmation before responding. VERIFIED CONTACTS: Contact info must be verified before it can be revealed on match. The user's login email is auto-verified. Additional contacts can be added via openmandate_list_contacts and the Settings page at https://openmandate.ai/settings. The user's primary verified contact is automatically attached to new mandates. Workflow: 1. openmandate_create_mandate — describe what user wants and offers 2. openmandate_submit_answers — answer follow-up questions 3. openmandate_list_matches — check for matches once active 4. openmandate_get_match — review match details with user 5. openmandate_respond_to_match — accept/decline with user's confirmation 6. openmandate_submit_outcome — report how it went after connecting Useful tools: - openmandate_list_contacts — view user's verified contacts - openmandate_list_mandates — view user's mandates API keys: https://openmandate.ai/api-keys

Known tools 15

openmandate_create_mandate

Create a new mandate on OpenMandate.

Potential side effects

openmandate_submit_answers

Submit the user's answers to pending intake questions.

Inferred read-only

openmandate_get_mandate

Get a mandate by ID.

Inferred read-only

openmandate_list_mandates

List the user's open mandates.

Inferred read-only

openmandate_close_mandate

Close (withdraw) a mandate.

Inferred read-only

openmandate_list_matches

List matches for the authenticated user.

Inferred read-only

openmandate_get_match

Get detailed information about a specific match, including compatibility grade, strengths, concerns, and — if both parties accepted — the counterparty's contact information.

Inferred read-only

openmandate_respond_to_match

Accept or decline a match.

Inferred read-only

openmandate_submit_outcome

Report how a confirmed match went.

Inferred read-only

openmandate_list_contacts

List the user's verified contacts.

Inferred read-only

openmandate_add_contact

Add a new contact for the user.

Inferred read-only

openmandate_verify_contact

Verify a contact by submitting the OTP code sent to it.

Inferred read-only

openmandate_update_contact

Update a contact's display label or set it as the primary contact.

Potential side effects

openmandate_delete_contact

Delete a contact.

Potential side effects

openmandate_resend_otp

Resend the verification code for a pending contact.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.openmandate]
url = "https://mcp.openmandate.ai/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "openmandate": {
      "type": "http",
      "url": "https://mcp.openmandate.ai/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: openmandate
Remote MCP URL: https://mcp.openmandate.ai/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "openmandate": {
      "type": "http",
      "url": "https://mcp.openmandate.ai/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "openmandate",
  "transport": "streamable-http",
  "url": "https://mcp.openmandate.ai/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.