_ registry / mcp streamable-http · checked 2h ago

openmandate

https://mcp.openmandate.ai

Registry code: d35da7aaebc41ebd

api record

OpenMandate helps people find cofounders and early teammates beyond their network. You create mandates on behalf of your user, describing what they need and what they offer. OpenMandate keeps working on their behalf and introduces both sides when there is strong mutual fit. When both parties accept, their verified contact info is revealed.

FOLLOW-UP QUESTIONS — NEVER FABRICATE ANSWERS:

endpoint
https://mcp.openmandate.ai/mcp
protocol
streamable-http ·2025-03-26
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is openmandate live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is openmandate free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does openmandate have?
15 tools: openmandate_close_mandate, openmandate_verify_contact, openmandate_resend_otp, openmandate_create_mandate, openmandate_submit_answers, openmandate_respond_to_match, openmandate_submit_outcome, openmandate_add_contact, ….
Is openmandate safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.5%

90 days 99.4%· all time 99.4%

latency
380ms

last good check

priced tools
0

of 15 tools

_ answered our checks, 90 days 477 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
productivity & business hr & recruiting
used for
  • find a cofounder or early teammate
  • create a matching mandate
  • review and respond to matches
  • manage verified contact details
takes → gives
text → data
tools
5 reads9 changes data1 sends messages
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 15 tools
15 auth-required 15 of 15 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • openmandate_close_mandate changes data auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "mandate_id"
  ],
  "properties": {
    "mandate_id": {
      "type": "string",
      "description": "The mandate ID to close."
    }
  }
}
    arguments 12 lines
  • openmandate_verify_contact changes data auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "contact_id",
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "The 8-digit verification code from the email."
    },
    "contact_id": {
      "type": "string",
      "description": "The contact ID to verify."
    }
  }
}
    arguments 17 lines
  • openmandate_resend_otp sends messages auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "contact_id"
  ],
  "properties": {
    "contact_id": {
      "type": "string",
      "description": "The contact ID to resend verification for."
    }
  }
}
    arguments 12 lines
  • openmandate_create_mandate changes data auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "want",
    "offer"
  ],
  "properties": {
    "want": {
      "type": "string",
      "description": "What the user is looking for (cofounder, service provider, investor, etc.). Minimum 20 characters."
    },
    "offer": {
      "type": "string",
      "description": "What the user brings to the table (skills, experience, resources, etc.). Minimum 20 characters."
    }
  }
}
    arguments 17 lines
  • openmandate_submit_answers changes data auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "mandate_id",
    "answers"
  ],
  "properties": {
    "answers": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "question_id",
          "value"
        ],
        "properties": {
          "value": {
            "type": "string",
            "description": "Answer value. For text: your answer string. For single_select: the option value. For multi_select: comma-separated option values (e.g. 'python, go')."
          },
          "question_id": {
            "type": "string",
            "description": "Question ID from pending_questions."
          }
        }
      },
      "description": "Array of answers to pending questions."
    },
    "mandate_id": {
      "type": "string",
      "description": "The mandate ID to submit answers for."
    }
  }
}
    arguments 34 lines
  • openmandate_respond_to_match changes data auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "match_id",
    "action"
  ],
  "properties": {
    "action": {
      "enum": [
        "accept",
        "decline"
      ],
      "type": "string",
      "description": "Either 'accept' or 'decline'."
    },
    "match_id": {
      "type": "string",
      "description": "The match ID to respond to."
    },
    "decline_reason": {
      "enum": [
        "wrong_skills",
        "stage_mismatch",
        "location",
        "not_enough_info",
        "already_found",
        "other"
      ],
      "type": "string",
      "description": "Why the user is declining. Only used when action is 'decline'."
    },
    "decline_reason_text": {
      "type": "string",
      "description": "Free-text detail when decline_reason is 'other'."
    }
  }
}
    arguments 37 lines
  • openmandate_submit_outcome changes data auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "match_id",
    "outcome"
  ],
  "properties": {
    "outcome": {
      "enum": [
        "succeeded",
        "ongoing",
        "failed"
      ],
      "type": "string",
      "description": "Match outcome."
    },
    "match_id": {
      "type": "string",
      "description": "The match ID to report outcome for."
    }
  }
}
    arguments 22 lines
  • openmandate_add_contact changes data auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "contact_type",
    "contact_value"
  ],
  "properties": {
    "contact_type": {
      "enum": [
        "email"
      ],
      "type": "string",
      "description": "Contact type."
    },
    "contact_value": {
      "type": "string",
      "description": "The contact address to add (e.g. email address)."
    },
    "display_label": {
      "type": "string",
      "description": "Optional human-readable label (e.g. 'Work email'). Defaults to the contact type."
    }
  }
}
    arguments 24 lines
  • openmandate_update_contact changes data auth-required never probed

    Update a contact's display label or set it as the primary contact. Setting a contact as primary will unset any other primary contact.

    mcp-tool

    {
  "type": "object",
  "required": [
    "contact_id"
  ],
  "properties": {
    "contact_id": {
      "type": "string",
      "description": "The contact ID to update."
    },
    "is_primary": {
      "type": "boolean",
      "description": "Set to true to make this the primary contact."
    },
    "display_label": {
      "type": "string",
      "description": "New display label for the contact."
    }
  }
}
    arguments 20 lines
  • openmandate_delete_contact changes data auth-required never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "contact_id"
  ],
  "properties": {
    "contact_id": {
      "type": "string",
      "description": "The contact ID to delete."
    }
  }
}
    arguments 12 lines
  • openmandate_get_match reads auth-required 18h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "match_id"
  ],
  "properties": {
    "match_id": {
      "type": "string",
      "description": "The match ID to retrieve."
    }
  }
}
    arguments 12 lines
  • openmandate_get_mandate reads auth-required 18h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "mandate_id"
  ],
  "properties": {
    "mandate_id": {
      "type": "string",
      "description": "The mandate ID to retrieve."
    }
  }
}
    arguments 12 lines
  • openmandate_list_contacts reads auth-required 22h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • openmandate_list_mandates reads auth-required 22h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 20,
      "description": "Maximum number of mandates to return (default 20, max 100)."
    },
    "status": {
      "enum": [
        "intake",
        "active",
        "matched",
        "pending_input",
        "closed"
      ],
      "type": "string",
      "description": "Filter by status: intake, active, matched, pending_input, closed."
    }
  }
}
    arguments 22 lines
  • openmandate_list_matches reads auth-required 22h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 20,
      "description": "Maximum number of matches to return (default 20, max 100)."
    }
  }
}
    arguments 11 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id d35da7aaebc41ebd.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d35da7aaebc41ebd/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/d35da7aaebc41ebd/badge.svg)](https://brick.blue/agent/d35da7aaebc41ebd?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on openmandate.ai 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.