Kitty Hive MCP Server

kitty-hive npm v0.7.14 Source verified

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

MCP server for multi-agent collaboration — DM, tasks, workflow, federation

Trust grade
C
79/100
Last scanned get badge →
Trust
C · 79/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
C Why this grade threat 89 − adoption risk = 79/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 − 11 = 89. What the published surface and source actually contain:

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

2. Client adoption risk — 89 − 10 = 79. 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 9

high Shell/command execution in server code (codex-channel.ts)MTC-SRC-002

In the server's implementation (`codex-channel.ts:36`): 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: ildProcess } from 'node:child_process'; import { execSync } from 'node:child_process'; import { createServer } 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 codex-channel.ts

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

In the server's implementation (`dist/codex-supervisor.js:29`): 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 { existsSync } from 'node:fs'; import { dirname, join, resolve } from 'no

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/codex-supervisor.js

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

In the server's implementation (`dist/index.js:12`): 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 { buildPushMessage } from './preview.js'; import { AGENT_EVENT_MODES } fr

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/index.js

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

In the server's implementation (`dist/opencode-supervisor.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: ync, spawn } from 'node:child_process'; import { existsSync } from 'node:fs'; import { dirname, join } from 'node:path';

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/opencode-supervisor.js

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

In the server's implementation (`dist/tunnel.js:5`): 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 { existsSync } from 'node:fs'; const URL_REGEX = /https:\/\/[a-z0-9-]+\.t

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/tunnel.js

high Shell/command execution in server code (opencode-channel.ts)MTC-SRC-002

In the server's implementation (`opencode-channel.ts:13`): 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: ildProcess } from 'node:child_process'; import { createServer, type Server as HttpServer } from 'node:http'; import { cr

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 opencode-channel.ts

medium Untrusted input concatenated into a command sink (codex-channel.ts)MTC-SRC-009

In the server's implementation (`codex-channel.ts:100`): 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: EX_CMD set) try { execSync(`${CODEX_CMD} --version`, { stdio: 'pipe' }); } catch { console.error(`[codex-cha

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 codex-channel.ts

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

In the server's implementation (`dist/index.js:378`): 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(`${codex} mcp add hive --url ${url}`, { stdio: 'pipe' }); return { 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/index.js

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

In the server's implementation (`dist/tunnel.js:16`): 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: const out = execSync(`where ${name}`, { encoding: 'utf8' }).trim().split(/\r?\n/)[0]; if (ou

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/tunnel.js

Tools 35

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

  • hive_file_fetchingests untrusted input
  • hive_inboxingests untrusted input
  • hive_agentsno sensitive capability
  • hive_checkno sensitive capability
  • hive_codex_pane_wsno sensitive capability
  • hive_dmno sensitive capability
  • hive_dm_readno sensitive capability
  • hive_opencode_pane_serverno sensitive capability
  • hive_peersno sensitive capability
  • hive_remote_agentsno sensitive capability
Show 25 more tools ↓
  • hive_renameno sensitive capability
  • hive_startno sensitive capability
  • hive_taskno sensitive capability
  • hive_task_cancelno sensitive capability
  • hive_task_claimno sensitive capability
  • hive_task_completeno sensitive capability
  • hive_tasksno sensitive capability
  • hive_team_createno sensitive capability
  • hive_team_eventsno sensitive capability
  • hive_team_infono sensitive capability
  • hive_team_joinno sensitive capability
  • hive_team_leaveno sensitive capability
  • hive_team_listno sensitive capability
  • hive_team_messageno sensitive capability
  • hive_team_rename_nicknameno sensitive capability
  • hive_team_set_rulesno sensitive capability
  • hive_teamsno sensitive capability
  • hive_update_roleno sensitive capability
  • hive_whoamino sensitive capability
  • hive_workflow_approveno sensitive capability
  • hive_workflow_proposeno sensitive capability
  • hive_workflow_rejectno sensitive capability
  • hive_workflow_step_approveno sensitive capability
  • hive_workflow_step_completeno sensitive capability
  • hive-whoamino sensitive capability

What this scan could not see

Versions 4

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.7.14 latest C 79/100 9 1.13.0 2026-09-07
v0.7.12 C 79/100 9 1.12.1 2026-08-03
v0.7.11 C 79/100 9 1.12.1 2026-07-28
v0.7.10 C 79/100 9 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: C · 79/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/kitty-hive/badge.svg)](https://mcptrustchecker.com/registry/kitty-hive)
HTML
<a href="https://mcptrustchecker.com/registry/kitty-hive"><img src="https://mcptrustchecker.com/registry/kitty-hive/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/kitty-hive/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 kitty-hive --online

Use the free API → How scoring works

More in AI & Agents