LLM Pulse

The materials explicitly state that no keys or environment variables are required. No API key, OAuth token, or other sensitive credential is requested, so credential leakage and abuse risk appears relatively low.

The tool declares network access to the remote endpoint api.llmpulse.ai. Its described functions around brand mentions, citations, sentiment, and reporting typically imply that related queries or analysis data may be sent to that service. This egress is consistent with the stated purpose, but it is still external data transfer and should be reviewed.

System checks indicate that the tool executes code or launches local processes, which is a standard MCP capability. The provided materials do not show requests for clearly excessive privileges or dangerous system control unrelated to its purpose, so this merits normal caution rather than a higher rating.

The provided materials do not specify which local files, directories, or other resources it can read or write. Without README details, it is not possible to confirm that access is limited to the minimum necessary data. There is no explicit evidence of overbroad access, but the data-access boundary is not very transparent, so least-privilege use is advisable.

Positive factors include being listed in an official registry, having an auditable open-source repository, and showing updates within the last year. Points to watch are the missing README, undeclared license, and low community adoption (0 stars), so overall supply-chain risk is not high but transparency and maturity are only moderate.