Sinataoke Cn MCP Server

@liuliang520500/sinataoke_cn npm v2.0.9

Published by @liuliang520500 — 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
73/100
Last scanned
Trust
C · 73/100
How safe the published surface and source look. Deterministic; every point is auditable.
Capability
Minimal
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 − 27 = 73/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
−27 Obfuscated / encoded payload in server code ×3 MTC-SRC-004 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 3

high Obfuscated / encoded payload in server code (dist/cli.js)MTC-SRC-004

In the server's implementation (`dist/cli.js:2`): Decoding an encoded blob and executing it is how malicious logic is hidden from human review of the source. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: \x35\x4f\x36\x69\x35\x50\x32\x64\x36\x41\x51\x6d\x36\x6b\x2b\x62\x36\x79\x63\x41\x36\x6c\x2b\x68

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

high Obfuscated / encoded payload in server code (dist/index.js)MTC-SRC-004

In the server's implementation (`dist/index.js:2`): Decoding an encoded blob and executing it is how malicious logic is hidden from human review of the source. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: \x62\x69\x7a\x5f\x73\x63\x65\x6e\x65\x5f\x69\x64

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

high Obfuscated / encoded payload in server code (dist/smithery.js)MTC-SRC-004

In the server's implementation (`dist/smithery.js:1`): Decoding an encoded blob and executing it is how malicious logic is hidden from human review of the source. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: \x61\x62\x63\x64\x65\x66\x67\x68\x69\x6a\x6b\x6c\x6d\x6e\x6f\x70\x71\x72\x73\x74\x75\x76\x77\x78\x79\x7a\x41\x42\x43\x44\x45\x46\x47\x48\x49\x4a\x4b\x4c\x4d\x4e

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/smithery.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
v2.0.9 latest C 73/100 3 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 · 73/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/liuliang520500-sinataoke-cn/badge.svg)](https://mcptrustchecker.com/registry/liuliang520500-sinataoke-cn)
HTML
<a href="https://mcptrustchecker.com/registry/liuliang520500-sinataoke-cn"><img src="https://mcptrustchecker.com/registry/liuliang520500-sinataoke-cn/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/liuliang520500-sinataoke-cn/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 @liuliang520500/sinataoke_cn --online

Use the free API → How scoring works

More in Marketing & Social