MCP server for DeepL translation API
Nothing to run from here
OpenMandate is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
15
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
MCP server for OpenMandate — open protocol for bilateral matching.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http openmandate-mcp https://api.openmandate.ai/mcp
# 2 — ask your agent for something these tools do
# openmandate_create_mandate, openmandate_submit_answers, openmandate_get_mandate and 12 more
OpenMandate costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
AOAll 1 server
api.openmandate.ai1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, read from the address; if the publisher says otherwise, swap that one word.
claude mcp add --scope user --transport http openmandate-mcp https://api.openmandate.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| want | string | yes | What the user is looking for (cofounder, service provider, investor, etc.). Minimum 20 characters. |
| offer | string | yes | What the user brings to the table (skills, experience, resources, etc.). Minimum 20 characters. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mandate_id | string | yes | The mandate ID to submit answers for. |
| answers | array | yes | Array of answers to pending questions. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mandate_id | string | yes | The mandate ID to retrieve. |
List the user's open mandates. Returns non-closed mandates by default. Pass status to filter (e.g. status='closed' for history).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Filter by status: intake, active, matched, pending_input, closed. |
| limit | integer | no | Maximum number of mandates to return (default 20, max 100). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mandate_id | string | yes | The mandate ID to close. |
List matches for the authenticated user. Returns matches with compatibility grade, strengths, and concerns. Check this periodically after a mandate becomes active.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Maximum number of matches to return (default 20, max 100). |
Get detailed information about a specific match, including compatibility grade, strengths, concerns, and — if both parties accepted — the counterparty's contact information.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| match_id | string | yes | The match ID to retrieve. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| match_id | string | yes | The match ID to respond to. |
| action | string | yes | Either 'accept' or 'decline'. |
| decline_reason | string | no | Why the user is declining. Only used when action is 'decline'. |
| decline_reason_text | string | no | Free-text detail when decline_reason is 'other'. |
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 mandat
| Parameter | Type | Required | Notes |
|---|---|---|---|
| match_id | string | yes | The match ID to report outcome for. |
| outcome | string | yes | Match outcome. |
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 parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_type | string | yes | Contact type. |
| contact_value | string | yes | The contact address to add (e.g. email address). |
| display_label | string | no | Optional human-readable label (e.g. 'Work email'). Defaults to the contact type. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_id | string | yes | The contact ID to verify. |
| code | string | yes | The 8-digit verification code from the email. |
Update a contact's display label or set it as the primary contact. Setting a contact as primary will unset any other primary contact.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_id | string | yes | The contact ID to update. |
| display_label | string | no | New display label for the contact. |
| is_primary | boolean | no | Set to true to make this the primary contact. |
Delete a contact. If the deleted contact was primary, the next verified contact is automatically promoted. This is permanent.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_id | string | yes | The contact ID to delete. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_id | string | yes | The contact ID to resend verification for. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install OpenMandate or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.6.0.
0.6.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish OpenMandate can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.