massive-financial-connector_skill

This skill retrieves real-time and historical market data from Massive/Polygon, starting MCP server, and provides endpoint discovery, docs, and SQL-style
  • Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill massive-financial-connector

  • _meta.json310 B
  • SKILL.md2.0 KB

Overview

This skill is a full market-data connector for Massive (Polygon) that provides secure local API key handling and a complete MCP server interface. It enables endpoint discovery, documentation lookup, generic API calls, SQL-style querying, post-processing functions, and quick scripts for common quote checks. Use it to retrieve real-time and historical data for stocks, options, forex, crypto, and indices sourced from Massive.

How this skill works

The skill expects a local MASSIVE_API_KEY and never prints or commits that key. In full-capability mode it starts the official MCP server, exposing tools for searching endpoints, fetching endpoint docs, making generic API calls, and running SQL-style queries against stored market data. It also includes lightweight scripts for retrieving last trades, previous closes, and daily OHLCV aggregates.

When to use it

  • When you need authenticated, low-latency access to Massive/Polygon market data.
  • When you want endpoint discovery and human-readable endpoint documentation before calling APIs.
  • When you want to store and query market data with SQL-style queries and post-process results.
  • When you need quick checks like last trade, previous close, or a daily aggregate from scripts.
  • When you require a secure local workflow that avoids exposing API keys to remote services.

Best practices

  • Set MASSIVE_API_KEY in your local environment and never echo or commit it anywhere.
  • Start the MCP server for full functionality: it provides endpoint discovery, docs, and query tools.
  • Return a concise numeric result first, then include timestamp and exchange metadata in responses.
  • If auth fails with 'Unknown API Key', verify the local shell environment and key status in the Massive dashboard.
  • If Massive is unavailable, explicitly handle failure and offer a fallback data source before proceeding.

Example use cases

  • Start the MCP server to explore available Massive endpoints and pull intraday quotes for a trading dashboard.
  • Run scripts/get-last-trade.sh AAPL to retrieve the latest trade price plus timestamp and exchange.
  • Use query_data to store daily bars and run SQL-style queries for backtesting or analytics.
  • Fetch previous close and percent change for earnings reports or portfolio rebalancing checks.
  • Retrieve historical OHLCV with scripts/get-agg-day.sh <SYMBOL> <YYYY-MM-DD> for research or reporting.

FAQ

Set MASSIVE_API_KEY in your local environment; the skill accepts quoted or unquoted values.

How do I get full functionality?

Start the official MCP server using scripts/start-mcp-server.sh to enable endpoint search, docs, API calls, and query tools.

What happens if Massive is down?

The skill should explicitly report the failure and ask whether to use a predefined fallback data source.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational