io.github.cyanheads/gutenberg-mcp-server

The materials only show MCP_LOG_LEVEL, which is typically a logging-level setting rather than a sensitive credential; there is no indication of an API key, OAuth token, or account secret, so credential abuse risk appears low.

The tool is declared to connect to gutenberg.caseyjhand.com, which is broadly consistent with its Gutenberg ebook retrieval purpose. User queries or request content may be sent to that remote endpoint, but the materials do not show exfiltration to unrelated or unknown third parties.

The system checks indicate it executes code / runs as a local MCP service, which is a standard capability for this type of tool. The provided materials do not show requests for unusual system privileges, persistence mechanisms, or dangerous execution behavior unrelated to its stated function.

From the available description, it appears to handle retrieved ebook text and user requests; with no README, it is not possible to fully determine whether it reads/writes local files, caches data, or accesses additional resources. There is no clear evidence of overbroad access, but transparency is limited.

Positive factors include an official registry listing, an open-source repository, and updates within the past year, which improve auditability. Points to watch are the missing README, undeclared license, and very low star count, which weaken evidence of broad adoption and documentation maturity.