Semantic Scholar MCP Server

It requires a SEMANTIC_SCHOLAR_API_KEY, which is a sensitive credential for accessing a third-party scholarly API. The materials do not indicate requests for excessive secrets, but the key should be protected from leakage via logs, config files, or sessions.

Its functionality inherently depends on contacting the Semantic Scholar API, so user queries are expected to be sent to an external service relevant to its stated purpose. The materials do not list a specific host, which limits transparency, but there is no evidence of exfiltration to unrelated or unknown endpoints.

As an MCP server, it needs to start and run a local service process, which is standard for this tool category. The available materials do not show requests for elevated privileges, unrelated system command execution, or suspicious persistence behavior.

Based on the description, it primarily handles paper, author, citation, and recommendation queries, so its expected data scope appears limited to user input and API responses. The materials do not indicate broad local file read/write access or obvious over-privilege, but the missing README leaves important details unspecified.

It is listed in an official registry and has an open-source repository with updates in the past year, which are positive signals that reduce risk. However, the repository has very low community adoption, no declared license, and no README, so auditability and community validation are only moderate; reviewing the source and dependency list first is still recommended.