Catalyst MCP Server

Catalyst MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Audited SEC catalyst signals for agents — ranked filing intel with a public track record. Free tier.

What you get

A hosted instance is live. Point any MCP-capable client at it, or POST JSON-RPC directly:

What the assistant can call

Once Catalyst is connected, these are the calls the assistant has available:

• get_convergence_picks — free
• get_track_record — free
• get_ticker_signal — intelligence
• get_thesis — intelligence
• get_sector_lean — intelligence

Configuration and credentials

You will need one environment variable: CATALYST_MCP_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

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

Choosing this one

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. Catalyst's toolset — get_convergence_picks, get_track_record, get_ticker_signal and 2 more — is a fair guide to whether it matches your workflow. It is maintained by com.catalystedgescanner; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Catalyst's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the catalyst mcp server does with a few real requests.