Openprovider MCP Server

The materials explicitly state that no keys or environment variables are required, and no API token, password, or other credential request is shown. Based on the available materials, there is no clear credential collection or abuse red flag; however, because the claimed functionality involves Openprovider account actions, the actual authentication model remains unclear due to missing documentation.

As an MCP server for checking, registering, and managing domains, it would normally need to communicate with Openprovider-related online services, which is standard network egress for this class of tool. The materials also say there is no remote endpoint, creating an information gap versus the stated functionality; however, there is no specific evidence of data being sent to unrelated or unknown third-party endpoints.

The system checks explicitly indicate that this tool executes code/spawns processes, which is a normal characteristic of MCP tools and not by itself a high-risk indicator. The current materials do not disclose its exact system capabilities, subprocess scope, or sandboxing constraints, so the local execution surface should be treated with caution.

From the description, the tool mainly operates on domains, contacts, and related account resources rather than explicitly targeting the local filesystem; the materials also do not claim access to sensitive local directories or broad data collection. Because there is no README or permission documentation, the actual scope of access to local data, config files, or conversation content cannot be confirmed.

Positive signals include a public GitHub repository and an MIT open-source license, making the project theoretically auditable; this should materially lower the risk rating. Points to watch are that it comes from a third-party registry, currently shows 0 stars, has unknown maintenance status, and lacks documentation, so supply-chain maturity and ongoing maintenance signals are weak.