Mydisease

The material states that no keys or environment variables are required. No API token, account password, or other sensitive credential is requested, so credential leakage and abuse exposure appears relatively low.

The tool connects to the remote endpoint gateway.pipeworx.io, so query content or user input may be sent to that service. The README is absent, so the exact transmitted fields, purpose, and data minimization controls cannot be confirmed; network egress therefore warrants caution.

System checks indicate that it executes code/spawns a process, which is a common MCP tool behavior. The available material does not show requests for unusual system privileges or actions unrelated to its stated function, but documentation is insufficient to define its exact system capability boundaries.

The provided material does not specify which local files, directories, or other resources it can read or write, so the data access scope cannot be confirmed. No explicit over-privilege red flag is shown, but because it has local execution capability, it should still be used under least-privilege assumptions.

It comes from an official registry and has a public source repository with updates within the last year, both of which meaningfully reduce risk. However, the missing README, undeclared license, and very low community adoption (0 stars) limit confidence in auditability and maturity, so supply-chain caution remains appropriate.