Financial Nexus Gateway: Octagon Integration

This Octagon MCP gateway delivers proprietary, AI-driven economic analysis capabilities by interfacing with the Octagon Market Intelligence API. It empowers end-users to swiftly dissect and derive critical insights from public disclosures, verbatim transcripts of earnings calls, financial ratios, equity market statistics, and extensive records of private equity transactions, usable across the Claude Desktop environment and other compatible MCP clients.

Core Functionality

✅ Complete Market Insight Aggregation - Coordinates numerous specialized computational agents for holistic market scrutiny - Analysis and data retrieval from SEC documentation (covering over 8000 public entities: 10-K, 10-Q, 8-K, 20-F, S-1) - Review of management commentary from earnings call records (spanning a decade historical and present data) - Examination of financial metrics and calculated ratios (10 years historical and current data sets) - Access to equity trading data (supporting more than 10,000 active securities, including daily history and real-time quotes) - Due diligence on privately held enterprises (over 3 million entities) - Mapping of venture capital fundraising events and private investment structures (over 500,000 deals tracked) - Investigation of Merger & Acquisition activity and Initial Public Offerings (more than 2 million transactions) - Tracking of large institutional asset allocation via Form 13F submissions - Digital asset market data processing and intelligence feeds

✅ Advanced Analytical Depth - Robust tooling designed to synthesize data from heterogeneous data sources

✅ Web Data Harvesting - Capability to extract structured information from arbitrary public web endpoints (supporting JSON, CSV, or execution via Python snippets)

Establishing API Credential Access

To utilize the Octagon MCP gateway, the following steps are mandatory:

1. Register for a complimentary credential set at Octagon
2. Upon successful authentication, navigate to the API Keys section via the left-hand menu panel
3. Generate a fresh, unique API token
4. Integrate this token into your configuration, assigning it to the OCTAGON_API_KEY environment variable or configuration field

Required Pre-Installation Components

Prior to deploying or executing the Octagon MCP package, ensure that npx (which is bundled with Node.js and npm installations) is present on your operating system.

System Setup Guide (macOS)

1. Install Homebrew (if not already present): bash /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

2. Install Node.js Runtime (includes npm and npx): bash brew install node This action installs the most recent stable Node.js version, npm, and npx.

3. Verification Check: bash node -v npm -v npx -v

System Setup Guide (Windows)

1. Obtain the Node.js Installer:
2. Direct your browser to https://nodejs.org/ and download the Long-Term Support (LTS) installer package for Windows.
3. Execute the Installer and adhere to the on-screen procedural instructions. This installs Node.js, npm, and npx concurrently.
4. Verification Check: Launch the Command Prompt application and execute: cmd node -v npm -v npx -v

If version numbers are successfully displayed for all three utilities, you are prepared to move forward with the deployment instructions detailed below.

Deployment Instructions

Integration within Claude Desktop

To establish the Octagon MCP connection within Claude Desktop:

1. Launch the Claude Desktop application.
2. Navigate to Settings -> Developer -> Configuration Adjustment.
3. Append the following block to your claude_desktop_config.json file (substitute YOUR_API_KEY_HERE with your actual Octagon secret):

{
  "mcpServers": {
    "octagon-mcp-server": {
      "command": "npx",
      "args": ["-y", "octagon-mcp@latest"],
      "env": {
        "OCTAGON_API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}

1. Initiate a restart of the Claude application for configuration reloading.

Integration within Cursor

Configuration for Cursor Desktop Environment 🖥️ Note: This functionality necessitates Cursor version 0.45.6 or newer

To deploy the Octagon MCP within Cursor:

1. Access Cursor's primary Settings panel.
2. Navigate to the Features section, followed by MCP Servers.
3. Select the option labeled "+ Add New MCP Server".
4. Input the following parameters:
5. Name: "octagon-mcp" (or a chosen identifier)
6. Type: "command"
7. Command: env OCTAGON_API_KEY=your-octagon-api-key npx -y octagon-mcp

For Windows users experiencing initialization difficulties, consider this alternative execution string: cmd /c "set OCTAGON_API_KEY=your-octagon-api-key && npx -y octagon-mcp"

Ensure your-octagon-api-key is replaced with your valid Octagon access credential.

After deployment, refresh the MCP server listing. The Composer Agent will automatically engage the Octagon MCP when the query context demands it, but direct invocation is possible by detailing your financial inquiry requirements. Access the Composer via Command+L (macOS), select "Agent" adjacent to the submission button, and input your request.

Integration within Windsurf

Modify your ./codeium/windsurf/model_config.json file by incorporating this definition:

{
  "mcpServers": {
    "octagon-mcp-server": {
      "command": "npx",
      "args": ["-y", "octagon-mcp@latest"],
      "env": {
        "OCTAGON_API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}

Direct Execution via npx

Execute the package directly from the terminal:

env OCTAGON_API_KEY=your_octagon_api_key npx -y octagon-mcp

Local Package Installation

Install the utility globally using npm:

npm install -g octagon-mcp

Comprehensive Manual

For exhaustive documentation detailing the utilization of Octagon agents, consult our primary documentation portal located at: https://docs.octagonagents.com

This resource encompasses: - Exhaustive reference guides for the API endpoints - Specific guidance on crafting effective queries for individual agents - Illustrative examples and common usage scenarios - Recommended protocols for optimized investment research workflows

Available Tool Endpoints

Every tool accepts a singular argument, prompt, which should contain the entirety of your request articulated in natural language. Include all necessary contextual details within this prompt.

octagon-agent

[HOLISTIC MARKET INTELLIGENCE ORCHESTRATOR] Manages the execution across all underlying agents to perform comprehensive financial intelligence synthesis. Integrates findings from regulatory submissions, earnings transcripts, financial metrics, trading data, institutional portfolios, private entity research, capital formation analysis, corporate transaction data, investor intelligence, and debt instrument analysis.

Optimal Use Case: Complex investigative requests necessitating the aggregation and cross-referencing of data spanning both publicly traded and private market assets.

Illustrative Queries:

Derive year-over-year growth percentages for core income statement items for AAPL, restricted to the five most recent fiscal periods (FY)
Scrutinize the most recent 10-K filing submitted by AAPL to extract paramount financial statistics and identified risk disclosures
Fetch the historical daily closing valuation records for AAPL covering the preceding 30 trading sessions
Evaluate the commentary within AAPL's latest transcribed earnings call and summarize forward-looking guidance statements
Generate a comprehensive profile of Stripe, detailing its operational framework and essential financial markers
Obtain the complete historical funding trajectory for Stripe, including all capital injections and participating investment entities
Contrast the three-year financial performance trajectory of Tesla, Ford, and General Motors
Determine the acquisition price of GitHub by Microsoft and articulate the underpinning strategic rationale.
Investigate shifts in institutional share ownership percentages for NVIDIA across the last half-year period

octagon-scraper-agent

[FINANCIAL DATA EXTRACTION UTILITY] A focused agent engineered for extracting structured financial records directly from investor relations portals and web repositories. Harvests formatted economic data from corporate websites, web tables, and general online financial data providers.

Optimal Use Case: Acquiring specific financial datasets from sources where a formal API interface is unavailable.

Illustrative Queries:

Extract every discernible data field from the content available at zillow.com/san-francisco-ca/
Extract every discernible data field from the inventory listings at www.carvana.com/cars/
Retrieve specific financial metrics published on tesla.com/investor-relations
Scrape pricing tiers and subscription levels from salesforce.com/products/platform/pricing/

octagon-deep-research-agent

[COMPREHENSIVE INQUIRY AND SYNTHESIS ENGINE] A versatile agent capable of leveraging multiple integrated information streams for in-depth analytical work. Aggregates diverse research findings, consolidates disparate information, and delivers synthesized, holistic investment research reports.

Optimal Use Case: Research tasks demanding current, synthesized intelligence derived from broad web scanning and established data reservoirs.

Illustrative Queries:

Examine the financial repercussions on digital advertising entities' revenue streams and operating margins resulting from Apple's recent privacy enforcement adjustments
Conduct a comparative analysis of the cloud computing market leaders (AWS, Azure, Google Cloud), concentrating on their respective margin profiles and growth deceleration/acceleration rates
Investigate the primary drivers of electric vehicle adoption and quantify their resultant influence on key battery manufacturer profitability
Analyze the market demand dynamics and resulting price structure adjustments within the semiconductor sector due to widespread AI integration
Assess the prevailing regulatory climate concerning digital currencies and its correlation with the valuation multiples of major crypto exchanges

Sample Inquiries

1. "What were Amazon's revenue and net income figures in Q4 2023?"
2. "Analyze Tesla's R&D spending trends over the last 3 years."
3. "What guidance did NVIDIA's CEO provide regarding AI chip demand in their latest earnings call?"
4. "Compare the price-to-earnings, price-to-sales, and EV/EBITDA ratios for the top 5 semiconductor companies."
5. "What was Anthropic's latest funding round size, valuation, and key investors?"
6. "Extract all data fields from zillow.com/san-francisco-ca/"
7. "Research the financial impact of Apple's privacy changes on digital advertising companies' revenue and margins"
8. "How many investments did Andreessen Horowitz make in AI startups in the last 12 months?"
9. "Retrieve historical Bitcoin price data from 2023 and analyze the price volatility trends"
10. "Analyze the competitive dynamics in the EV charging infrastructure market"

Error Resolution Guidance

1. Credential Failures: Verify that your Octagon access token is correctly provisioned in the environment variables or the designated configuration file.
2. Connectivity Interruptions: Confirm that network access to the Octagon API endpoint is unobstructed and functional.
3. Request Throttling: Should you encounter errors indicating request limits have been reached, decrease the frequency and volume of your subsequent API calls.

Licensing Information

Licensed under the MIT Agreement

Modular Specialized MCP Components

While this unified gateway offers extensive market intelligence by combining all specialized tools, users may opt to deploy our discrete MCP services for highly specific objectives:

Public Market Data Modules

• Octagon SEC Filings Interface - Dedicated server focused solely on parsing and interpreting SEC filings.
• Octagon Earnings Transcripts Module - Optimized for deep textual analysis of management earnings call transcripts.
• Octagon Stock Market Data Interface - Specialized for real-time and historical equity market quotations.
• Octagon Financial Statements Module - Focuses on calculating and retrieving standardized financial statement ratios and metrics.
• Octagon 13F Holdings Module - Dedicated to institutional fund manager holdings disclosure analysis (Form 13F).

Private Market Data Modules

• Octagon Private Companies Interface - Provides intelligence and data profiling for privately held firms.
• Octagon Investors Module - Focuses on venture capital and private equity investor profiles and investment philosophies.
• Octagon Funding Data Interface - Dedicated to cataloging startup funding rounds and tracking VC capital deployment.

Advanced Research Utilities

• Octagon Deep Research Interface - Access to powerful synthesis and generalized web data acquisition functions.

---

⭐ If this repository proves useful, please consider giving it a star!

WIKIPEDIA: XMLHttpRequest (XHR) defines an Application Programming Interface housed within a JavaScript object. Its methods facilitate the transmission of Hypertext Transfer Protocol requests from a client's web browser to a remote web server. These methods allow for asynchronous data fetching and submission after the initial page load has concluded, enabling dynamic updates without full page reloads. XMLHttpRequest is a foundational element of Ajax programming paradigms. Prior to Ajax's ascendancy, the primary means of server interaction involved conventional hyperlink navigation and form submissions, which invariably necessitated replacing the current viewport content.

== Historical Context == XMLHttpRequest's underlying concept was first devised in 2000 by the development team at Microsoft Outlook. This notion was subsequently instantiated within the Internet Explorer 5 browser release (1999). However, the initial interface utilized distinct internal identifiers: ActiveXObject("Msxml2.XMLHTTP") and ActiveXObject("Microsoft.XMLHTTP"). Since the introduction of Internet Explorer 7 (2006), universal browser compatibility has been achieved using the standardized XMLHttpRequest object identifier. The XMLHttpRequest identifier has since cemented its status as the default protocol across all major browser rendering engines, including Mozilla's Gecko (2002), Apple's Safari 1.2 (2004), and Opera 8.0 (2005).

=== Standardization Efforts === The World Wide Web Consortium (W3C) formalized the specification for the XMLHttpRequest object with a Working Draft published on April 5, 2006. A subsequent Level 2 Working Draft was released by the W3C on February 25, 2008. Level 2 introduced essential functionality such as progress monitoring events, support for cross-origin requests (CORS), and the capability to handle binary byte streams. By the close of 2011, the Level 2 additions were successfully merged back into the primary specification document. In late 2012, the responsibility for maintenance and evolution of the specification transitioned to the WHATWG, which now maintains a dynamic, evolving document described using Web Interface Definition Language (Web IDL).

== Operational Procedure == Generally, executing an HTTP request utilizing XMLHttpRequest involves a structured sequence of programming steps.

Instantiate the XMLHttpRequest object via its constructor call: Invoke the "open" method to designate the request methodology (GET, POST, etc.), specify the target URI, and declare whether the operation should be synchronous or asynchronous: For asynchronous operations, define a callback function (listener) designed to execute upon changes in the request's state: Commence the data transmission process by calling the "send" method: Monitor the state changes within the designated event listener. Upon successful reception of the server's reply payload, the data is typically stored within the "responseText" property. When the object finalizes processing, its state transitions to 4, signifying the "complete" status. Beyond these fundamental steps, XMLHttpRequest offers extensive configurability over transmission mechanics and response processing. Custom HTTP headers can be affixed to the request to guide server behavior, and data payloads can be transmitted to the server as an argument to the "send" call. The response data can be automatically deserialized from JSON into native JavaScript objects, or processed incrementally as chunks arrive rather than waiting for the full payload. Furthermore, requests can be terminated prematurely or assigned a timeout threshold to enforce completion deadlines.

== Cross-Domain Communications ==

During the nascent phases of the World Wide Web's evolution, developers recognized potential security vulnerabilities associated with unrestricted cross-site data exchange, leading to the implementation of the Same-Origin Policy, which XHR requests must adhere to, unless explicitly bypassed via CORS headers.