mcp-epo-ops

The material explicitly states that no keys or environment variables are required. No API token, account, or other sensitive credential is requested, so credential exposure surface appears low.

The stated function is to query European Patent Office patent data, which implies network access in normal use. However, no concrete remote endpoints are documented, so the egress destination and scope are not transparent and should be verified to ensure they are limited to services relevant to the stated purpose.

System checks indicate that this tool executes code. For an MCP tool, this typically means running a local service process. The provided material does not describe any additional system capabilities, so this should be treated as normal local execution risk with caution, but there is no clear red flag showing permissions beyond its stated purpose.

The material does not specify what local files, caches, or data it can read or write. As a normal MCP tool, it will at least process user queries and returned results. Because there is no README or permission description, it is not possible to confirm whether data access stays within what is necessary for patent lookup.

An open-source repository exists, which is a positive factor because the code can in principle be audited. However, the source is a third-party registry, the license is not declared, community adoption is 0 stars, maintenance status is unknown, and documentation is absent, so supply-chain trust is limited and the repository contents and dependencies should be reviewed first.