io.github.cyanheads/openlibrary-mcp-server

The materials only show MCP_LOG_LEVEL, which is a logging configuration rather than a sensitive secret. No API key, OAuth token, or other high-sensitivity credential is indicated, so credential exposure risk appears low.

The tool is declared to connect to the remote endpoint openlibrary.caseyjhand.com to perform book/author search and cover resolution. This means user queries may be sent to that endpoint. This is normal outbound behavior, and the provided materials do not show unrelated third-party endpoints or other clear exfiltration red flags.

The system checks indicate it executes code/processes locally as an MCP tool, which is standard behavior for this class of tool. The provided materials do not indicate any extra system-level privileges, shell-injection behavior, or execution scope unrelated to its stated function.

The description is limited to searching books, authors, editions, and subjects, and does not state any need to read/write local files, access databases, the clipboard, or other sensitive resources. Based on the current materials, no excessive data-access request is evident.

It comes from the official registry, has an auditable open-source repository, and was updated within the last year; these materially reduce supply-chain risk. The 0-star community signal and unspecified license add some adoption and compliance uncertainty, but they do not by themselves constitute a high-risk red flag.