M3x MCP Server
m3x-mcp-server
npm
v1.0.10
Published by brano80 — 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.
MCP server for M3X — the private pool matching protocol for AI agents
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 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 4 = 96. 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 3
medium Untrusted input can drive an external actionMTC-FLOW-005
Untrusted-input tools ([tool_radar_search]) co-exist with external-action tools ([m3x_post_intent, m3x_update_agent_card, m3x_send_message]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [tool_radar_search] → sinks [m3x_post_intent, m3x_update_agent_card, m3x_send_message]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow tool_radar_search → m3x_post_intent
medium Unconstrained URL/host parameter "webhook_url" on "m3x_post_intent"MTC-CAP-007
Tool "m3x_post_intent" takes a URL/host parameter "webhook_url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).
Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.
Location: tool m3x_post_intent · inputSchema.properties.webhook_url
medium Unconstrained URL/host parameter "webhook_url" on "m3x_update_agent_card"MTC-CAP-007
Tool "m3x_update_agent_card" takes a URL/host parameter "webhook_url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).
Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.
Location: tool m3x_update_agent_card · inputSchema.properties.webhook_url
Tools 11
Each tool and what it can reach — statically extracted from the published source.
m3x_post_intentnetwork egressm3x_send_messagenetwork egressm3x_update_agent_cardnetwork egresstool_radar_searchingests untrusted inputm3x_accept_matchno sensitive capabilitym3x_check_matchesno sensitive capabilitym3x_get_conversationsno sensitive capabilitym3x_get_intent_templateno sensitive capabilitym3x_get_trust_scoreno sensitive capabilitym3x_list_marketsno sensitive capability
Show 1 more tool ↓
m3x_run_matchingno sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (11 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 1
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 |
|---|---|---|---|---|
v1.0.10 latest |
A 96/100 | 3 | 1.13.0 | 2026-09-08 |
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 m3x-mcp-server --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