douban-mcp

The materials explicitly state that no keys or environment variables are required. Although the description mentions authenticated write actions, no setup or configuration requiring user credentials is shown, so no direct credential exposure or abuse path is evident from the current materials.

Its functionality involves accessing Douban movie/book data, so outbound network requests are likely inherent to its purpose. However, the materials do not disclose specific remote endpoints, and the system metadata also lists none. The current information is insufficient to verify which hosts receive data, so actual runtime network access should be monitored.

The system marks it as executes-code, meaning it runs code/processes locally as an MCP tool. This is a normal capability for this class of tool; the materials do not show requests for unusual system privileges or clearly unrelated dangerous operations, so this is caution rather than high risk.

The description shows it can read Douban content data and perform write actions such as marking movies/books when authenticated. However, no README or permission boundaries are provided, so it is unclear whether it accesses local files, browser state, or other additional data sources. The data access scope is under-disclosed and should be treated with least privilege.

Positive factors include being open-source, MIT-licensed, and having an auditable source repository, which materially lowers risk. Caution remains because it comes from a third-party registry, has 0 stars, and an unknown maintenance status, indicating weaker trust and maintenance signals; reviewing the source and dependencies first is advisable.