Vi Assistant by Vultax
io.github.ChristopherZYXPublished by GitHub account ChristopherZYXv1.1.0Updated Oct 1, 2026
Vi market evidence, hypothetical price scenarios and published Vultax research.
Overview
Vi Assistant by Vultax lets an assistant inspect Polymarket prediction markets, run hypothetical price scenarios, and read published Vultax research.
- What you can do
- Inspect a Polymarket event or market: resolution rules, outcome prices, spread, volume, liquidity, source times and a bounded trade sample, with selection prompts when an event has several markets. Calculate hypothetical profit/loss and break-even from explicit contract quantity, entry and scenario prices, and dollar costs. Search published Vultax studies and read full articles with their sources. Retrieve published research datasets with tables, units, observation context and CSV/JSON downloads.
- When to use it
- Useful when you want to check a Polymarket link's exact rules and pricing evidence, test explicit what-if price scenarios arithmetically, or ground an analysis in published Vultax research. It is a public companion, not a trading or account tool.
- Requirements
- Remote Streamable HTTP endpoint at vultax.com with no API key or authentication. The optional desktop bundle needs Node 20+ or a compatible bundled runtime and uses stdio. Network access to Polymarket's public APIs and Vultax's research service is required for lookups.
Installation
In SourceWeft
- Open Vi Assistant by Vultax in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.ChristopherZYX%2Fvultax-research/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"vi-assistant-by-vultax": {
"type": "http",
"url": "https://vultax.com/vi-mcp"
}
}
}README
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
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:
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
Or use a direct MCP connection:
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
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:
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
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.
Source: README.md at commit 62bc35c
Tools
0Version history
1- v1.1.0LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.