AI assistants (MCP)
The algoum API is also a remote Model Context Protocol server. Connect your AI assistant to it and ask in plain language - the assistant looks up insider trades, material events and fund holdings for you. Nothing to install: an address and your API key are all it takes.
| URL | https://api.algoum.de/v1/mcp |
| Transport | Streamable HTTP |
| Authentication | Your API key as Authorization: Bearer <key> |
1. Get your API key
The assistant uses the same key as the REST API. Create it in your dashboard and keep it in an environment variable, or let your app prompt for it. Create one key per app or machine, so each one stays under your control, and revoke keys at any time:
export ALGOUM_API_KEY="paste-your-key-here"2. Check the connection
This asks the server for its tools; a list of tool definitions means the key and the address are right.
curl -s https://api.algoum.de/v1/mcp \
-H "Authorization: Bearer $ALGOUM_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'3. Add the server to your assistant
Some assistants can install the server for you - look for algoum in the MCP Registry, or use APM below. Otherwise use the values from the table above in your assistant.
Claude Code
claude mcp add --transport http algoum-mcp https://api.algoum.de/v1/mcp \
--header "Authorization: Bearer $ALGOUM_API_KEY"Verify with claude mcp list.
VS Code (GitHub Copilot)
Create .vscode/mcp.json in your project, or run MCP: Open User Configuration to use it in all projects. VS Code asks for the key on first start and does not store it in the file.
{
"inputs": [
{ "type": "promptString", "id": "algoum-key", "description": "algoum API key", "password": true }
],
"servers": {
"algoum-mcp": {
"type": "http",
"url": "https://api.algoum.de/v1/mcp",
"headers": { "Authorization": "Bearer ${input:algoum-key}" }
}
}
}Switch the chat to agent mode and check in the tools list that the algoum-mcp tools are enabled.
Cursor
Create .cursor/mcp.json in your project, or ~/.cursor/mcp.json for all projects. The key is read from the environment variable of step 1, so it does not end up in the file. Start Cursor from a shell in which ALGOUM_API_KEY is set, then check under Settings → MCP that the server is connected.
{
"mcpServers": {
"algoum-mcp": {
"url": "https://api.algoum.de/v1/mcp",
"headers": { "Authorization": "Bearer ${env:ALGOUM_API_KEY}" }
}
}
}IntelliJ IDEA and other JetBrains IDEs
With the GitHub Copilot plugin: open Settings → Tools → GitHub Copilot → Model Context Protocol (MCP), choose Configure and add the server to mcp.json. Then switch the Copilot chat to agent mode and check that the algoum-mcp tools are listed.
{
"servers": {
"algoum-mcp": {
"type": "http",
"url": "https://api.algoum.de/v1/mcp",
"headers": { "Authorization": "Bearer <your key>" }
}
}
}With JetBrains AI Assistant: open Settings → Tools → AI Assistant → Model Context Protocol (MCP), choose Add, then As JSON, paste the configuration and wait until the server shows as connected.
{
"mcpServers": {
"algoum-mcp": {
"url": "https://api.algoum.de/v1/mcp",
"headers": { "Authorization": "Bearer <your key>" }
}
}
}GitHub Copilot CLI
Add the server to ~/.copilot/mcp-config.json, then run /mcp in the CLI to see algoum-mcp connected.
{
"mcpServers": {
"algoum-mcp": {
"type": "http",
"url": "https://api.algoum.de/v1/mcp",
"headers": { "Authorization": "Bearer <your key>" },
"tools": ["*"]
}
}
}Install with APM
APM (Agent Package Manager) sets the server up for the assistant you choose. Run it in your project; it reads the key from the environment variable of step 1, so the key does not end up in any file. Replace vscode with copilot, claude, cursor or another assistant; apm targets lists them all.
apm marketplace add fi4all/algoum-mcp
apm install algoum-mcp@algoum-marketplace --target vscodeWhat you can ask
Ask for what you want to know - the assistant picks the right tools itself.
- “Which insiders bought NVIDIA shares in the last 7 days?”
- “Where did at least 3 insiders buy within the last 14 days?”
- “Which 8-K filings about cyber incidents came in today?”
- “What material events did Boeing report this year?”
- “Who holds Apple in 2026-Q1, and what is the institutional sentiment?”
- “Give me the SEC filing behind that trade.”
Available tools
One read-only tool per endpoint of the API. Each returns the same response as the REST call, so paging works through the cursor argument as described in the conventions.
| Tool | What it does |
|---|---|
insider_ | Search insider trades |
insider_ | Latest insider trades across the market |
insider_ | Get a single transaction |
insider_ | Find cluster buys |
insider_ | Officer buy/sell ratio |
events_ | Search material events |
events_ | Most recently filed events |
events_ | Get a single event |
institutional_ | Search funds and managers |
institutional_ | Get a fund's portfolio |
institutional_ | Who holds a stock? |
institutional_ | Aggregated buy/sell picture per stock |
institutional_ | Most recently filed 13F disclosures |
resolve_ | Ticker and CIK resolution, company search |
filings_ | Get the original SEC filing |
get_ | Data freshness per source |
get_ | The OpenAPI specification, for details the tool descriptions leave out |
Good to know
- Read-only access to published SEC data - the assistant cannot change anything.
- Tool calls count against the same key and the same rate limit as REST requests (see conventions).
- The streams have no tool: a push stream does not fit a question and an answer. The assistant asks for the most recent events or cluster buys instead.
- Insider trades and material events become available within minutes of being filed.
- Timestamps are in US Eastern Time, exactly as the SEC reports them.
- 13F values are the holdings a fund reported for a quarter, so they describe positions rather than money flows.
get_statustells the assistant how current each data source is. - Sign-in through OAuth is not supported yet, so assistants that only connect that way cannot use the server for now.
Source and feedback
The setup guide and its updates are public on GitHub at fi4all/algoum-mcp. The server is also listed in the MCP Registry and on Glama. Questions, or an assistant missing from this page? Talk to us.