pump.fun Solana Data

It requires PUMPFUN_MCP_URL. This appears more like a remote service URL than a typical API secret, but if it embeds auth parameters or points to a private endpoint, leakage could expose backend access; the materials do not define its format, sensitivity, or least-privilege expectations.

Network egress is expected because the tool depends on PUMPFUN_MCP_URL to reach a remote service; the provided host field is empty and the materials do not disclose actual domains or data destinations. Based on the stated functionality, query content and related inputs will likely be sent to whatever service that URL points to, with limited endpoint transparency but no explicit evidence of unrelated exfiltration.

The system flags code execution, indicating that an MCP service or related process runs locally. This is a normal MCP capability; the current materials do not show any need for shell privilege escalation, driver installation, process injection, or other system permissions clearly disproportionate to read-only data queries.

The description only claims read-only capabilities for token discovery, on-chain analysis, SNS, and 3D snapshots, with no mention of on-chain writes, local file modification, or broad access to user data. The materials also do not request extra data permissions such as filesystem, camera, or clipboard access, so no overbroad data access is evident from the available facts.

It is listed in an official registry, has a public source repository, and was updated within the last year, all of which reduce risk. On the other hand, the README is absent, the license is unspecified, and community adoption is only 0 stars, so audit context and maturity signals are limited; this supports caution rather than a high-risk supply-chain rating.