# OpenMandate (remote · mcp.openmandate.ai)

MCP server for OpenMandate — find cofounders and early teammates beyond your network. 15 tools.

- Trust score: 74/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.openmandate.ai`: 74/100 (this document), [markdown](https://verifymcp.io/servers/ai-openmandate-mcp/mcp.md), [page](https://verifymcp.io/servers/ai-openmandate-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.openmandate.ai/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.6.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1711 tokens (~114/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-openmandate-mcp": {
      "type": "remote",
      "url": "https://mcp.openmandate.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-openmandate-mcp --url https://mcp.openmandate.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-openmandate-mcp:
    url: "https://mcp.openmandate.ai/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 73, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-29 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 67)

First indexed and scored.

## MCP tools (15)

### `openmandate_create_mandate` (~175 tokens)

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 parameters:

- `offer` (string, required): What the user brings to the table (skills, experience, resources, etc.). Minimum 20 characters.
- `want` (string, required): What the user is looking for (cofounder, service provider, investor, etc.). Minimum 20 characters.

### `openmandate_submit_answers` (~109 tokens)

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 parameters:

- `answers` (array, required): Array of answers to pending questions.
- `mandate_id` (string, required): The mandate ID to submit answers for.

### `openmandate_get_mandate` (~62 tokens)

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 parameters:

- `mandate_id` (string, required): The mandate ID to retrieve.

### `openmandate_list_mandates` (~84 tokens)

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

Input parameters:

- `limit` (integer): Maximum number of mandates to return (default 20, max 100).
- `status` (string): Filter by status: intake, active, matched, pending_input, closed.

### `openmandate_close_mandate` (~57 tokens)

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 parameters:

- `mandate_id` (string, required): The mandate ID to close.

### `openmandate_list_matches` (~59 tokens)

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

Input parameters:

- `limit` (integer): Maximum number of matches to return (default 20, max 100).

### `openmandate_get_match` (~54 tokens)

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

Input parameters:

- `match_id` (string, required): The match ID to retrieve.

### `openmandate_respond_to_match` (~114 tokens)

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 parameters:

- `action` (string, required): Either 'accept' or 'decline'.
- `decline_reason` (string): Why the user is declining. Only used when action is 'decline'.
- `decline_reason_text` (string): Free-text detail when decline_reason is 'other'.
- `match_id` (string, required): The match ID to respond to.

### `openmandate_submit_outcome` (~124 tokens)

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 parameters:

- `match_id` (string, required): The match ID to report outcome for.
- `outcome` (string, required): Match outcome.

### `openmandate_list_contacts` (~45 tokens)

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_add_contact` (~117 tokens)

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 parameters:

- `contact_type` (string, required): Contact type.
- `contact_value` (string, required): The contact address to add (e.g. email address).
- `display_label` (string): Optional human-readable label (e.g. 'Work email'). Defaults to the contact type.

### `openmandate_verify_contact` (~76 tokens)

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 parameters:

- `code` (string, required): The 8-digit verification code from the email.
- `contact_id` (string, required): The contact ID to verify.

### `openmandate_update_contact` (~81 tokens)

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 parameters:

- `contact_id` (string, required): The contact ID to update.
- `display_label` (string): New display label for the contact.
- `is_primary` (boolean): Set to true to make this the primary contact.

### `openmandate_delete_contact` (~47 tokens)

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

Input parameters:

- `contact_id` (string, required): The contact ID to delete.

### `openmandate_resend_otp` (~68 tokens)

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 parameters:

- `contact_id` (string, required): The contact ID to resend verification for.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-openmandate-mcp/mcp#diagnostics

## Score history

- 2026-08-03: 74
- 2026-08-02: 74
- 2026-08-01: 73
- 2026-07-31: 73
- 2026-07-30: 70
- 2026-07-29: 69
- 2026-07-28: 68
- 2026-07-27: 68
- 2026-07-26: 67

## Links

- Remote endpoint: https://mcp.openmandate.ai/mcp
- Authorisation metadata: https://mcp.openmandate.ai/.well-known/oauth-protected-resource/mcp
- Website: https://openmandate.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-openmandate-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-openmandate-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-openmandate-mcp/mcp