@invinite-org/invinite-data-cli 0.1.21 → 0.1.22

package/README.md

@@ -77,6 +77,14 @@ Because environment and `.env` values take precedence over stored credentials,
 
 This repo includes plugins for AI coding tools that enable AI-powered financial data retrieval and analysis. Supports **Claude Code**, **OpenCode**, **Codex**, and **Copilot**.
 
+### Choose an integration
+
+- **Standalone skill:** installs the Invinite workflow and CLI reference. It prefers MCP when connected and falls back to the local `invd` CLI.
+- **Standalone MCP connector:** add `https://data.invinite.com/t/<teamId>/mcp` in Claude's connector settings, leave OAuth client ID/secret empty, and complete browser OAuth. This supplies tools but not the packaged research workflows.
+- **Claude plugin:** bundles the skill, remote MCP connector, data agent, and research commands. During setup, enter the team ID shown in the team-pinned MCP URL in Invinite Data API settings; OAuth still uses Dynamic Client Registration and PKCE.
+
+The team ID controls access, usage, and billing for MCP calls. CLI calls use the team selected by `invd login --team <teamId>` and do not inherit the plugin's connector setting.
+
 ### Quick install
 
 ```bash
@@ -123,6 +131,8 @@ npx @invinite-org/invinite-data-cli@latest plugin uninstall --all --global
 claude --plugin-dir /path/to/invinite-data-cli/claude-plugin
 ```
 
+The Claude plugin also includes `compare-companies`, `analyze-filing`, and `ownership-review`. Its `.mcp.json` connects the team-pinned remote server automatically; use `/mcp` to complete OAuth or inspect connection status in Claude Code. In Claude web/Desktop, install the plugin through your organization's plugin marketplace, enter the team ID when prompted, and connect the bundled connector.
+
 ### Usage examples
 
 Use `/financial-research` for multi-step analysis:

package/claude-plugin/.claude-plugin/plugin.json

@@ -1,11 +1,19 @@
 {
-  "name": "invd",
+  "name": "invinite-financial-data",
   "description": "Fetch and analyze financial data using the Invinite Data API — company fundamentals, financial statements, SEC filings, institutional ownership, insider trades, and more.",
-  "version": "0.1.0",
+  "version": "0.3.0",
   "author": {
-    "name": "Outraday"
+    "name": "Invinite"
   },
   "homepage": "https://github.com/outraday-org/invinite-data-cli",
   "repository": "https://github.com/outraday-org/invinite-data-cli",
-  "license": "ISC"
+  "license": "ISC",
+  "userConfig": {
+    "team_id": {
+      "type": "string",
+      "title": "Invinite team ID",
+      "description": "Team billed for Data API usage. Copy it from the team-pinned MCP URL in Invinite Data API settings.",
+      "required": true
+    }
+  }
 }

package/claude-plugin/.mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "invinite-financial-data": {
+      "type": "http",
+      "url": "https://data.invinite.com/t/${user_config.team_id}/mcp"
+    }
+  }
+}

package/claude-plugin/agents/invinite-data.md

@@ -23,7 +23,7 @@ You are a financial data retrieval specialist. Your job is to fetch the requeste
 - Always use `--json` on every data command
 - **Before querying metrics (ratios, CAGR, or growth) or financial statements, first run `invd metadata metrics --json`** to discover the available metric identifiers. The responses from these endpoints use `metric_id` keys — you need the metadata to know what metrics exist and to correctly interpret the results. Run this as a first step alongside or before your main data queries.
 - **Before querying filing sections, first run `invd metadata section-ids --json`** to discover valid section IDs.
-- If a command fails with an authentication error, report it clearly and tell the caller that `INVINITE_DATA_API_KEY` must be set or `invd config set-key` must be run
+- If a command fails with an authentication error, report it clearly and tell the caller to run `invd login`; `INVINITE_DATA_API_KEY` and `invd config set-key` remain manual fallbacks
 - If a company identifier is ambiguous, use `invd company search -q "<name>" --json` first to resolve it
 - For comparing companies, prefer `invd financials snapshot -i AAPL,MSFT,GOOGL -p annual --json` over individual queries
 - When fetching financial statements, default to `annual` period unless the request specifies otherwise

package/claude-plugin/commands/analyze-filing.md

@@ -0,0 +1,15 @@
+---
+description: Analyze a company's SEC filing for material changes, risks, management commentary, and evidence.
+argument-hint: <ticker> [form type or research question]
+---
+
+# Analyze SEC Filing
+
+Analyze the filing requested in `$ARGUMENTS` using Invinite Data.
+
+1. Resolve the company and identify the relevant filing and accession number.
+2. Discover valid filing section IDs before requesting sections.
+3. Retrieve only the sections needed for the question, normally risk factors, MD&A, business, and financial statements.
+4. Separate direct filing evidence from your interpretation.
+5. Report the form type, filing date, accession number, and section for every material finding.
+6. Flag missing sections or unavailable periods instead of inferring their contents.

package/claude-plugin/commands/compare-companies.md

@@ -0,0 +1,15 @@
+---
+description: Compare the financial performance, valuation, growth, and risks of two or more companies.
+argument-hint: <tickers or company names> [focus]
+---
+
+# Compare Companies
+
+Compare the companies in `$ARGUMENTS` using Invinite Data.
+
+1. Resolve ambiguous company names with `company_search` or the equivalent `invd` command.
+2. Fetch available metric definitions before requesting financial metrics.
+3. Fetch company details, the latest annual standardized snapshot, profitability and valuation ratios, and five-year CAGR where available.
+4. Run independent reads in parallel when the active Claude surface supports it.
+5. Present a compact comparison table followed by the most material strengths, weaknesses, and data limitations.
+6. Cite the reporting periods used; do not mix annual and quarterly values without labeling them.

package/claude-plugin/commands/ownership-review.md

@@ -0,0 +1,14 @@
+---
+description: Review institutional ownership, position changes, concentration, and insider trading for a company.
+argument-hint: <ticker> [period or focus]
+---
+
+# Review Ownership
+
+Review ownership activity for `$ARGUMENTS` using Invinite Data.
+
+1. Resolve the company identifier.
+2. Fetch institutional holdings, institutional transactions, and insider trades for the requested period.
+3. Identify the largest holders, notable new or exited positions, and meaningful insider acquisitions or dispositions.
+4. Distinguish position value from share count and filing date from transaction date.
+5. Present concise tables and call out reporting-lag limitations in institutional filings.

package/claude-plugin/skills/invinite-data-cli/SKILL.md

@@ -1,21 +1,51 @@
 ---
-name: invinite-data-cli
-description: Fetch financial data using the Invinite Data API CLI. Use this skill whenever the user wants to look up company information, financial statements, SEC filings, institutional ownership, insider trades, IPO data, market holidays, financial metrics, or any stock/company-related data. Also use when the user mentions tickers, CIKs, balance sheets, income statements, cash flows, 10-K, 10-Q, ratios, CAGR, growth rates, dividends, stock splits, or institutional holdings — even if they don't mention "Invinite" by name.
+name: invinite-financial-data
+description: Fetch financial data through the Invinite Data API MCP connector or invd CLI. Use whenever the user wants company information, financial statements, SEC filings, institutional ownership, insider trades, IPO data, market holidays, financial metrics, or other stock/company data, including requests mentioning tickers, CIKs, balance sheets, income statements, cash flows, 10-K, 10-Q, ratios, CAGR, growth rates, dividends, stock splits, or institutional holdings.
 allowed-tools: Bash(invd *)
 ---
 
-# Invinite Data API CLI
+# Invinite Data API
 
-The `invd` CLI provides access to comprehensive financial data from the Invinite Data API. Always use `--json` when fetching data for analysis — it returns structured JSON you can pipe to `jq` or parse programmatically.
+Use the connected Invinite Data API MCP tools when available. Fall back to the `invd` CLI when MCP is unavailable. Both transports access the same team-billed Data API.
+
+## Transport selection
+
+1. Prefer MCP tools when an Invinite Data connector is available. Call the direct domain tool matching the request; unlike the Web API MCP server, the Data API MCP server does not use meta-tools such as `call_endpoint`.
+2. Use the CLI examples below when MCP is unavailable or when the user explicitly requests CLI usage. Always pass `--json` for data used in analysis.
+3. Do not mix transports merely to repeat a successful request.
+
+### MCP and CLI mapping
+
+| Data need | MCP tool | CLI command family |
+|---|---|---|
+| Search/details/list | `company_search`, `company_details`, `available_companies` | `invd company ...` |
+| Dividends/periods/splits | `company_dividends`, `company_fiscal_periods`, `company_splits` | `invd company ...` |
+| Standardized statements/snapshots | `standardized_financial_statement`, `standardized_financial_snapshot` | `invd financials ...` |
+| As-reported statements/snapshots | `as_reported_financial_statement`, `as_reported_financial_snapshot` | `invd financials ... --as-reported` |
+| Ratios/growth/CAGR | `financial_ratios`, `financial_growth`, `financial_cagr` | `invd metrics ...` |
+| Segment data | `segmented_financials` | `invd segments ...` |
+| SEC filings/search/sections | `sec_filings`, `sec_filings_search`, `sec_filing_sections` | `invd filings ...` |
+| Filing and metric discovery | `sec_available_form_types`, `list_available_section_ids`, `list_available_metrics` | `invd filings form-types`, `invd metadata ...` |
+| Institutional ownership | `holdings_by_company`, `holdings_by_investor`, `institutional_investors`, `institutional_transactions` | `invd ownership ...` |
+| Insider trades/IPOs/holidays | `insider_trades`, `ipos`, `market_holidays` | `invd insider-trades`, `invd ipos`, `invd market ...` |
+
+The discovery rules below apply to both transports: call `list_available_metrics` before ratios, growth, CAGR, or financial-statement analysis, and call `list_available_section_ids` before requesting filing sections.
 
 ## Prerequisites
 
-The CLI must be installed (`npm install -g @invinite-org/invinite-data-cli`) and authenticated. Authentication is resolved in this order:
+### MCP
+
+Connect `https://data.invinite.com/t/<teamId>/mcp` through OAuth. The team in the URL controls data billing. Leave OAuth client ID and secret empty so the client uses Dynamic Client Registration and PKCE.
+
+### CLI
+
+Install the CLI with `npm install -g @invinite-org/invinite-data-cli`, then run `invd login` or `invd login --team <teamId>`. Authentication is resolved in this order:
 1. `INVINITE_DATA_API_KEY` environment variable
-2. OS keychain (via optional `keytar`)
-3. Stored config (set via `invd config set-key`)
+2. `.env` file
+3. OS keychain (via optional `keytar`)
+4. Stored config
 
-If a command fails with an auth error, tell the user to run `invd config set-key` or set `INVINITE_DATA_API_KEY`.
+If an MCP call fails with an auth error, reconnect the connector and complete OAuth. If a CLI call fails with an auth error, run `invd login`; manual `invd config set-key` and `INVINITE_DATA_API_KEY` remain supported fallbacks.
 
 ## Global Options
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@invinite-org/invinite-data-cli",
-  "version": "0.1.21",
+  "version": "0.1.22",
   "type": "module",
   "description": "CLI for the Invinite Data API",
   "publishConfig": {