AlphaAI MCP Server

AI-enriched financial news for AI agents & trading bots: search, trending, insider, scored 1-10. Exposed over MCP by the alphaai mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Every story is enriched with per-ticker analysis, a category (14 buckets), and a 1–10 relevance score, so an agent can filter to what actually matters before spending a reasoning token.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

Everything the assistant can do here goes through one of these:

• alphai_news_search — Full-text + filtered news search (query, tickers, category, dates, relevance)
• alphai_ticker_news — Latest news for one ticker (optionally incl. insider)
• alphai_trending — Biggest stories of the last 48h by relevance
• alphai_actionable_now — Breaking, decision-grade news (actionability + novelty gate)
• alphai_insider_news — SEC Form 4 insider trades + 13F ownership moves as news
• alphai_pair_analysis — Two-ticker read-across (news naming both companies)
• alphai_article — Fetch a single article by uid
• alphai_tickers — Discover supported tickers — US stocks, ETFs, crypto & foreign listings

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the alphaai mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. AlphaAI's toolset — alphai_news_search, alphai_ticker_news, alphai_trending and 5 more — is a fair guide to whether it matches your workflow. It is maintained by makeev; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.