English Français العربية

Vi Assistant by Vultax

Official registry Search and web

Vi market evidence, hypothetical price scenarios and published Vultax research.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http vi-assistant-by-vultax 'https://vultax.com/vi-mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "vi-assistant-by-vultax": {
            "type": "http",
            "url": "https://vultax.com/vi-mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Vi Assistant by Vultax
  2. Install in your assistant
  3. Try these workflows
  4. Run or reuse the tools
  5. Data handling

Vi Assistant by Vultax

Bring a Polymarket link to your assistant. Inspect the exact market and its resolution rules, calculate explicit price scenarios, and support your analysis with published Vultax research.

Try the public demo · Download v1.1.0 · MCP Registry

MCP endpoint: https://vultax.com/vi-mcp · Streamable HTTP · No API key

ToolWhat it does
inspect_prediction_marketResolves an exact Polymarket event/market, returns rules, outcome prices, spread, reported volume/liquidity, source times and a bounded trade sample. Asks for selection when an event has several markets.
calculate_probability_scenarioComputes hypothetical profit/loss and break-even for explicit contract quantity, entry/scenario prices and dollar costs.
search_researchFinds published studies with stable article IDs and citation URLs.
get_research_articleReads a complete published article and its sources.
get_research_datasetRetrieves published tables, units, observation context and CSV/JSON downloads.

Snapshots may be delayed. Provider metadata updates are not quote timestamps. Scenarios are arithmetic, with no forecast, backtest, market depth, slippage or execution. Published studies are historical. The public extension cannot access private accounts or create trades, alerts, bots or paper positions. It is a public Vi companion; the full authenticated Vi app has a separate access boundary.

Install in your assistant

Codex

Install this repository as a Codex plugin through a configured marketplace, or connect directly:

codex mcp add vultax-research --url https://vultax.com/vi-mcp

Start a new task after installing. The native package includes .codex-plugin/plugin.json and two skills. Keep the existing vultax-research identifier when upgrading.

ChatGPT and Claude connectors

Where your account supports custom MCP connectors, add Vi Assistant by Vultax with URL https://vultax.com/vi-mcp and no authentication. Custom connection availability depends on the client/account. A downloadable package or registry entry does not imply approval in a curated directory. See publication status.

Claude Code marketplace
/plugin marketplace add Vultax/vultax-research-plugin
/plugin install vultax-research@vultax

Or use a direct MCP connection:

claude mcp add --transport http vultax-research https://vultax.com/vi-mcp

Use either the plugin or direct connection to avoid duplicate tools. This repository contains the native plugin and its self-hosted marketplace, not an Anthropic-endorsed listing. Official marketplace instructions.

Claude Desktop bundle

Download vultax-vi-1.1.0.mcpb from the release and open it in a compatible desktop client. The bundle includes the Node server and production dependencies; Node 20+ or the client's compatible bundled runtime is required. The local transport uses stdio and opens no listening port. Research queries go to Vultax; market lookups go to Polymarket. MCP bundle specification.

Gemini CLI extension
gemini extensions install https://github.com/Vultax/vultax-research-plugin --ref=v1.1.0

The root gemini-extension.json connects the same tools and includes GEMINI.md guidance. Gallery discovery requires the gemini-cli-extension topic and Google's crawler validation. Official release instructions.

Cursor, VS Code, Windsurf and OpenCode

Merge the matching entry into the client's configuration, preserving existing servers:

ClientConfiguration
Cursorconnections/cursor.mcp.json → .cursor/mcp.json
VS Code / GitHub Copilotconnections/vscode.mcp.json → .vscode/mcp.json, or MCP: Add Server → HTTP
Windsurf / Devin Desktopconnections/windsurf.mcp.json → ~/.codeium/windsurf/mcp_config.json
OpenCodeconnections/opencode.json → opencode.json

These are MCP connections, not VS Code Marketplace extensions. Configuration references: Windsurf/Devin, OpenCode.

n8n and public feeds

Import the n8n workflow to retrieve Vultax's public Atom feed on manual request. It sends no messages and needs no credentials. Research access also provides Markdown and downloadable datasets.

Try these workflows

  • “Inspect this Polymarket link. Show its rules, available evidence, source times and the matching Vultax workspace.”
  • “For 100 contracts bought at 0.50, calculate exits at 0.40 and 0.60 with $1 entry and $1 exit costs.”
  • “Find research on copying Polymarket traders. Explain the measured costs and study limitations.”

The scenario example gives −$12 and +$8, with a break-even price of 0.52. It is an illustration using explicit assumptions.

Run or reuse the tools

npm ci --ignore-scripts
npm test
npm start
# Another terminal:
npm run test:vi

The demo starts at http://127.0.0.1:3147. Set VI_TEST_URL to test the public endpoint. For a generic stdio client use node /absolute/path/to/src/stdio.mjs after installing dependencies. npm run test:live verifies the original research-only service.

The reusable functions are marketBrief and probabilityScenario. They return structured evidence/calculations without a model call. See Vi integration notes for reuse inside the authenticated app.

Data handling

The hosted service receives only submitted tool arguments. Market identifiers are sent to Polymarket's public Gamma/Data APIs. Research queries and article IDs are sent to Vultax's public research MCP. Scenario arithmetic needs no external data provider. Do not include account links, credentials, private portfolios or unrelated conversation text. Fixed public-provider URLs, bounded response sizes, request timeouts, validation and request limits constrain the adapter.

Vultax infrastructure may keep ordinary HTTP/security logs. The adapter adds no user accounts, database, query analytics or payment requirements. Workspace links use fixed utm_source=vi_assistant attribution, with no private questions in the URL. Operated by OmniOS OÜ: about/support, privacy, terms.

The MIT license covers this original integration code and documentation. It does not grant rights to Vultax branding, published research or third-party market data.

Frequently asked questions

What is Vi Assistant by Vultax?

Vi market evidence, hypothetical price scenarios and published Vultax research.

How do I install Vi Assistant by Vultax?

It runs as a remote server. In Claude Code: claude mcp add --transport http vi-assistant-by-vultax 'https://vultax.com/vi-mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Vi Assistant by Vultax need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Vi Assistant by Vultax open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains Vi Assistant by Vultax?

It is published by Vultax. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.