Deploy Market Screener MCP Server
Remote MCP server for market screeners and technical analysis
tradingview-mcp
Just deployed
Deploy and Host self hosted Market Screener MCP Server (AI/ML) on Railway
This template deploys an independent community packaging of the MIT-licensed tradingview-mcp v0.8.0 server as a private remote MCP endpoint on Railway.
About Hosting Market Screener MCP Server open-source software on Railway (self hosted Market Screener MCP Server template)
When you deploy this template, the MCP server runs as a single service in your own Railway project, and the data it handles stays with you.
This is independent community packaging of atilaahmettaner/tradingview-mcp v0.8.0. It is not affiliated with or endorsed by TradingView Inc. TradingView is a trademark of its owner and is used here only to describe the public screener endpoints the tools read.
Why Deploy Market Screener MCP Server, the self-hosted remote MCP market screener on Railway
A local stdio MCP market tool ties screener access to one machine and one client, while this deployment gives you a private HTTPS endpoint guarded by a bearer token you control.
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying Market Screener MCP Server on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Railway vs Other Hosting Providers and VPS for Market Screener MCP Server self hosting
Railway gives you a token-protected MCP endpoint with less setup than a general-purpose host.
| Provider | What You Get with Railway | What You Get with the Other Provider |
|---|---|---|
| DigitalOcean | A one-click template with a generated MCP_AUTH_TOKEN and a public HTTPS domain. | A Linux droplet where you handle Docker, firewall, and TLS. |
| AWS | One service with no volume to provision and a public domain. | Wide service choice, but you assemble the runtime yourself. |
| Hetzner | Managed deploys with no server sizing or OS patching on your side. | Low-cost servers where you own the OS, Docker setup, and token handling. |
Choose Railway for a quick start, or a VPS for the host.
Common Use Cases for hosted Market Screener MCP Server
- Shared research endpoint for a small team: Point several MCP clients at one Railway HTTPS domain plus /mcp, each sending the same bearer token, so everyone uses the same tools without a local install.
- Remote access from any MCP client: Connect a desktop or hosted AI client over HTTPS, even when the client cannot run a local stdio process.
- Technical analysis and screening queries: Ask an MCP client to run top gainers, RSI, MACD or Bollinger scans, and candlestick pattern checks against public screener endpoints.
- Protected access with a bearer token: Keep the MCP endpoint private by requiring MCP_AUTH_TOKEN in an Authorization Bearer header, or as a token query parameter for clients that cannot set headers.
Dependencies for Market Screener MCP Server Docker hosted on Railway
This template runs as one Railway service built from one container image, with no database and no volume.
Deployment Dependencies for Managed Market Screener MCP Server Service
The template creates one public service on port 8080 with no volume. The health check is /health with a 120 second timeout, and the restart policy is Always. There is no volume-related replica constraint; still start with one instance.
The template generates one variable with no input from you:
- MCP_AUTH_TOKEN: a 40 character bearer token every MCP client must send. Keep it secret. If you clear it, the endpoint becomes public.
Two optional variables are not pre-set. MARKETAUX_API_TOKEN enables the news tools. PROXY_* variables route requests through a proxy if the data source rate-limits the Railway IP.
Implementation Details for Market Screener MCP Server
The image is ghcr.io/onepush-dev/tradingview-mcp:0.8.0, the unmodified upstream ghcr.io/atilaahmettaner/tradingview-mcp:0.8.0 app plus railway/serve.py. The launcher serves the same FastMCP app over streamable HTTP on port 8080, keeps /health public, and requires MCP_AUTH_TOKEN as an Authorization Bearer header or as a token query parameter. DNS-rebinding protection is turned off because the Railway edge forwards the public hostname; the bearer token is the protection instead. A recorded test of this pinned 0.8.0 image listed 37 tools. Market data is for research only, not financial advice. Connect clients at the Railway HTTPS domain plus /mcp, and use a neutral client name such as market-screener rather than a trademark as the product brand.
How does Market Screener MCP Server compare against other tools
Market Screener MCP Server vs a local stdio MCP market tool (Local stdio Alternative)
- Access model: This template runs the unmodified upstream app as a remote HTTP endpoint with a bearer token, so clients on other machines can reach it. A local stdio tool runs only where it is installed.
- Setup effort: A local stdio tool is often quicker for one person on one laptop. Here you deploy once and paste the Railway domain plus /mcp into your client.
- Token control: MCP_AUTH_TOKEN gates every request except /health. If you clear it, the MCP endpoint becomes public.
Market Screener MCP Server vs checking screeners in a browser (Browser Screener Alternative)
- Interface: A browser screener offers visual charts and manual review. This service exposes screener and technical-analysis data as MCP tools an AI client can call.
- Coverage: The pinned 0.8.0 image listed 37 tools in a recorded test. A browser screener may offer deeper charting than this server provides.
- Statefulness: The service is stateless with no volume, so it keeps no saved screens or watchlists.
Market Screener MCP Server with Docker vs Railway (Docker Self-Host Alternative)
- Control: Running the Docker image yourself gives full control over the host, networking, and update timing. Railway handles the build, public HTTPS domain, and restarts for you.
- Healthchecks: Railway checks /health with a 120 second timeout and restarts the service under the Always policy. With plain Docker you wire up your own monitoring.
- Effort: Docker on a VPS asks for more operating work; Railway trades some control for a faster first deployment.
How to use Market Screener MCP Server on Railway?
- Open the service's Variables tab and copy MCP_AUTH_TOKEN. Every MCP client must send this token, so store it safely.
- Note the public HTTPS domain Railway assigned to the service. Your MCP endpoint is that domain with /mcp added.
- Point your client at the endpoint and send the token as an Authorization Bearer header. Clients that cannot set headers can use a token query parameter instead.
- Check /health on the domain without a token. It is the only public path.
- Confirm the tool list loads. A recorded test of this 0.8.0 packaging listed 37 tools.
- For a custom domain, change only the URL you give clients.
Use a neutral name such as market-screener for the service and client config key. The endpoint is your domain plus /mcp, the header is Authorization Bearer plus the token, and /health stays public.
How to self host Market Screener MCP Server on other VPS Services (Market Screener MCP Server self hosting guide)
Clone the Repository
Clone the packaging repository, or pull the pinned image directly.
git clone https://github.com/onepush-dev/tradingview-mcp
cd tradingview-mcp
Install Dependencies
The packaged image pins the unmodified upstream app at version 0.8.0.
docker pull ghcr.io/onepush-dev/tradingview-mcp:0.8.0
Configure Environment Variables
Set a long random bearer token.
export MCP_AUTH_TOKEN=your-long-random-token
export HOST=0.0.0.0
export MCP_PORT=8080
Start the Market Screener MCP Server Application
Run the container on port 8080, then check /health without a token and call /mcp with the Authorization Bearer header.
docker run -p 8080:8080 -e MCP_AUTH_TOKEN=your-long-random-token ghcr.io/onepush-dev/tradingview-mcp:0.8.0
On Railway, the template handles the public HTTPS domain, the health check, and the generated token for you.
Pricing and License of Market Screener MCP Server (Market Screener MCP Server pricing)
Market Screener MCP Server is released under the MIT License, which means the software is free to use, modify, and self-host.
Market Screener MCP Server hosted vs self hosted comparison (Pricing, features, costs, and more)
This template packages the MIT software, and no hosted plan is described in the pinned v0.8.0 release.
Monthly cost of self hosting Market Screener MCP Server on Railway
Railway bills on usage, so cost depends on RAM and CPU.
System Requirements for Hosting Market Screener MCP Server on a VPS
A VPS needs enough memory and CPU to run the container, plus outbound access to the public screener endpoints.
Frequently Asked Questions (FAQs)
How do I connect an MCP client to this deployment?
Point the client at your Railway HTTPS domain with /mcp added to the end, and send MCP_AUTH_TOKEN as an Authorization Bearer header.
Is /health protected by the token?
No. /health is public so Railway's health check can reach it, but /mcp requires the token on every request.
What happens if I clear MCP_AUTH_TOKEN?
The MCP endpoint becomes public, so anyone who knows your domain can call the tools.
How many tools does the server expose?
A recorded test of this pinned 0.8.0 image listed 37 tools.
Is the output financial advice?
No. Market data from this server is for research only.
Is this affiliated with TradingView?
No. This packaging is not affiliated with or endorsed by TradingView Inc. TradingView is a trademark of its owner.
Template Content
tradingview-mcp
ghcr.io/onepush-dev/tradingview-mcp:0.8.0
