PkgRadar

npm · registry.npmjs.org

mcp-remote-next

Suspicious Publish Context: {"package_age_days":0,"publisher":"terry623","burst_same_day":1,"burst_week":1,"lure":{"kind":"token_affix","target":"next"},"version_anomaly":false,"new_account":false}

Why PkgRadar flagged 0.1.49

SeveritySignalEvidence
mediumSuspicious Publish Context{"package_age_days":0,"publisher":"terry623","burst_same_day":1,"burst_week":1,"lure":{"kind":"token_affix","target":"next"},"version_anomaly":false,"new_account":false}

Scanned versions

VersionVerdictScoreScanned (UTC)
0.1.49Review102026-06-15
0.1.48Review102026-06-15
0.1.47Review102026-06-15
0.1.46Review102026-06-15
0.1.45Review102026-06-15
0.1.41Review102026-06-15
0.1.40Review102026-06-15
0.1.43Review102026-06-15
0.1.42Review102026-06-15
0.1.38Review252026-06-15

Block this in CI

PkgRadar gates mcp-remote-next (and every other dependency) before it merges. One line in your pipeline:

pkgradar gate --ecosystem npm [email protected]
Start free — 25 scans / moView full evidence