getoutpost

This MCP server provides Claude with access to GetOutpost's real-time Indian options market data and volatility analytics. It exposes tools to retrieve implied volatility (IV), realized volatility (RV) using multiple methods (close-to-close, Parkinson, Garman-Klass, Rogers-Satchell, Yang-Zhang), compute the volatility risk premium (VRP), and analyze volatility skew across strike prices. In addition, it includes discovery/filtering tools to find symbols based on IV/RV/VRP metrics and an opportunity scanner suite to identify potential trading opportunities such as short-vol, tail-risk hedges, and directional trades. To use it, install the MCP server globally, configure your credentials file path, and run the MCP server through your MCP framework. Once running, you can call tools like get_iv, get_vol, get_vrp, get_skew, filter_quick_rules_iv_percentile, filter_quick_rules_rv_percentile, and the scan_* tools to build data-driven prompts for Claude.

Typical workflows include: querying IV or RV for specific symbols to gauge market expectations and historical volatility, comparing IV/RV across symbols to identify relative cheapness or richness, and scanning for short volatility or hedging opportunities. You can also leverage prompts that combine several tools to generate comprehensive analyses, such as “find symbols with top short vol opportunities in NIFTY+30DTE” or “show skew patterns across strikes for a given symbol.”

Prerequisites:

• Node.js v24.x or newer installed on your system
• npm available in PATH
• Access to a valid GetOutpost credentials file

Installation steps:

1. Install the MCP server package globally via npm:

npm install -g getoutpost-mcp-server

2. Prepare your credentials file. Create a JSON file at the path you will reference (e.g., ~/.getoutpost_credentials.json) with your tokens, e.g.:

{
  "ACCESS_TOKEN": "your_access_token_here",
  "REFRESH_TOKEN": "your_refresh_token_here",
  "EMAIL": "your_email@example.com"
}

3. Configure your MCP to run the GetOutpost MCP server. Create a configuration snippet like:

{
  "mcpServers": {
    "getoutpost": {
      "command": "getoutpost-mcp-stdio",
      "env": {
        "CREDENTIALS_FILE_PATH": "/absolute/path/to/.getoutpost_credentials.json"
      }
    }
  }
}

4. Start the MCP-enabled runtime or your MCP bridge that loads this configuration. The exact command depends on your environment (e.g., starting the MCP host that loads the JSON above).

If you prefer not to edit configuration directly, simply ensure the environment variable CREDENTIALS_FILE_PATH points to your credentials file and your runtime can invoke getoutpost-mcp-stdio as shown.

Notes and tips:

• The server uses a credentials file that is automatically refreshed; ensure the path is writable by the process running the MCP server.
• The package name implies the MCP server uses stdio-based communication (stdio) for tool invocation. Ensure your MCP host supports stdio adapters.
• The environment variable CREDENTIALS_FILE_PATH should be an absolute path to your credentials file.
• If you encounter token refresh issues, verify that the credentials file contains ACCESS_TOKEN, REFRESH_TOKEN, and EMAIL as shown in the example.
• When upgrading, the npm package name or command might change; consult the repository's release notes for breaking changes.
• This server targets Indian markets (NSE, BSE); data availability may depend on GetOutpost subscription level and API access.}