Practical overview
When it fits
Use the web scanner or Bundle Index for direct token and launch-pattern research; choose the local browser companion when you want to inspect posts as you browse, or the Telegram bot for chat-based scanning.
Who it is for
- Researchers examining Solana memecoin contracts and launch activity.
- Users who want to trace shared funding, launch-block purchases or wallet connections.
- People who want research surfaced through a browser companion or Telegram bot.
Documented uses
- Review a contract's authorities, holders, developer share, prior launches and liquidity or curve progress.
- Investigate launch-block purchases and connections among holders through transaction trails.
- Monitor new pump.fun launches through the live Bundle Index or use the Telegram bot for scans and X-rays.
- Set up a local browser companion to turn visible feed posts into research questions.
Requirements & limits
The website README describes its listed tools as free and says they require no wallet connection. The local browser companion requires Python 3.11+ and Chrome or Chromium; its backend supports macOS, Linux or Windows through WSL2. Node 22+ is needed only for the full test suite and optional Solana module. Grok reviews are optional and require a locally configured API key.
- The scanner's score is accompanied by reasons, and unreadable information is marked unknown rather than safe.
- Web X-ray exposes transaction links for wallet connections, allowing readers to inspect the underlying trail.
- The browser companion is distinct from the hosted web tools: its engine and database run locally and the extension pairs to that engine.
- Grok Council reviews are optional; the README describes separate reviewer roles and calls their opinions evidence-bound.
- The repository identifies the project as Python-based, open source under the MIT license, and not archived.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up the local browser companion
Connect the local Gem Search engine to its Chrome extension so it can inspect rendered posts in an X feed, search or profile page.
Before you start
- Python 3.11 or later
- Chrome or Chromium
- macOS, Linux or Windows through WSL2 for the backend
Steps
Clone the repository, enter its directory, copy .env.example to .env, and run python3 app.py.
Open http://127.0.0.1:8787, visit Connections and copy the local pairing code.
In chrome://extensions, enable Developer mode, choose Load unpacked and select the repository's extension/ directory.
Open the toolbar popup, paste the pairing code and connect; then open an X feed, search or profile and select Release spider on this tab.
Expected outcome
The local browser companion can inspect rendered posts in the visible viewport as the user scrolls; auto-scroll is optional.
Guide limitations
- The local engine must remain running.
- Only rendered posts in the visible viewport are inspected; background tabs do not collect or auto-scroll.
- If the engine is offline, up to 200 captured posts remain queued in the extension until a later successful connection.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 8 October 2026
- Original website title
- h100envy/gem-search · Official homepage title · retained in its source language