Skip to content
Ticker All! logo

Ticker All!

Connects code, TradingView alerts and chat bots to MetaTrader 4 and 5 accounts, placing orders and streaming prices through one API.

At a glanceswept 2026-10-14

1.7k installs/mo

Emerging

Price
Price not read
Activity
Actively maintainedrelease 7 days ago · site updated yesterday
Company
founding year not on record
Runs as
APISDK
Your datawhat they publish, each line with its page · read 2026-10-14

These are Ticker All!'s own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.

How a program reaches itfound, not claimed · read 2026-10-14
  • MCP servercom.tickerall/mcpverified in the MCP registry
  • Stateanswers, requires sign-inchecked 2026-10-14
  • Address to connectmcp.tickerall.com
  • OpenAPI spec32 pathsthe spec ↗
  • MCP docstickerall.com/dashboard/mcpthe vendor's page ↗
  • Status pagelinked from the homepagetickerall.com/status ↗

MCP server details →

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.

Alternatives in Developer toolsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

All Developer tools tools →

Questions this page answers
  • What is Ticker All!?

    Connects code, TradingView alerts and chat bots to MetaTrader 4 and 5 accounts, placing orders and streaming prices through one API. It is listed in the Atlas under Developer tools.

  • Do people use Ticker All!?

    Emerging: 1.7k installs/mo (npm).

  • Is Ticker All! still maintained?

    Actively maintained: release 7 days ago · site updated yesterday.

  • What are alternatives to Ticker All!?

    In Developer tools, by use: IFTTT, CircleCI, Voice, Video & Chat APIs for Real-Time Interaction, Devart Software, RefineAI, Merge.

Not quite it? Describe the job

beta

Five tools from the Atlas that fit it, each judged against what you wrote.

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.