USPTO Patents

The materials explicitly state that no keys or environment variables are required. There is no indication of API tokens, account credentials, or other sensitive authentication data being requested, so credential exposure and abuse risk appears low.

The tool connects to the declared endpoint uspto-patents-mcp.atlasword.workers.dev to provide patent search functionality, which means query content may be sent to a remote service. The materials do not detail the exact data transmitted or privacy handling, so users should assume their inputs may leave the local environment.

System checks indicate that this MCP executes code or launches a local process, which is a common operational pattern for MCP tools. The materials do not show requests for unusual system privileges or clearly unrelated high-risk actions, so this is best rated as caution rather than risk.

The available materials do not specify what local files or data it reads or writes, nor any persistence scope; however, as an executable MCP, it should be treated under least-privilege assumptions. There is no explicit sign of overbroad access requests, but the data access boundary is insufficiently documented.

Positive factors include an official registry source, an open-source repository, and updates within the past year, all of which reduce supply-chain risk. Remaining concerns are the missing README, undeclared license, and low community adoption (0 stars), which limit maturity and practical audit confidence.