September 22, 2026
Interview: "The API Makes the Tool Interesting for My Own Workflows"
David, a developer and hobby investor, on combining the StockMarketScan REST API and MCP connection with the website, working within rate limits, and keeping automation to research lists only.
David, 37, developer and hobby investor. The interview was conducted in German and has been translated and lightly edited for length.
You don't only use stockmarketscan.com in the browser. What does your workflow look like?
I build small research tools for my personal market observation. That is why the API of stockmarketscan.com was especially interesting to me. The platform documents endpoints for screeners, chart patterns, market and options data. There is also an MCP connection for AI clients. That lets me build the information into my own workflow instead of using only the dashboard.
What exactly do you do with it?
I regularly fetch the screener metadata and store selected hits in a local overview. I can also query detected chart patterns for specific symbols. That saves me repetitive manual work and lets me build my own presentation. For example, I can merge hits from different lists and then sort them by my personal criteria.
What role does the website still play?
An important one. The API delivers structured data, but for the visual check I still open stockmarketscan.com and look at the charts and screener context. I don't want to process tables only. The browser helps me understand the results and look at individual names more closely. For me the website and the API complement each other rather than compete.
What do you like about the API?
The documentation is clearly structured: authentication via header, JSON responses, described parameters and rate limits. What I find especially useful is that the data source is the same one the dashboard uses. That makes it easier to connect browser research and my own workflow. I also know which endpoints are public and which features require a particular plan.
How do you deal with the rate limits?
I plan my requests deliberately and cache results instead of fetching the same data unnecessarily often. For a personal workflow that is usually enough. If a script only updates an overview once a day, the technical side is fairly simple. For more frequent requests you have to follow what the documentation says and can't just assume unlimited access.
Do you also use the AI connection?
Yes, but with clear limits. I can have an AI client query a screener list or summarize hits by certain criteria. That speeds up the research. But I don't allow automatic order execution, and I always check important information myself. The AI may help me organize data or phrase questions; it should not make unchecked investment decisions.
Can you give an example of such an analysis?
For example, I could have it find the overlap between a momentum screener and a technical screener. Then I have the shared symbols sorted by volume or chart pattern. After that I check the results manually on stockmarketscan.com. That gives me a narrower list without having to compare the individual tables by hand again and again.
Isn't that more something for professional users?
The API is certainly aimed more at advanced users. Anyone who only looks for stocks occasionally probably doesn't need it. For me it is a big plus, because I don't have to use the platform as an isolated website. I can integrate the screeners into my own process. At the same time I like that you can use stockmarketscan.com through the normal interface without any programming.
Are there limits to your automated workflow?
Of course. Data can change, a screener can return different hits, and a chart pattern is no guarantee of a price move. That is why my scripts only create research lists. They don't place orders, don't change accounts and don't replace checking the original sources. That matters to me, because otherwise automation can quickly create a false sense of security.
Your overall verdict?
I find stockmarketscan.com very convincing because it offers something for a quick start as well as for more technical workflows. The ready-made screeners help with finding ideas, the chart context with checking them and the API with automating the research. That combination is what makes the offering strong for me. I can start small and later take individual parts into my own workflow without having to build a complete software solution right away.
Related Resources
- API Documentation
- MCP Server for Claude, Cursor and other AI clients.
- All Stock Screeners
This interview reflects one user's personal experience. It is not investment advice, and screener results are research data, not recommendations.