Iconnect MCP Server

iconnect-mcp npm v0.1.1 Source verified

Published by heznpc — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Trust grade
B
84/100
Last scanned get badge →
Trust
B · 84/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Critical
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
B Why this grade threat 94 − adoption risk = 84/100

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 − 6.3 = 94. What the published surface and source actually contain:

PointsWhat was foundCategory
−6.3 Untrusted input concatenated into a command sink MTC-SRC-009 injection

2. Client adoption risk — 94 − 10 = 84. 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:

PointsAdoption-risk factor
−10 capability blast radius (critical) — client exposure if the model is manipulated

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 8

critical Completed toxic-flow trifecta across toolsMTC-FLOW-002

This server (without client built-ins) exposes a complete data-exfiltration chain: get_unread_count → list_directory → send_file. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.

Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.

Location: flow get_unread_count → list_directory → send_file

high Shell/command execution in server code (dist/cli/doctor.js)MTC-SRC-002

In the server's implementation (`dist/cli/doctor.js:9`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: { execSync } from "node:child_process"; import { MODULE_NAMES, STARTER_MODULES, NPM_PACKAGE_NAME } from "../shared/confi

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/cli/doctor.js

high Shell/command execution in server code (dist/shared/jxa.js)MTC-SRC-002

In the server's implementation (`dist/shared/jxa.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: { execFile } from "node:child_process"; import { promisify } from "node:util"; const execFileAsync = promisify(execFile)

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/shared/jxa.js

high Shell/command execution in server code (dist/shared/swift.js)MTC-SRC-002

In the server's implementation (`dist/shared/swift.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: rt { spawn } from "node:child_process"; import { access } from "node:fs/promises"; import { resolve, dirname } from "nod

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/shared/swift.js

medium Untrusted input concatenated into a command sink (dist/cli/doctor.js)MTC-SRC-009

In the server's implementation (`dist/cli/doctor.js:117`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try { execSync(`osascript -l JavaScript -e "Application('${appName}'); JSON.stringify({ok:true})"`, {

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/cli/doctor.js

medium Tool "move_file" can modify the filesystemMTC-CAP-002

Tool "move_file" can write, overwrite or delete files (keyword "move_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool move_file

low Mutating tool "move_file" declares no destructiveHintMTC-CAP-005

Tool "move_file" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool move_file

low Unconstrained path parameter "path" on "list_directory"MTC-CAP-008

Tool "list_directory" takes a path parameter "path" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.

Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.

Location: tool list_directory · inputSchema.properties.path

Tools 124

Each tool and what it can reach — statically extracted from the published source.

  • get_unread_countingests untrusted input
  • list_directoryreads sensitive data
  • move_filewrites files
  • read_messageingests untrusted input
  • send_filenetwork egress
  • send_messagenetwork egress
  • activate_tabno sensitive capability
  • add_contact_emailno sensitive capability
  • add_contact_phoneno sensitive capability
  • add_to_albumno sensitive capability
Show 114 more tools ↓
  • bulk_move_notesno sensitive capability
  • capture_screenshotno sensitive capability
  • close_tabno sensitive capability
  • compare_notesno sensitive capability
  • complete_reminderno sensitive capability
  • create_albumno sensitive capability
  • create_contactno sensitive capability
  • create_directoryno sensitive capability
  • create_eventno sensitive capability
  • create_folderno sensitive capability
  • create_noteno sensitive capability
  • create_recurring_eventno sensitive capability
  • create_recurring_reminderno sensitive capability
  • create_reminderno sensitive capability
  • create_reminder_listno sensitive capability
  • delete_contactno sensitive capability
  • delete_eventno sensitive capability
  • delete_noteno sensitive capability
  • delete_photosno sensitive capability
  • delete_reminderno sensitive capability
  • delete_reminder_listno sensitive capability
  • find_relatedno sensitive capability
  • flag_messageno sensitive capability
  • get_clipboardno sensitive capability
  • get_current_tabno sensitive capability
  • get_file_infono sensitive capability
  • get_frontmost_appno sensitive capability
  • get_photo_infono sensitive capability
  • get_screen_infono sensitive capability
  • get_shortcut_detailno sensitive capability
  • get_track_infono sensitive capability
  • get_upcoming_eventsno sensitive capability
  • get_volumeno sensitive capability
  • get_workflowno sensitive capability
  • import_photono sensitive capability
  • list_accountsno sensitive capability
  • list_albumsno sensitive capability
  • list_calendarsno sensitive capability
  • list_chatsno sensitive capability
  • list_contactsno sensitive capability
  • list_eventsno sensitive capability
  • list_favoritesno sensitive capability
  • list_foldersno sensitive capability
  • list_group_membersno sensitive capability
  • list_groupsno sensitive capability
  • list_mailboxesno sensitive capability
  • list_messagesno sensitive capability
  • list_notesno sensitive capability
  • list_participantsno sensitive capability
  • list_photosno sensitive capability
  • list_playlistsno sensitive capability
  • list_reminder_listsno sensitive capability
  • list_remindersno sensitive capability
  • list_running_appsno sensitive capability
  • list_shortcutsno sensitive capability
  • list_tabsno sensitive capability
  • list_tracksno sensitive capability
  • mark_message_readno sensitive capability
  • move_messageno sensitive capability
  • move_noteno sensitive capability
  • now_playingno sensitive capability
  • open_urlno sensitive capability
  • play_playlistno sensitive capability
  • play_trackno sensitive capability
  • playback_controlno sensitive capability
  • proofread_textno sensitive capability
  • read_chatno sensitive capability
  • read_contactno sensitive capability
  • read_eventno sensitive capability
  • read_noteno sensitive capability
  • read_page_contentno sensitive capability
  • read_reminderno sensitive capability
  • recent_filesno sensitive capability
  • reply_mailno sensitive capability
  • rewrite_textno sensitive capability
  • run_javascriptno sensitive capability
  • run_shortcutno sensitive capability
  • scan_notesno sensitive capability
  • search_chatsno sensitive capability
  • search_contactsno sensitive capability
  • search_eventsno sensitive capability
  • search_filesno sensitive capability
  • search_messagesno sensitive capability
  • search_notesno sensitive capability
  • search_photosno sensitive capability
  • search_remindersno sensitive capability
  • search_shortcutsno sensitive capability
  • search_tabsno sensitive capability
  • search_tracksno sensitive capability
  • semantic_indexno sensitive capability
  • semantic_searchno sensitive capability
  • semantic_statusno sensitive capability
  • send_mailno sensitive capability
  • set_clipboardno sensitive capability
  • set_file_tagsno sensitive capability
  • set_shuffleno sensitive capability
  • set_volumeno sensitive capability
  • setup_permissionsno sensitive capability
  • show_notificationno sensitive capability
  • summarize_contextno sensitive capability
  • summarize_textno sensitive capability
  • today_eventsno sensitive capability
  • toggle_dark_modeno sensitive capability
  • trash_fileno sensitive capability
  • tv_list_playlistsno sensitive capability
  • tv_list_tracksno sensitive capability
  • tv_now_playingno sensitive capability
  • tv_playno sensitive capability
  • tv_playback_controlno sensitive capability
  • tv_searchno sensitive capability
  • update_contactno sensitive capability
  • update_eventno sensitive capability
  • update_noteno sensitive capability
  • update_reminderno 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

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.

VersionScoreFindingsEngineScanned
v0.1.1 latest B 84/100 8 1.10.0 2026-07-25

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.

MCP Trust Score: B · 84/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/iconnect-mcp/badge.svg)](https://mcptrustchecker.com/registry/iconnect-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/iconnect-mcp"><img src="https://mcptrustchecker.com/registry/iconnect-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/iconnect-mcp/badge.json via https://img.shields.io/endpoint?url=…

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 iconnect-mcp --online

Use the free API → How scoring works

More in Developer Tools