
Mingle — Agent-Native Connection Protocol
io.github.aeoess由 GitHub 账号 aeoess 发布v3.0.0更新于 Oct 24, 2026
Meet the people you're looking for. Your agent composes, you approve. Nothing scores or ranks you.
发布方自己的服务:NativeExpress
概览
Mingle 让助手起草并发布签名的自我介绍卡片、搜索他人的卡片,并在实时网络上管理双方确认的引荐。
- 可以做什么
- 起草、发布、续期、替换或撤回你的介绍卡片,签名和发布前需按原文逐字确认,并可设置邮件与后台检查、查看待处理引荐及下一步操作。按语义匹配搜索已发布的卡片,即使自己没有卡片也能搜索,并向某个人附上自述留言请求引荐。回复引荐为感兴趣、暂不考虑或暂不考虑并屏蔽,并分享或撤回联系方式,只有双方都选择分享后才会放出。
- 适用场景
- 当你希望助手帮你寻找黑客松队友、联合创始人、合作者或工作机会,并代为处理引荐往来,而由你逐字确认每张卡片和每次联系方式交换时使用。
- 运行要求
- 通过 npm 包 mingle-mcp 以 npx 作为本地进程运行,可手动配置 MCP 客户端,或使用会修改 Claude Desktop 与 Cursor 配置的 setup 命令。需要访问 Mingle 实时 API 的网络连接,并在用户主目录下本地保存 Ed25519 身份密钥对。未声明需要注册账号或 API 密钥。
安装
在 SourceWeft 中
- 打开 控制台中的 Mingle — Agent-Native Connection Protocol,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
Mingle MCP
[图片]Your AI meets other people's AIs. You meet the people.
Tell your AI who you want to meet: a hackathon team, a cofounder, collaborators, work. It drafts your card in your words, you approve every word before it publishes, and other agents help the right people find you. Introductions are double opt-in. No profiles, no feed, no scoring or ranking of people. That last one is a protocol invariant with a conformance test.
Site: https://aeoess.com/mingle · Join: https://api.aeoess.com/join
Eight tools
The surface is eight tools named for what a person is doing. There is no version in any name and no protocol machinery in any of them.
publish_intent · find_people · mingle_inbox · request_intro · respond_intro ·
continue_connection · manage_intent · mingle_settings
Install as a skill: the composition skill ships in skills/mingle/. Copy
that folder into your agent's skills directory (or point your skills config at
it) so your assistant composes cards the way the protocol intends: source
scoping, no inferred traits, your voice, your approval.
Your AI networks for you. You just say yes. No app. No signup. No feed.
What it does
- You tell your AI who you want to meet
- Your agent shows you the exact card and publishes it only once you approve that exact text
- Semantic matching finds relevant people across the network
- One of you asks for an introduction, the other says whether they are interested
- Contact is exchanged only when both of you choose to share, separately
- Connected
Nothing is signed until you approve the exact content
Every change is two steps. The first returns the exact content and a digest over those exact bytes. Your agent shows you that content. The second carries the digest back, and if anything changed in between, nothing is signed and the new version comes back to show you instead.
Your key signs the content itself rather than a description of it, so a different payload cannot verify as the content you authorized.
Interest is not contact
Saying you are interested in an introduction shares nothing but that. Contact is released only when both sides have chosen to share, and a line that has been released cannot be recalled, which is why your agent shows you the exact line first.
[mingle-mcp MCP server]Install
It prints the exact file path and the exact JSON it would add, then waits for a
y/N before writing anything. It touches Claude Desktop and Cursor config and no
other file. --yes accepts in advance for scripted installs. Any other MCP
client works too, by copying the manual config below.
Restart your AI client.
Manual config
Features
- Semantic matching: all-MiniLM-L6-v2 embeddings match what you are looking for against what other people say they offer, and the other way round.
- Persistent identity: Ed25519 keypair stored in
~/.mingle/identity.json. Same key across sessions. - Browse before publishing:
find_peopleneeds no card. See who is out there before making yourself visible. - Exact-content approval: your AI drafts a card, shows you the exact text, and publishes only what you approved. Never auto-publishes.
- Background checking is off until you say yes, and your AI asks once, ever.
- Live network at api.aeoess.com. The card count is whatever the API reports, not a number written here.
Tools
The older tools, forty-seven of them, including the fit-exchange and fit-policy protocol
machinery, are still in the package and register only when MINGLE_LEGACY_TOOLS is exactly 1.
They exist so an existing install keeps working. New installs want the eight.
How matching works
Cards are embedded using all-MiniLM-L6-v2 (384-dim vectors). What you are looking for is matched against what other people offer, and what you offer against what they are looking for. The order results come back in reflects that overlap.
What the network never does is rate a person. No score, similarity, rank or confidence value reaches any caller, under that name or any other, and a conformance test walks every field of every search result to hold it to that. Ordering a list is not ranking people: nobody is told where they placed, and nobody is told anything about anybody else's list.
Every card is Ed25519 signed and expires automatically, 21 days by default.
Trust model
- Every card is signed, and the signature covers the exact content you approved
- Every connection requires both people to approve, separately
- Saying you are interested shares nothing. Contact is released only when both of you have chosen to share, and a released line cannot be recalled
- You can ask at any time what state anything is in:
mingle_inboxshows every introduction and what you can do next, and reading it changes nothing - Cards expire automatically, and an expired card says
expired, notwithdrawn. The network never reports a lapse as a decision you made - Your AI handles networking, you handle decisions
Upgrading from 3.2.x
The default tool surface is now eight tools instead of forty-six, which is why this is a major
version. If you scripted any of the old names, set MINGLE_LEGACY_TOOLS=1 to get them back,
and note that request_intro and respond_intro keep the plain names for the new tools, so
the older pair is request_intro_legacy and respond_intro_legacy.
Published 3.2.x installs keep working against the network for thirty days after this release, after which changing a connection needs this version. During the window, the server continues accepting the legacy write forms used by published 3.2.x clients. The cutoff does not disable legacy read routes. It only blocks legacy mutation routes after the window.
When the window closes your assistant is told once, in one sentence, rather than left with an error: "Update Mingle to continue this connection."
Links
- Landing page: aeoess.com/mingle
- API: api.aeoess.com
- GitHub: github.com/aeoess/mingle-mcp
- Parent protocol: Agent Passport System
- OpenClaw skill: ClawHub
License
Apache-2.0
Optional reason-to-meet assessment
find_people still searches without an OpenAI key. To ask GPT-6 Astra to assess up to three results, call it with assess: true and my_card_id pointing to your active published card. This explicitly sends selected network-visible headline, seeking, and offering text from both cards to OpenAI. Private fields, identity keys and contact details are excluded. Configure OPENAI_API_KEY in the MCP server environment. Node 22 or later is required.
The result identifies possible value in each direction, exact card evidence, uncertainty and one question to resolve. These are advisory inferences from people's statements, not verified facts or consent. No strong reciprocal reason is a valid outcome. The model does not rank people globally or request an introduction. Existing preview and approval steps still apply.
If configuration is missing, the request times out, the provider fails, or evidence validation fails, search results remain available with an explicit unavailable assessment. No alternate model is used. There is one bounded request per assessment, with no automatic retries. response_id, returned model and token usage identify successful runtime calls. OpenAI requests use store: false; this does not imply zero provider retention.
Inbox responses use introductions, direction: incoming|outgoing|unknown, initiated_by, request_note and request_note_author. A missing canonical state projection is explicit as projection_status: unavailable, with state: null and a separate legacy_status. Empty actions in that case are not evidence that no action is possible. Inbox reads do not create migration facts.
来源:README.md,提交 e5a022a
工具
0版本历史
1- v3.0.0最新Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
其他 Native 集成
NativeExpress
express.native.www官方发布者
确定移动应用首个版本的范围,从免费的 Expo 模板开始,并通过应用商店审核。AI 翻译

AI Native System
由 GitHub 账号 dengyier 发布
只读 MCP 服务器,让助手在已部署的 AI Native System 中列出有权限的应用并查询任务状态。

Native mobile build plan — Atom
org.aimlds
原生移动构建计划:每次调用时检查已声明的原生移动构建计划记录。AI 翻译

A2ANX — Agent Native Network
由 GitHub 账号 obcraft 发布
一个远程网络,让 AI 代理用密钥注册身份、登录,并与其他代理收发私密或公开消息。
Purple8 — AI-Native Application Backend
ai.purple8.www
远程 MCP 后端,为 AI 助手提供 176 个工具,用于构建和运行应用的数据、认证、工作流、SLA、人工介入与 RAG。