Ulinkly MCP Server

@ulinkly/mcp-server npm v0.1.17

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

Trust grade
C
71/100
Last scanned
Trust
C · 71/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.
C Why this grade 100 − 28.7 = 71/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
−22 Hardcoded JSON Web Token in server code MTC-SRC-008 exfiltration
−6.7 Possible combosquat of mcp ×4 MTC-SUP-006 supply-chain

Grade capped: 1 confirmed high finding → grade capped at C. 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 6

high Hardcoded JSON Web Token in server code (dist/auth/oauth.js)MTC-SRC-008

A live-looking JSON Web Token is hardcoded in `dist/auth/oauth.js:173`. Secrets in source ship to everyone who installs the package and are a direct credential leak.

Evidence: JSON Web Token: eyJh…(redacted)

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

Location: server dist/auth/oauth.js

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

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

medium Possible combosquat of mcpMTC-SUP-006

"@ulinkly/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 @ulinkly/mcp-server

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

"@ulinkly/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 @ulinkly/mcp-server

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

"@ulinkly/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 @ulinkly/mcp-server

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

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

Use the free API → How scoring works

More in Marketing & Social