Skip to content

OpenMandate MCP server

ai.openmandate/mcpopenmandate.aistreamable-httpv0.6.1Scanned

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

15 tools: 2 can delete or cancel things, 1 do something that can't be undone, 7 change things and 5 only read.

Tools: 2 delete, 1 irreversible, 7 write, 5 read.
  • Reads private data · 2
  • Reads text others write · 0
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here can delete or cancel things and 1 does something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the OpenMandate MCP server can do

The OpenMandate MCP server is published by openmandate.ai, a domain the MCP Registry verified. It has 15 tools. It can delete or cancel things (2 tools: openmandate_close_mandate and openmandate_delete_contact), do things that cannot be undone, such as sending, paying or publishing (openmandate_resend_otp) and create or change data (7 tools: openmandate_create_mandate, openmandate_submit_answers, openmandate_respond_to_match, openmandate_submit_outcome and 3 more). 5 tools only read.

2 tools read private data (openmandate_get_match and openmandate_list_contacts); 1 tool can send data out of your system (openmandate_resend_otp).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 11, 2026, version 0.6.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

15 tools

Deletes or cancels 2Claude Code: deny
  • openmandate_close_mandateClose (withdraw) a mandate.No findings

    Why it is in this group

    • The name "openmandate_close_mandate" says "close": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
  • openmandate_delete_contactDelete a contact.No findings

    Why it is in this group

    • The name "openmandate_delete_contact" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete a contact. If the deleted contact was primary, the next verified contact is automatically promoted. This is permanent.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
Can't be undone 1Claude Code: ask
  • openmandate_resend_otpResend the verification code for a pending contact.Can send data outNo findings

    Why it is in this group

    • The name "openmandate_resend_otp" says "resend": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "openmandate_resend_otp" says "resend": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
Changes things 7Claude Code: ask
  • openmandate_add_contactAdd a new contact for the user.No findings

    Why it is in this group

    • The name "openmandate_add_contact" says "add": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
  • openmandate_create_mandateCreate a new mandate on OpenMandate.No findings

    Why it is in this group

    • The name "openmandate_create_mandate" says "create": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
  • openmandate_respond_to_matchAccept or decline a match.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
  • openmandate_submit_answersSubmit the user's answers to pending intake questions.No findings

    Why it is in this group

    • The name "openmandate_submit_answers" says "submit": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
  • openmandate_submit_outcomeReport how a confirmed match went.No findings

    Why it is in this group

    • The name "openmandate_submit_outcome" says "submit": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
  • openmandate_update_contactUpdate a contact's display label or set it as the primary contact.No findings

    Why it is in this group

    • The name "openmandate_update_contact" says "update": a word for a change.
    Description, as the server wrote it
    Update a contact's display label or set it as the primary contact. Setting a contact as primary will unset any other primary contact.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
  • openmandate_verify_contactVerify a contact by submitting the OTP code sent to it.No findings

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
Only reads 5Show 5 read-only tools
  • openmandate_get_mandateGet a mandate by ID.No findings

    Why it is in this group

    • The name "openmandate_get_mandate" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • openmandate_get_matchGet detailed information about a specific match, including compatibility grade, strengths, concerns, and — if both parties accepted — the counterparty's contact information.Reads private dataNo findings

    Why it is in this group

    • The name "openmandate_get_match" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "contact": it reads contacts.
    Description, as the server wrote it
    Get detailed information about a specific match, including compatibility grade, strengths, concerns, and — if both parties accepted — the counterparty's contact information.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • openmandate_list_contactsList the user's verified contacts.Reads private dataNo findings

    Why it is in this group

    • The name "openmandate_list_contacts" says "list": a word for reading.

    What it can reach

    • private-dataThe name "openmandate_list_contacts" says "list" and "contact": it reads contacts.
    • private-dataThe description's first sentence says "list" and "contact": it reads contacts.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • openmandate_list_mandatesList the user's open mandates.No findings

    Why it is in this group

    • The name "openmandate_list_mandates" says "list": a word for reading.
    Description, as the server wrote it
    List the user's open mandates. Returns non-closed mandates by default. Pass status to filter (e.g. status='closed' for history).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • openmandate_list_matchesList matches for the authenticated user.No findings

    Why it is in this group

    • The name "openmandate_list_matches" says "list": a word for reading.
    Description, as the server wrote it
    List matches for the authenticated user. Returns matches with compatibility grade, strengths, and concerns. Check this periodically after a mandate becomes active.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:27 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
10
Protocol version
2025-03-26
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 10 tools that change things (2 destructive, 1 irreversible, 7 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.openmandate.ai/mcp: tools/list returned 15 tools to an anonymous client, including openmandate_close_mandate (destructive), openmandate_delete_contact (destructive), openmandate_resend_otp (irreversible), openmandate_create_mandate (write), openmandate_submit_answers (write) and 5 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.6.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http openmandate https://mcp.openmandate.ai/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http openmandate https://mcp.openmandate.ai/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__openmandate__openmandate_get_mandate",
      "mcp__openmandate__openmandate_list_mandates",
      "mcp__openmandate__openmandate_list_matches",
      "mcp__openmandate__openmandate_get_match",
      "mcp__openmandate__openmandate_list_contacts"
    ],
    "ask": [
      "mcp__openmandate__openmandate_create_mandate",
      "mcp__openmandate__openmandate_submit_answers",
      "mcp__openmandate__openmandate_respond_to_match",
      "mcp__openmandate__openmandate_submit_outcome",
      "mcp__openmandate__openmandate_add_contact",
      "mcp__openmandate__openmandate_verify_contact",
      "mcp__openmandate__openmandate_update_contact",
      "mcp__openmandate__openmandate_resend_otp"
    ],
    "deny": [
      "mcp__openmandate__openmandate_close_mandate",
      "mcp__openmandate__openmandate_delete_contact"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as openmandate. Review it before you use it.

Capability tags behind 3 rules
  • mcp__openmandate__openmandate_get_match private-data
  • mcp__openmandate__openmandate_list_contacts private-data
  • mcp__openmandate__openmandate_resend_otp outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.openmandate/mcp/verify?hash=e3c7cb16f9b1dae4216825511549f67a3b20eb730592dd44b117698ef6cbfc64" | jq -e '.changed == false'

Pinned hash e3c7cb16f9b1, from Nov 11, 2026, 20:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.openmandate/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.openmandate/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.openmandate/mcp.svg)](https://radar.anlyon.com/servers/ai.openmandate/mcp)

Source: MCP Registry. Synced Oct 21, 2026, 17:42 UTC.

OpenMandate MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the OpenMandate MCP server safe?

No scan can promise that. What its definitions show: 15 tools, 10 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the OpenMandate MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: openmandate_close_mandate and openmandate_delete_contact.

Can the OpenMandate MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: openmandate_resend_otp.

What tools does the OpenMandate MCP server have?

15 tools: 2 destructive, 1 irreversible, 7 write, 5 read. openmandate_close_mandate, openmandate_delete_contact, openmandate_resend_otp, openmandate_create_mandate, openmandate_submit_answers, openmandate_respond_to_match, openmandate_submit_outcome, openmandate_add_contact and 7 more.

Does the OpenMandate MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the OpenMandate MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): openmandate_resend_otp.

Has the OpenMandate MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.