npm JavaScript analyzed 1.0.127

@runsec/mcp

v1.0.127
npm

RunSec MCP server rewritten in TypeScript.

maintainer
runsec
licence
MIT
first seen
2026-06-02
last seen
2026-06-16
releases · 30d
0
short id
risk 27/100 · heuristic grade
B low inferred analyzer v33 (current)
  • capability exposure inferred + 35
  • trust mitigators mixed − 8

inferred mixed

The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.

grade last moved 1w ago · see ecosystem CVEs →

risk trajectory 4 movements
  • B · 24 B · 27
  • B · 32 B · 24
  • C · 47 B · 32
  • C · 59 C · 47
capability exposure grade factor +35
Inferred surface — each links to servers holding it:
vulnerabilities 0 CVEs

No known CVEs for this server.

tool safety all quiet

No tool-safety findings — heuristic detectors run on the compute-risk cadence; a finding appears when a tool trips a rule.

skills & danger signals npm-tarball
prompt-surface shipped agent-instruction files + hidden-content / dangerous-code findings — quoted from the analyzed source

analyzed v1.0.127 · analyzer v33 · 4w ago

danger signals1

  • suspicious endpoint 169.254.169.254 (cloud metadata) package/dist/index.js :7539 'curl -i --max-time 3 "http://169.254.169.254/latest/meta-data/"'
embed badge readme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/npm:@runsec/mcp/badge.svg)](https://mcpobservatory.com/servers/npm:@runsec/mcp/security)

Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of runsec.