B-

mcp.openmandate.ai

Item: mcp.openmandate.ai
Rating: 80
Author: wmcp.sh

https://mcp.openmandate.ai/mcp

80/100 · MCP Trust Grade · checked 4h ago · MCP 2025-03-26

✓ Watched since 2026-06-03 — behavioral baseline locked. We re-check this server's tool surface on a schedule; if it adds, removes, or silently rewrites a tool (rug-pull), we record it.

What it offers — 15 tools · Developer Tools

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 contact

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,

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 retrie

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_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 with

openmandate_list_matches

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

openmandate_get_match

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

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 mat

openmandate_submit_outcome

Report how a confirmed match went. Available after both parties accepted and contact info was revealed. Outcomes: - 'succeeded': Found the right perso

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 lab

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_veri

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 u

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_delete_contact

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

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 l

Spec conformance20%80

✓ initialize → protocolVersion 2025-03-26
✓ initialize HTTP 200
✗ unknown method → -32600
✓ tools/list → 15 tools
✓ every tool has name + inputSchema

Security (OWASP MCP)30%100

15 tools scanned
no injection markup
no secret-path refs

Reliability / performance20%70

single-probe latency 2916ms (PRELIMINARY — continuous uptime/p95 from proxy telemetry lands in v2)

Tool hygiene15%66

93% of tools have typed inputSchema
0/15 declare outputSchema
2 destructive-by-name tools lack safety annotations

Transparency / provenance15%70

HTTPS ✓
advertises protocol 2025-03-26

Observed behavior

No proxied traffic observed for this host yet. Connect it at /connect and its grade gains a measured Reliability score + per-tool behavioral evidence — the half a static scan can't produce.

Findings

No blocking issues found in the static + spec checks.

Grade another server

We re-grade mcp.openmandate.ai on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — mcp.openmandate.ai grade B-

Share on X Open card image

https://wmcp.sh/mcp/grade/mcp.openmandate.ai

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade B-](https://wmcp.sh/mcp/grade/mcp.openmandate.ai/badge.svg)](https://wmcp.sh/mcp/grade/mcp.openmandate.ai)

HTML

<a href="https://wmcp.sh/mcp/grade/mcp.openmandate.ai"><img src="https://wmcp.sh/mcp/grade/mcp.openmandate.ai/badge.svg" alt="MCP Trust Grade B- · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.