Yade MCP

Detected

• Runs shell commands7 places

  Spawns processes on your machine. Expected for command, browser and build tools.

• Loads code at runtime10 places

  Uses eval, dynamic imports or encoded payloads, which static review cannot fully follow.

• Reads local configuration files3 places

  Loads a .env, .npmrc or config file. Normal for a server that needs an API key.

• Contains instructions aimed at AI agents1 places

  Text in code or agent-facing files that steers a model. Worth reading before you trust it.

• Runs unpinned packages at runtime2 places

  Executes npx or uvx without a version, so a compromised upstream release would run.

Not detected: reads environment variables in bulk, sends conversation content outward, reads or writes other agents' configuration, accesses credential files, uses elevated privileges, installs itself to run later, matches a known malicious pattern.

Dependencies with known advisories

None found in the lockfiles and manifests checked against OSV.dev.

Left out of the profile

4 pattern matches in documentation, configuration or CI files were recorded but are not part of the profile, because they do not run when the server does. The owner dashboard lists them.