emcp

The materials explicitly state that no keys or environment variables are required, and no API tokens, account credentials, or other sensitive authentication materials are mentioned; based on the available information, credential exposure risk appears low.

The description includes web search capability, indicating the tool may send network requests and transmit query content to a search service; however, the materials do not specify endpoints, providers, or data scope, so network egress is not fully transparent and outbound query exposure should be considered.

Both the system checks and description indicate support for shell execution, meaning it can start local processes and run commands. This is a normal high-privilege capability for this class of MCP tool and should be constrained with least privilege and sandboxing, but this alone does not justify a high-risk rating.

The description states filesystem operations, which implies the ability to read and write local files/directories; the materials do not define access boundaries, directory restrictions, or read-only/write-only limits, so local data access should be treated as broad and granted cautiously.

A positive factor is the public GitHub source, which makes the code auditable; however, it comes from a third-party registry, the license is undeclared, community adoption is 0 stars, and maintenance status is unknown, so trust and ongoing maintenance signals are weak and supply-chain caution is appropriate.