Cursor Eod MCP Server

@techhalo/cursor-eod-mcp npm v1.0.13

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

Trust grade
D
65/100
Last scanned
Trust
D · 65/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.
D Why this grade 100 − 35.1 = 65/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
−33 Hardcoded Slack token in server code ×2 MTC-SRC-008 exfiltration
−2.1 Package has no source repository MTC-SUP-011 supply-chain

Grade capped: 2 confirmed high findings → grade capped at D. A hard gate overrides the point total — no amount of clean surface buys back a confirmed catastrophe.

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 Hardcoded Slack token in server code (test-config.js)MTC-SRC-008

A live-looking Slack token is hardcoded in `test-config.js:9`. Secrets in source ship to everyone who installs the package and are a direct credential leak.

Evidence: Slack token: xoxb…(redacted)

Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.

Location: server test-config.js

high Hardcoded Slack token in server code (test-mcp-server.js)MTC-SRC-008

A live-looking Slack token is hardcoded in `test-mcp-server.js:158`. Secrets in source ship to everyone who installs the package and are a direct credential leak.

Evidence: Slack token: xoxb…(redacted)

Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.

Location: server test-mcp-server.js

high Shell/command execution in server code (test-mcp-protocol.js)MTC-SRC-002

In the server's implementation (`test-mcp-protocol.js:8`): 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 test-mcp-protocol.js

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

In the server's implementation (`test-mcp-server.js:8`): 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 test-mcp-server.js

low Package has no source repositoryMTC-SUP-011

"@techhalo/cursor-eod-mcp" declares no repository URL, so its published artifact cannot be compared against reviewable source.

Fix: Prefer packages that link to public, reviewable source.

Location: package @techhalo/cursor-eod-mcp

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

Use the free API → How scoring works

More in Productivity & Workflow