Mingle MCP Server
mingle-mcp
npm
v3.2.0
Published by aeoess — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Your AI meets other people's AIs. You meet the people. Agent-native networking via MCP.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 1.2 = 99. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −1.2 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
2. Client adoption risk — 99 − 4 = 95. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
low Package runs install-time scripts (postinstall)MTC-SUP-010
"mingle-mcp" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.
Evidence: echo '\n🤝 Mingle installed! Run: npx mingle-mcp setup\n'
Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.
Location: package mingle-mcp
Tools 36
Each tool and what it can reach — statically extracted from the published source.
approve_first_stepingests untrusted inputanswer_fitno sensitive capabilityanswer_fit_v4no sensitive capabilitycheck_pending_matchesno sensitive capabilityclose_fitno sensitive capabilitycommit_fit_handshakeno sensitive capabilitycomplete_introno sensitive capabilityget_card_statusno sensitive capabilityget_digestno sensitive capabilityget_fit_activityno sensitive capability
Show 26 more tools ↓
get_fit_exchangeno sensitive capabilityget_fit_handshakeno sensitive capabilityget_fit_recordno sensitive capabilitylist_introsno sensitive capabilitypause_fit_autonomyno sensitive capabilityprioritize_candidatesno sensitive capabilitypropose_first_stepno sensitive capabilitypublish_intent_cardno sensitive capabilityrate_connectionno sensitive capabilityremove_intent_cardno sensitive capabilityrenew_cardno sensitive capabilityrequest_counterparty_deletionno sensitive capabilityrequest_fit_handshakeno sensitive capabilityrequest_introno sensitive capabilityrequest_intro_v3no sensitive capabilityrequest_moreno sensitive capabilityrequest_more_v4no sensitive capabilityrespond_introno sensitive capabilityrespond_to_introno sensitive capabilityreveal_dimensionno sensitive capabilitysearch_cardsno sensitive capabilitysearch_matchesno sensitive capabilityset_disclosuresno sensitive capabilityset_fit_autonomyno sensitive capabilityset_fit_policyno sensitive capabilityset_notificationsno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (36 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 2
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v3.2.0 latest |
A 95/100 | 1 | 1.13.0 | 2026-09-08 |
v3.1.1 |
A 95/100 | 1 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan mingle-mcp --onlineMore in AI & Agents
Authenticated MCP transport with HTTP Signatures for AAuth agents
Local-first MCP server for parallel AI coding agents to claim file ownership before edits, preventing stomping on each other in the same worktree.
Agent-agnostic intercommunication system — sessions, messaging, channels, shared state, and real-time events
MCP server for AI agent task communication and delegation with diagnostic lifecycle visibility
Programmatic add/link/unlink for MCP servers across 23 AI coding agents (Claude Code, Claude Desktop, Cursor, VS Code, Codex, Gemini CLI, Zed, Cline, OpenCode, Goose, Kiro, Windsurf, and more). Functional API with dry-run support.
MCP server layer exposing agent-mesh orchestrator as an MCP agent