Developer · Remote MCP server
LuxAlgo MCP
LuxAlgo for AI agents: the Library, prop firms, Market Trackers, Edge Stats, and your Trade Journal.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.LuxAlgo/luxalgo-mcp-server- Version
- 1.5.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-24
- Updated
- 2026-09-24
- Publisher
- LuxAlgo (GitHub)
- Website
- www.luxalgo.com/mcp
- Repository
- github.com/LuxAlgo/luxalgo-mcp-server
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.luxalgo.com/mcp | None |
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @luxalgo/mcp | 1.5.0 | stdio |
How to connect LuxAlgo MCP
LuxAlgo MCP is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.luxalgo.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @luxalgo/mcp version 1.5.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @luxalgo/mcp@1.5.0.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"luxalgo-mcp-server": {
"command": "npx",
"args": [
"-y",
"@luxalgo/mcp@1.5.0"
]
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Lumino MCP ServerAI-powered SRE observability for Kubernetes/OpenShift with 40+ Tekton debugging tools. | Local · stdio |
| LungeAgent-native API client: execute/test REST/GraphQL/WS/SSE with assertions, extraction, collections. | Local · stdio |
| Luogu MCP ServerSearch Luogu problems, fetch statements, explore problem sets and get practice recommendations. | Remote · HTTP |
| lurqVerify npm packages before your AI agent installs them: hallucinations, advisories, API drift. | Remote · HTTP |
| LynxLynxMCP: 100% local MCP server for the code questions grep can't answer: call graph, hybrid search. | Local · stdio |
| Lynxprompt MCPMCP server for LynxPrompt — browse, search, and manage AI configuration blueprints. | Local · stdio |
| m-dev-toolsMCP server wrapping the m-dev-tools catalog: route_intent, describe, verify. | Local · stdio |
| M1ndThe shell around your coding agent: a neuro-symbolic code graph with calibrated trust, via MCP. | Local · stdio |