Massive Financial Connector

Full Massive (Polygon) market-data connector with secure local key handling. Starts the official MCP server and supports endpoint discovery, endpoint docs, g...

This skill appears to implement a legitimate Massive/Polygon connector, but there are three red flags you should address before installing or running it: (1) The registry metadata does not list MASSIVE_API_KEY or required binaries (curl, python3, uvx) — verify and supply only the minimal credentials needed. (2) start-mcp-server.sh calls a local uvx binary with a git+ URL which will fetch and execute code from GitHub at runtime — inspect what uvx does and manually review the GitHub repo (massive-com/[email protected]) before allowing it to run. (3) The scripts source your ~/.zshrc which can execute arbitrary shell code and expose other env variables; consider removing that line or running the scripts in a controlled environment. Recommended steps: run the scripts manually in an isolated VM/container, confirm the uvx binary's origin and behavior (or install a vetted alternative), verify the remote repo contents, and ensure your MASSIVE_API_KEY is stored and used securely (not committed or uploaded). If you cannot audit uvx and the GitHub repo, do not run the start script with network access.

Type: OpenClaw Skill Name: massive-financial-connector Version: 1.1.1 The skill bundle exhibits high-risk behaviors including sourcing the user's '~/.zshrc' file in all shell scripts (e.g., 'get-agg-day.sh', 'start-mcp-server.sh'), which executes arbitrary code from the user's shell configuration and exposes the full environment. It also transmits the 'MASSIVE_API_KEY' as a plaintext URL query parameter to 'api.massive.com', a practice that leaks credentials in logs. Additionally, 'start-mcp-server.sh' uses 'uvx' to fetch and execute code directly from a remote GitHub repository ('github.com/massive-com/mcp_massive'), introducing a significant supply chain risk without sufficient pinning or verification.