io.github.chrischall/setlist-mcp

The materials show it requires SETLIST_API_KEY and SETLIST_SESSION_COOKIE; both an API key and a session cookie are sensitive credentials and could allow third-party use of the related service if exposed. SETLIST_ACCEPT_LANGUAGE appears to be a configuration value rather than a sensitive secret.

No explicit remote host is listed by the system, but the stated function is to retrieve setlist.fm concert data, which normally implies outbound requests to related services and transmission of query content. The materials do not show evidence of sending data to unrelated or unknown endpoints, so this looks like standard network behavior that warrants caution.

The system explicitly marks it as executes-code, meaning it runs code/processes locally as an MCP tool. This is an inherent capability of such tools; the available materials do not indicate requests for additional high-risk system privileges or actions unrelated to its stated purpose.

The provided materials do not specify which local files or other resources it reads or writes, though it will at least handle credentials stored in environment variables. Because the README and permission details are absent, the local data-access boundary cannot be fully confirmed, but there is no clear sign of overbroad access in the materials.

The source is the official registry and there is a public source repository with updates within the last year, providing reasonable auditability and signs of maintenance. Low community stars and an undeclared license add some uncertainty, but not enough to constitute a high-risk supply-chain red flag.