Flowdot.ai MCP Server

@flowdot.ai/mcp-server npm v1.3.14

Published by @flowdot.ai — 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
93/100
Last scanned
Trust
A · 93/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 − 6.7 = 93/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

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 9

high Dynamic code execution in server code (dist/utils/script-validator.js)MTC-SRC-001

In the server's implementation (`dist/utils/script-validator.js:96`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: eval(

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/utils/script-validator.js

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

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

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

In the server's implementation (`dist/utils/script-validator.js:109`): 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/utils/script-validator.js

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

In the server's implementation (`dist/resources/index.js:2467`): 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://example.com/article'

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

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

In the server's implementation (`dist/tools/create-app.js:72`): 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://...'

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/tools/create-app.js

medium Possible combosquat of mcpMTC-SUP-006

"@flowdot.ai/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 @flowdot.ai/mcp-server

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

"@flowdot.ai/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 @flowdot.ai/mcp-server

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

"@flowdot.ai/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 @flowdot.ai/mcp-server

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

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

Use the free API → How scoring works

More in AI, Memory & Reasoning