mingle
MCP serverAI & modelsMeet the people you're looking for. Your agent composes, you approve. Nothing scores or ranks you.
This server has no hosted endpoint yet, so ahel can't serve it. You can still add it. It stays paused until ahel can serve it.
Serve it through your gateway
One link, every agent. Your own credentials, stored once.
Tools it gives your agents (44)
| Tool | What it does |
|---|---|
| publish_intent_card | Publish your profile to the Mingle network — what you're looking for and what you can offer. Cards are Ed25519 signed with your persistent identity and expire after 48h. |
| search_matches | Find people relevant to you on the Mingle network. Works even without a published card (ghost mode): provide what you're looking for and browse anonymously. |
| get_digest | Check the Mingle v3 network for your published cards: new matches since you last looked (as overlap maps, never scores), how many introductions await your response, and any card expiring soon. |
| request_intro | Reach out to someone you matched with on Mingle. Send a message explaining why you'd be a good connection. Nothing personal crosses until both sides say yes. |
| respond_to_intro | Respond to an introduction on Mingle. Someone's AI reached out because they think you'd be a good match. Approve to connect, decline to pass. No details shared unless both sides say yes. |
| remove_intent_card | Remove your card from the Mingle network. Your identity and connection history are preserved. Publish a fresh card anytime. |
| rate_connection | Rate a connection you made through Mingle. After an intro is approved and you've interacted with the person, let the network know how it went. This helps improve matching for everyone. |
| compose_connection_card | Step 1 of publishing. Build the exact card the principal approves. Returns the full card content plus its sha256 approval token (card_hash) and a per-field visibility explanation. |
| publish_connection_card | Step 2 of publishing. Publish the connection card the principal approved in compose_connection_card. |
| compose_opportunity_card | Step 1 of publishing. Build the exact card the principal approves. Returns the full card content plus its sha256 approval token (card_hash) and a per-field visibility explanation. |
| publish_opportunity_card | Step 2 of publishing. Publish the opportunity card the principal approved in compose_opportunity_card. |
| search_cards | Search Mingle v3 cards by explicit fields (card_type, intents, topics, engagement, location, event_ref) and, when a query is given, semantic similarity over published card text. |
| withdraw_card | Withdraw a v3 card from the network. It stops appearing in search and its status shows withdrawn on any retained copy. |
| supersede_claims | Mark a v3 card superseded (its claims are replaced by a newer card). Status shows superseded. |
| revoke_agent_authority | Revoke all future agent authority tied to a v3 card. The card leaves search and its status shows authority_revoked. |
| delete_server_copy | Ask the server to delete its stored copy of a v3 card. Content is blanked; status shows deleted. Counterparties may retain what they already received. |
| stop_new_matches | Stop new matches against a v3 card without withdrawing it. Status shows stopped_new_matches. |
| request_counterparty_deletion | Ask counterparties who received your card to delete their copy. Phase 2 feature; not yet active. Counterparties may retain what they already received. |
| get_card_status | Show the current server status of the v3 cards you have published (adapts the digest to v3 card types). Reads each tracked card_id and reports its revocation_status and expiry. |
| renew_card | Renew one of your Mingle v3 cards before it expires: re-sign the exact same content with a fresh expiry, which supersedes the old version. |
| set_notifications | Turn Mingle email notifications on or off. Your email is stored server-side for notifications only, verified by a confirmation link before anything sends, never shown to anyone or placed on any... |
| request_intro_v3 | Ask to be introduced to a Mingle v3 card found via search_cards. Two steps, like publishing a card: the first call returns a preview of exactly what will be sent (your card, the target, the purpose... |
| list_intros | List your Mingle v3 introductions: incoming requests awaiting your response (with purpose and note), your outgoing requests, and completed introductions (with the other side's contact line, released... |
| respond_intro | Respond to an incoming Mingle v3 intro request. action=accept shares a contact line with the other side (two steps: the first call previews the exact line and shares nothing; call again with the... |
| complete_intro | Complete a Mingle v3 intro you requested, after the other side accepted. Sharing your contact line here releases both contacts to each other (theirs to you, yours to them) and to no one else. |
| set_disclosures | Set your Mingle disclosure ledger: a list of discrete, concrete statements you are willing to share inside a fit exchange (for example 'I can commit 20 hours a week' or 'I have cofounded once before') |
| get_fit_exchange | Show a Mingle fit exchange for the principal: its state, your answers so far, the other person's answers, any custom questions, and the consent sheet. |
| answer_fit | Answer a Mingle fit exchange. Call with no answers to get the drafting context: the platform questions and your OWN approved ledger items. |
| request_more | Ask for more in a Mingle fit exchange. round2 marks up to 3 existing questions as 'tell me more' for the other side. |
| close_fit | Close a Mingle fit exchange and assemble its record. Either side can close; the exchange also closes automatically after 72 hours. |
| get_fit_record | Show the signed record of a closed Mingle fit exchange: per question, both sides' verbatim answers and a deterministic status. |
| set_fit_policy | Set your private Fit Policy for a card: a list of typed dimensions (weekly_commitment, start_window, time_horizon, timezone, cadence, project_stage, relationship_shape, role_spike... |
| prioritize_candidates | Order a candidate pool LOCALLY by your own Fit Policy, for the principal only. The network never ranks people; this ordering happens entirely in this tool, is never sent to the server, never... |
| request_fit_handshake | Open a bilateral fit handshake for an accepted intro by sending a Fit Request Manifest: the dimensions you want to check and the dimensions you will symmetrically reveal in return. |
| commit_fit_handshake | Commit to a fit handshake the other side requested: accept the dimensions you agree to have checked and offer matching reciprocity. |
| get_fit_handshake | Show a fit handshake for the principal: its state and, once both sides have committed, the overlap map (distinct facts) and the signed receipt. |
| reveal_dimension | Release the exact value of one of YOUR dimensions to the other party in a fit handshake, on the principal's tap. |
| answer_fit_v4 | Answer the unresolved fit questions after a handshake. Call with no answers to get the questions (the unresolved dimensions, capped at four); draft each answer from the principal's own words and... |
| request_more_v4 | Ask the other side for more on up to 3 fit dimensions (tell-me-more). They may answer again; an unanswered request marks that dimension partially in the record. |
| set_fit_autonomy | Set a scoped standing autonomy for a card: which intents and dimensions your agent may handle without asking each time, and to what tier. |
| pause_fit_autonomy | Pause or resume all autonomous fit disclosure for a card. While paused, nothing discloses without the principal's per-match approval, whatever the standing scope says. |
| get_fit_activity | Show the principal a legible 'while you were away' summary of automatic fit activity for a card: how many cards were evaluated, how many people an overlap was disclosed to and on which dimensions... |
| propose_first_step | Propose your half of a First Step: a short plan for the first real conversation, drafted from the principal's OWN words only (purpose, next_action, meeting_length, agenda, each_wants, boundaries... |
| approve_first_step | Approve the shared First Step plan (both halves together). Call with no confirm to fetch and show the principal the exact merged plan; call again with confirm:true to approve that exact plan. |
Signals
- GitHub stars
- 6
- Forks
- 2
- Last commit
- Jul 2026
- Weekly downloads
- 113
- Tools captured
- 44