4da MCP Server

@4da/mcp-server npm v4.6.6

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

Trust grade
B
87/100
Last scanned
Trust
B · 87/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.
B Why this grade 100 − 13 = 87/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
−6.7 Possible combosquat of mcp ×4 MTC-SUP-006 supply-chain
−6.3 Untrusted input concatenated into a command sink 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 8

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

In the server's implementation (`dist/project-scanner.js:80`): 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 dist/project-scanner.js

medium Hardcoded egress to an external endpoint (dist/embeddings.js)MTC-SRC-003

In the server's implementation (`dist/embeddings.js:160`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch("https://api.openai.com/v1/embeddings"

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

medium Hardcoded egress to an external endpoint (dist/llm.js)MTC-SRC-003

In the server's implementation (`dist/llm.js:229`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch("https://api.anthropic.com/v1/messages"

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

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

In the server's implementation (`dist/db.js:719`): 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 dist/db.js

medium Possible combosquat of mcpMTC-SUP-006

"@4da/mcp-server" is "mcp" with a decorative suffix — a common combosquat pattern.

Fix: Confirm you meant "mcp". Install packages only from their documented, official name.

Location: package @4da/mcp-server

medium Possible combosquat of @playwright/mcpMTC-SUP-006

"@4da/mcp-server" is "@playwright/mcp" with a decorative suffix — a common combosquat pattern.

Fix: Confirm you meant "@playwright/mcp". Install packages only from their documented, official name.

Location: package @4da/mcp-server

medium Possible combosquat of @stripe/mcpMTC-SUP-006

"@4da/mcp-server" is "@stripe/mcp" with a decorative suffix — a common combosquat pattern.

Fix: Confirm you meant "@stripe/mcp". Install packages only from their documented, official name.

Location: package @4da/mcp-server

medium Possible combosquat of @browsermcp/mcpMTC-SUP-006

"@4da/mcp-server" is "@browsermcp/mcp" with a decorative suffix — a common combosquat pattern.

Fix: Confirm you meant "@browsermcp/mcp". Install packages only from their documented, official name.

Location: package @4da/mcp-server

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
v4.6.6 latest B 87/100 8 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: B · 87/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/4da-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/4da-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/4da-mcp-server"><img src="https://mcptrustchecker.com/registry/4da-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/4da-mcp-server/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 @4da/mcp-server --online

Use the free API → How scoring works

More in Lifestyle & Local