Mingle — Agent-Native Connection Protocol
NPM · MINGLE-MCP · SCANNED SEP 22
Meet the people you're looking for. Your agent composes, you approve. Nothing scores or ranks you.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security83
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects uuid 9.0.1, reached via agent-passport-system > uuid. A fixed version is available. View diagnostics → Fail
- Runs a script at install time (postinstall) that we could not recognise. It may be perfectly ordinary, but we do not read the published tarball, so we cannot say what it does. View diagnostics → Partial
- 34 of 106 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 6 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1644 tokens (~86/item across 19 items; 19 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 66% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "publish_intent_card" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Mingle — Agent-Native Connection Protocol MCP server?
Mingle — Agent-Native Connection Protocol runs locally as an npm package, launched with npx -y mingle-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mingle-mcp
claude mcp add aeoess-mingle -- npx -y mingle-mcp
{
"mcpServers": {
"aeoess-mingle": {
"command": "npx",
"args": [
"-y",
"mingle-mcp"
]
}
}
} {
"servers": {
"aeoess-mingle": {
"command": "npx",
"args": [
"-y",
"mingle-mcp"
]
}
}
} codex mcp add aeoess-mingle -- npx -y mingle-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"aeoess-mingle": {
"type": "local",
"command": [
"npx",
"-y",
"mingle-mcp"
],
"enabled": true
}
}
} openclaw mcp add aeoess-mingle --command npx --arg -y --arg mingle-mcp
mcp_servers:
aeoess-mingle:
command: "npx"
args: ["-y", "mingle-mcp"] {
"McpServers": {
"aeoess-mingle": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mingle-mcp"
]
}
}
} assistant mcp add aeoess-mingle -t stdio -c npx -a -y mingle-mcp
{
"mcpServers": {
"aeoess-mingle": {
"command": "npx",
"args": [
"-y",
"mingle-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Sept 26 0
- Stability: 0.97 → pass security
- 21 Sept 26 +1
- Security disclosure: unverified → pass ▲ functional
- 20 Sept 26 0
- Security disclosure: pass → unverified ▼ functional
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Analysed npm/mingle-mcp@3.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | unreviewed | echo '\n🤝 Mingle installed! Run: npx mingle-mcp setup\n' |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-p7fg-763f-g4gf | CVE-2026-41686 | medium | yes | |
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 106 packages
| Packages resolved | 106 |
|---|---|
| Deprecated | 1 |
| Stale | 33 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compose_connection_card ~185
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. Nothing is published. Show the rendered card to the principal, then call the matching publish tool echoing card_hash back once they say yes.
| Name | Type | Req | Description |
|---|---|---|---|
| artifacts | array | – | – |
| event_ref | object | – | – |
| headline | string | yes | Headline in the principal's voice |
| intents | array | yes | – |
| offering | array | – | – |
| preferences | array | – | Explicit self-declared values only, never inferred traits |
| seeking | array | – | – |
| team_size_sought | integer | – | – |
| ttl_days | integer | – | Days until auto-expiry (default 21) |
| visibility | object | – | Per-field audience; unlisted content fields default to network |
No output schema declared.
No examples provided.
compose_opportunity_card ~186
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. Nothing is published. Show the rendered card to the principal, then call the matching publish tool echoing card_hash back once they say yes.
| Name | Type | Req | Description |
|---|---|---|---|
| artifacts | array | – | – |
| event_ref | object | – | – |
| headline | string | yes | Headline in the principal's voice |
| intents | array | yes | – |
| offering | array | – | – |
| preferences | array | – | Explicit self-declared values only, never inferred traits |
| seeking | array | – | – |
| team_size_sought | integer | – | – |
| ttl_days | integer | – | Days until auto-expiry (default 21) |
| visibility | object | – | Per-field audience; unlisted content fields default to network |
No output schema declared.
No examples provided.
delete_server_copy ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| card_id | string | yes | The v3 card_id to act on |
No output schema declared.
No examples provided.
get_card_status ~48
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_digest ~41
Check what's happening on the Mingle network for you. Returns pending intro requests, top matches, and card status. Call this at session start to surface anything important.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
publish_connection_card ~77
Step 2 of publishing. Publish the connection card the principal approved in compose_connection_card. Requires the exact card object and the approved_hash returned by compose; a mismatch is refused so only approved content is published.
| Name | Type | Req | Description |
|---|---|---|---|
| approved_hash | string | yes | The card_hash the principal approved |
| card | – | – | The exact card object returned by compose |
No output schema declared.
No examples provided.
publish_intent_card ~163
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. Returns your top matches immediately.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Rich context for better matching (private — never shown to others) |
| hours | number | – | Hours until card expires (default 48) |
| name | string | yes | Your name or alias |
| needs | array | – | What you're looking for (plain text list) |
| offers | array | – | What you can provide (plain text list) |
| open_to | array | – | Open to (e.g. 'introductions', 'partnerships') |
| topic | string | – | What you're working on (short summary) |
No output schema declared.
No examples provided.
publish_opportunity_card ~79
Step 2 of publishing. Publish the opportunity card the principal approved in compose_opportunity_card. Requires the exact card object and the approved_hash returned by compose; a mismatch is refused so only approved content is published.
| Name | Type | Req | Description |
|---|---|---|---|
| approved_hash | string | yes | The card_hash the principal approved |
| card | – | – | The exact card object returned by compose |
No output schema declared.
No examples provided.
rate_connection ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | Optional: brief note on why |
| intro_id | string | yes | Intro ID of the connection to rate |
| rating | string | yes | How useful was this connection? |
No output schema declared.
No examples provided.
remove_intent_card ~45
Remove your card from the Mingle network. Your identity and connection history are preserved. Publish a fresh card anytime.
| Name | Type | Req | Description |
|---|---|---|---|
| card_id | string | yes | Card ID to remove |
No output schema declared.
No examples provided.
request_counterparty_deletion ~50
Ask counterparties who received your card to delete their copy. Phase 2 feature; not yet active. Counterparties may retain what they already received.
| Name | Type | Req | Description |
|---|---|---|---|
| card_id | string | yes | – |
No output schema declared.
No examples provided.
request_intro ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| match_id | string | yes | Match ID from search_matches |
| message | string | yes | Short message explaining why this intro would be valuable |
| to | string | yes | Agent ID of the person you want to meet |
No output schema declared.
No examples provided.
respond_to_intro ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| approve | boolean | yes | true to approve, false to decline |
| intro_id | string | yes | Intro ID from your digest |
| message | string | – | Optional response message |
No output schema declared.
No examples provided.
revoke_agent_authority ~51
Revoke all future agent authority tied to a v3 card. The card leaves search and its status shows authority_revoked.
| Name | Type | Req | Description |
|---|---|---|---|
| card_id | string | yes | The v3 card_id to act on |
No output schema declared.
No examples provided.
search_cards ~141
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. Returns network-visible fields only; private fields never appear. Relevance ordering for your own query is search, not a judgment of people.
| Name | Type | Req | Description |
|---|---|---|---|
| card_type | string | – | – |
| engagement | string | – | – |
| event_ref | string | – | – |
| intents | array | – | – |
| limit | integer | – | – |
| location | string | – | – |
| query | string | – | Free-text query for semantic ranking over published text |
| topics | array | – | – |
No output schema declared.
No examples provided.
search_matches ~127
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. Returns ranked matches based on semantic similarity between needs and offers.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | number | – | Max results (default: 15) |
| min_score | number | – | Minimum relevance score 0-1 (default: 0.3) |
| query_needs | array | – | Ghost mode: describe what you need without a published card |
| query_offers | array | – | Ghost mode: describe what you offer without a published card |
No output schema declared.
No examples provided.
stop_new_matches ~43
Stop new matches against a v3 card without withdrawing it. Status shows stopped_new_matches.
| Name | Type | Req | Description |
|---|---|---|---|
| card_id | string | yes | The v3 card_id to act on |
No output schema declared.
No examples provided.
supersede_claims ~48
Mark a v3 card superseded (its claims are replaced by a newer card). Status shows superseded.
| Name | Type | Req | Description |
|---|---|---|---|
| card_id | string | yes | The v3 card_id to act on |
No output schema declared.
No examples provided.
withdraw_card ~48
Withdraw a v3 card from the network. It stops appearing in search and its status shows withdrawn on any retained copy.
| Name | Type | Req | Description |
|---|---|---|---|
| card_id | string | yes | The v3 card_id to act on |
No output schema declared.
No examples provided.
What is the Mingle — Agent-Native Connection Protocol MCP server?
Mingle — Agent-Native Connection Protocol is an MCP server listed in the public MCP registry as io.github.aeoess/mingle. Meet the people you're looking for. Your agent composes, you approve. Nothing scores or ranks you. This page covers its npm package (mingle-mcp).
Is the Mingle — Agent-Native Connection Protocol MCP server safe to use?
Mingle — Agent-Native Connection Protocol scores 78 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 22 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Mingle — Agent-Native Connection Protocol MCP server expose?
Mingle — Agent-Native Connection Protocol exposes 19 tools: publish_intent_card, search_matches, get_digest, request_intro, respond_to_intro, and 14 more. Their descriptions and schemas cost roughly 1,644 tokens of context every time the server is loaded.
Is the Mingle — Agent-Native Connection Protocol MCP server still maintained?
Mingle — Agent-Native Connection Protocol is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Mingle — Agent-Native Connection Protocol MCP server under?
Mingle — Agent-Native Connection Protocol declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.