In-depth architectural comparison of the Zensei MCP and Luxalgo MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Zensei MCP
Finance & Fintech · Remote HTTP/SSE
Quality: 74/100 (Great) | Auth: OAuth 2.0
Luxalgo MCP Server
Finance & Fintech · Local stdio
Quality: 68/100 (Great) | Auth: No auth required
Verdict Summary: Choose Zensei MCP if you need specialized Finance & Fintech tools running via a hosted cloud SSE transport. Choose Luxalgo MCP Server if your workspace requires Finance & Fintech integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Z
Choose Zensei MCP when:
You need dedicated capabilities in the Finance & Fintech domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: OAuth 2.0 (Freemium).
Live sector rotation data for AI agents. Tools: sector rotation status (100+ sectors classified as leading, lagging, improving or weakening vs the S&P 500), sector-to-stock drill-down (the stocks driving each move), and macro regime (Zensei Index risk-on / risk-off read). Remote server, OAuth with a Zensei account.
LuxAlgo Library — the encyclopedia of trading & technical analysis for AI agents. Free, keyless.
Category & Scope
Tools & Capabilities Breakdown
Zensei MCP Tools (4)
zensei_index_about
What the Zensei Index is, how to read the score, how it is built, and what this server serves. Same wording as the website FAQ. Call it once before interpreting any score.
zensei_index_today
Today's Zensei Index for U.S. equities: the final score, its regime label, and the three layer scores (structural conditions, tactical filters, regime confirmations). The Zensei Index is a RISK score from 0 to 100: LOWER IS HEALTHIER. 0-20 Supportive, 20-40 Vulnerable, 40-70 Stressed, 70-100 Restrictive. A rising score means conditions are deteriorating, not improving. Call zensei_index_indicators to see why the score sits where it does.
zensei_index_indicators
The ten indicators behind today's Zensei Index, each with its current status, the layer it scores into, its weight in that layer, and the same explanation the website shows. Use it to explain why the index sits where it does. Indicator statuses run from healthiest to most stressed: Clear or Inactive (no stress), Watch (early warning), Stress (confirmed stress), Activated or Danger (full signal). Calibrating means not enough data yet; Unknown means no data.
zensei_index_summary
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Zensei MCP is categorized under Finance & Fintech and uses a remote streaming HTTP/SSE transport. In contrast, Luxalgo MCP Server belongs to Finance & Fintech using local stdio subprocess. Select Zensei MCP when you need capabilities focused on finance & fintech and Luxalgo MCP Server when you require tools for finance & fintech.
The latest written summary of the Zensei Index, with the score and regime it was written for. A summary is rewritten only when the indicators change. Check `stale` and `ageDays` before quoting it as today's view, and prefer zensei_index_today for the current number. The Zensei Index is a RISK score from 0 to 100: LOWER IS HEALTHIER. 0-20 Supportive, 20-40 Vulnerable, 40-70 Stressed, 70-100 Restrictive. A rising score means conditions are deteriorating, not improving.
Luxalgo MCP Server Tools (48)
library_search
Search the LuxAlgo Library — the encyclopedia of trading and technical analysis. One query over 800+ concepts (alias-aware: 'stochastics' finds Stochastic Oscillator) and 800+ ready-to-use indicators. Start here whenever you have a name, informal term, or topic; results carry slugs for the get tools plus canonical URLs for citation.
library_get_concept
Explain a trading concept: the Library's full write-up as markdown — definition, formula, how traders read it, and its indicator implementations. Use for any 'what is X / how does X work' question. Needs the exact slug — find it with library_search or library_list_concepts.
library_get_indicator
Details for one indicator: what it does, how to read it, family, concept links, preview image — plus whether its source code is available (fetch the code itself with library_get_source_code). Use when the user asks about a specific indicator.
library_get_source_code
The full, working source code of a Library indicator (works on TradingView). Kept separate from library_get_indicator because sources are long — call it only when the user wants the code itself.
library_list_concepts
Browse every trading and technical-analysis concept in the Library — paginated, optionally one family. Use to enumerate a topic area or find slugs for library_get_concept; for keyword lookup prefer library_search.
library_list_indicators
Browse the indicator catalog with filters and server-side sorting (newest first by default). Filter by family, concept slug (implementations of one concept), tags (ids from library_list_tags, AND-combined), trading platform, or plan tier. Use for structured browsing — 'latest indicators', 'everything in the volatility family', 'indicators implementing liquidity sweeps'; for keyword discovery prefer library_search.
library_list_tags
The Library's indicator tag vocabulary (behavioral traits like 'Volatility', 'Trailing-Stop', 'Repainting Functionality'). Returns ids to pass as the tags filter of library_list_indicators — tags are orthogonal to the concept-family taxonomy.
library_list_families
The Library's top-level taxonomy: 17 families of trading concepts (trend, momentum, SMC/ICT, statistics, …) with concept counts and hub links. The natural first call for orientation.
library_get_family
A family's hub page as markdown — the written overview of that school of analysis plus its complete concept roster. Use after library_list_families, or when the user asks about a whole area like 'SMC' or 'Wyckoff'.
propfirms_search
Search LuxAlgo's prop-firm catalog (proprietary trading firms offering funded accounts). Combine firm filters (platforms, markets, payment/payout methods, country availability, Trustpilot, year founded) with nested challenge filters (account size, price, steps, profit split, trading rules) and offer filters — a firm matches when at least one of its challenges/offers matches all of them. Omit every filter to list all firms. Use include to nest the matching challenges, live offers, and the written overview; for one firm's full dossier prefer propfirms_get. Uncaptured (null) fields are omitted from results; nested challenges reference offers via offerIds into the firm-level offers list. This tool returns directory data (what exists and on what terms), not outcomes: for simulated pass odds on a challenge found here, use propfirms_pass_rates or propfirms_simulate with its firm and challenge ids.
propfirms_get
One prop firm's full dossier by slug: general profile (platforms, markets, payments, Trustpilot, restricted countries), every challenge with its rules, live offers with promo codes and affiliate links, and the written overview (about, rules, payout policy, FAQ). Find slugs with propfirms_search. Uncaptured (null) fields are omitted; challenges reference applicable offers via offerIds into the firm-level offers list. For simulated pass odds on this firm's challenges (reference archetypes, same engine as luxalgo.com/prop-firms), use propfirms_pass_rates.
propfirms_search_challenges
Search funded-account challenges across all visible prop firms. Filter by challenge rules (account size, fee, steps, profit split, drawdown mode, news/copy/auto trading, weekend holding, …) and by parent-firm properties. Pass propfirmId to list one firm's challenges, or challengeId to fetch specific ones. include=['offers'] returns a deduplicated top-level offers list, with each challenge referencing its applicable offers via offerIds (firm-wide offers included). Uncaptured (null) rule fields are omitted from results and never match filters. This returns each challenge's listed rules and terms, not outcomes: to simulate a challenge found here pass its ids to propfirms_simulate or propfirms_pass_rates, and to screen one strategy across many challenges at once use propfirms_validate_strategy.