OpenMandate MCP Server

by openmandate Your server? Claim it

answering

OpenMandate is answering right now. Last checked 5 min ago. It exposes 15 tools.

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

Uptime history 91 days of history · worst day 98%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

505 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check OpenMandate every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://mcp.openmandate.ai/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.openmandate.ai/mcp

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 15

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

openmandate

openmandate_add_contact

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.

openmandate_close_mandate

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.

openmandate_create_mandate

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.

openmandate_delete_contact

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

openmandate_get_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.

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.

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.

openmandate_list_mandates

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

openmandate_list_matches

List matches for the authenticated user. Returns matches with compatibility grade, strengths, and concerns. Check this periodically after a mandate becomes active.

openmandate_resend_otp

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.

openmandate_respond_to_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.

openmandate_submit_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.

openmandate_submit_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.

openmandate_update_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.

openmandate_verify_contact

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.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.openmandate.ai/mcp	streamable-http	answering	650 ms	5 min ago

Alternatives to OpenMandate

same job, measured the same way

Ezeep

by ezeep

Cloud printing integration for AI-assisted app development via ezeep.

answering

Ramp

by mcparmory

Manage expenses, corporate cards, accounts payable, and accounting integrations

222 installs/wk local only

BANKSapi Docs

by banksapi

Search and read the BANKSapi developer docs and OpenAPI specs for Open Banking integrations.

4 tools answering

BuildData

by builddata-api

Canadian building permits, development and planning applications, major projects, new businesses.

answering

Avalara Developer Documentation

by avalara

Provides access to Avalara developer documentation, integration guides, and code examples

answering

Development Indicators MCP

by lbruce-wq

Open-source MCP for official development indicators with provenance and citations.

10 tools answering

Copilot MCP

by vomeshatukuri

MCP server for web development with Khoros, Gainsight, and HigherLogic integrations.

1 tools answering

Zapier Dev MCP

by arose26

For Zapier integration developers: inspect, lint, and validate zapier-platform-cli projects.

67 installs/wk local only

OpenMandate — questions

Answers built from our own checks of this server.

What can OpenMandate do?

It exposes 15 tools, read directly from the server on our last check. Among them: openmandate_add_contact, openmandate_close_mandate, openmandate_create_mandate, openmandate_delete_contact, openmandate_get_mandate, openmandate_get_match and 9 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is OpenMandate working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 505 ms. The bar chart above shows every period we have measured.

How do I connect OpenMandate?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does OpenMandate need an API key?

No. OpenMandate completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 15 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is OpenMandate?

It answers our handshake in 505 ms on average, which is faster than 24% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.