Collab MCP Server

@trustbaseai/collab-mcp npm v0.18.0

Published by @trustbaseai — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.

Trust grade
A
91/100
Last scanned
Trust
A · 91/100
How safe the published surface and source look. Deterministic; every point is auditable.
Capability
High
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.
A Why this grade 100 − 9.5 = 91/100

Every server starts at 100. These are the exact deductions the deterministic engine applied — each one reproducible, none of it an opinion or an LLM's guess:

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

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 the deduction.

Findings 5

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

In the server's implementation (`src/database.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: child_process

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 src/database.js

high Shell/command execution in server code (src/service-linux.js)MTC-SRC-002

In the server's implementation (`src/service-linux.js: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: child_process

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 src/service-linux.js

high Shell/command execution in server code (src/service-windows.js)MTC-SRC-002

In the server's implementation (`src/service-windows.js: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: child_process

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 src/service-windows.js

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

In the server's implementation (`src/cli-install.js:67`): 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: exec(` CREATE TABLE IF NOT EXISTS _install_meta ( key TEXT PRIMARY KEY, value TEXT ); INSERT OR REPLACE INTO _install_meta (ke

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 src/cli-install.js

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

In the server's implementation (`src/database.js:214`): 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: exec(`ALTER TABLE ${table} ADD COLUMN ${column} ${

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 src/database.js

What this scan could not see

Versions

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.18.0 latest A 91/100 5 1.5.0 2026-07-22

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: A · 91/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/trustbaseai-collab-mcp/badge.svg)](https://mcptrustchecker.com/registry/trustbaseai-collab-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/trustbaseai-collab-mcp"><img src="https://mcptrustchecker.com/registry/trustbaseai-collab-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/trustbaseai-collab-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 @trustbaseai/collab-mcp --online

Use the free API → How scoring works

More in API Development