GINO
not read yet
Use
- Used for
- look up US stock data through MCP
- get news updates inside Claude Code
- Has an MCP server (1 in the registry)public registry →
- MCP serverim.gino/stocks-usverified in the MCP registry
- Stateanswers, 7 toolschecked 2026-10-26
- Address to connectmcp-stocks-us.gino.im/mcp
- MCP docsmcp-stocks-us.gino.im/mcpthe vendor's page ↗
This card as JSON, for your agent →
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Figure and bar: visits/mo, estimate · year: online since
- #1
You.com
Returns live web search results and cleaned page content through APIs that AI agents and LLM apps call for grounding.
13.6k2020 - #2
Handinger
Builds AI agents that automate web tasks like searching, reading, clicking, and emailing without coding.
9.6kActiveFrom ≈ $11/mo - #3
SpeakeasyMCP · sign-in
Routes agent traffic through one identity-checked MCP gateway, enforcing security policy on every prompt and tool call.
5.8kActiveFrom $0.35 per use2021 - #4
LandbotMCP · sign-in
Builds conversational AI agents for lead generation, customer support, and sales on websites and WhatsApp.
3.7kActiveFrom ≈ $36/mo2015 - #5
Flowise
Visually build and deploy agentic AI systems with modular workflows, multi-agent orchestration, and tool integration.
3.6kMaintainedFrom $35/mo - #6
AgentX
Orchestrates, evaluates, and monitors multi-agent AI systems from development through production deployment.
1.6kActiveFrom $49/mo
Not it? Say what you need
betaThree tools from the Atlas for the job you describe, each with what fits and what does not.
No notes yet. What do you use GINO for?
Sign in to leave a noteWhat is GINO?
Orchestrates AI agents and MCP servers, with a US stocks MCP tool and a Claude Code newsline plugin. It is listed in the Atlas under Agents.
Do people use GINO?
Little sign of use.
What are alternatives to GINO?
In Agents, by use: You.com, Handinger, Speakeasy, Landbot, Flowise, AgentX.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.
How we read every tool → · By INITE Atlas Desk
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.