Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Local stdio MCP bridge for XCREENER's XQL screener API — validate, explain, and run queries.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
XCREENER_API_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"xcreener": {
"command": "npx",
"args": [
"-y",
"@xcreener/mcp"
],
"env": {
"XCREENER_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add xcreener --env XCREENER_API_KEY=your-value -- npx -y @xcreener/mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"xcreener": {
"command": "npx",
"args": [
"-y",
"@xcreener/mcp"
],
"env": {
"XCREENER_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"xcreener": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@xcreener/mcp"
],
"env": {
"XCREENER_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified against the domain xcreener.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: XCREENER_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.1) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Tool Guardian
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Too many MCP servers eating your context? A router that loads each tool's schema only when needed.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Local stdio MCP bridge for XCREENER's XQL screener API — validate, explain, and run XQL queries from Claude Desktop, Cursor, Windsurf, or any stdio MCP client.
XCREENER is a market screener that scans Crypto, Forex, Indices, Commodities, and Metals simultaneously, so you don't have to check charts one at a time. It's built for beginner traders through ready-made screeners as well as for developers and AI agents, who can express custom conditions in XCREENER Query Language (XQL) and run them instantly via a REST API or MCP. Learn more at xcreener.com.
This package is the local stdio bridge to XCREENER's XQL API specifically. It exposes xql_validate, xql_explain, xql_run, and xql_nl_reference as MCP tools, so any stdio MCP client can check and execute XQL screens against live market data without you writing any HTTP glue code.
.mcpb)Download the latest xcreener.mcpb from this repo's Releases page, then double-click it to install — Desktop asks for your API key in a masked field as part of that same dialog. No JSON to hand-edit, no separate Node install.
Add this to your client's MCP server config (e.g. Cursor, Windsurf, Claude Code):
{
"mcpServers": { "xcreener": { "command": "npx", "args": ["-y", "@xcreener/mcp"], "env": { "XCREENER_API_KEY": "your-api-key" } } } }
git clone https://github.com/xcreener/xcreener-mcp.git
cd xcreener-mcp npm install npm run build
Then point your client at node dist/index.js with XCREENER_API_KEY set in its environment.
| Variable | Required | Description |
|---|---|---|
XCREENER_API_KEY | Yes | Your XCREENER API key, from xcreener.com/account/api-key. |
The key is checked lazily — an invalid or missing key won't stop the server from starting, it'll just surface as an auth error the first time a tool is called.
| Name | Type | Description |
|---|---|---|
xql_validate | Tool | Validate XQL query text by parsing and planning it, without executing it against live data. |
xql_explain | Tool | Parse and plan an XQL query, returning its execution plan and a human-readable explanation. |
xql_run | Tool | Parse, plan, and execute an XQL query against live market data, returning matching instruments. |
xql_nl_reference | Tool | Reference document mapping natural-language trading phrases to XQL syntax. |
Under the hood, the assistant calls the xql_nl_reference tool, translates your plain-English ask into an XQL query, and calls xql_validate/xql_run — what you see is just the human-visible conversation. A few real examples:
Multi-market screen
You: check all markets and see which instruments are oversold at the moment
XCREENER runs (same query per market —
CRYPTO,FOREX,INDICES,METALS,COMMODITIES):
`xql
market = "CRYPTO"
timeframe = h1
columns = [rsi(14)]
sort = rsi(14) asc
rsi(14) < 30
`
XCREENER: Oversold (RSI(14) < 30, hourly) across all markets:
| Market | Symbol | RSI(14) |
| ----------- | -------- | ------- |
| Crypto | BTCUSDT | 26.3 |
| Crypto | ETHUSDT | 27.5 |
| Crypto | XRPUSDT | 28.0 |
| Commodities | WHEATUSD | 21.0 |
| Commodities | CORNUSD | 22.6 |
Forex, Indices, and Metals had no oversold matches.
Single-market snapshot
You: can you give me updates on how the metals are doing?
XCREENER runs:
`xql
market = "METALS"
timeframe = h1
let uptrend = close > sma(50)
columns = [close, roc(1), rsi(14), uptrend]
sort = roc(1) desc
close > 0
`
XCREENER: Metals snapshot, hourly:
| Symbol | Close | 1h ROC | RSI(14) | Trend (vs SMA50) |
| ----------------- | -------- | ------ | ------- | ---------------- |
| XPTUSD (Platinum) | 1,637.98 | +0.03% | 54.8 | Uptrend |
| XAGUSD (Silver) | 57.48 | +0.02% | 38.6 | Downtrend |
| XAUUSD (Gold) | 4,043.69 | +0.01% | 41.0 | Downtrend |
Overall: fairly quiet, no oversold/overbought extremes (all RSI 38–55). Platinum's the strongest — up-trending with the best momentum — while gold and silver are drifting below their 50-hour average.
Cross-pair aggregate analysis
You: which currency is the weakest and strongest?
XCREENER runs:
`xql
market = "FOREX"
timeframe = h1
columns = [close, roc(1)]
sort = roc(1) desc
close > 0
`
XCREENER: Based on the 1h ROC across all 28 pairs (aggregating each currency's average move against the other seven):
| Rank | Currency | Avg 1h Strength |
| ------------- | -------- | --------------- |
| 1 (strongest) | CHF | +0.0414% |
| 2 | JPY | +0.0184% |
| ... | | |
| 8 (weakest) | USD | -0.0421% |
Strongest: CHF — up against every other major this hour. Weakest: USD — sold broadly against EUR, GBP, AUD, JPY, and CHF alike.
Actionable trade plan
You: NZD looks like the strongest currency this week — which pair should I long based on that, and what stop-loss/take-profit levels make sense?
XCREENER runs:
`xql
market = "FOREX"
timeframe = h1
symbols = ["NZDUSD"]
columns = [close, atr(14), sma(50), highest(high, 20), lowest(low, 20), w::lowest(low, 52), rsi(14)]
close > 0
`
XCREENER: Idea: Long NZDUSD — the cleanest multi-timeframe confluence: NZD is the #2 strongest currency of the week, daily is non-conflicting, and hourly shows an uptrend (close 0.5881 > SMA(50) 0.5846) with bullish-but-not-overbought momentum (RSI(14) 60.8).
| | Level | Rationale |
| --------- | ------- | --------------------------------------------------- |
| Entry | ~0.5881 | Current price |
| Stop Loss | 0.5845 | Below the 20h swing low and h1 SMA(50); ~3× ATR(14) |
| TP1 | 0.5940 | ~1.6:1 R:R, partial scale-out |
| TP2 | 0.6093 | Weekly 52-week high, ~5.9:1 R:R |
_Not financial advice — a technical read off the pulled data; confirm against execution/spread costs before entering._
npm run dev # tsup --watch
npm run build # build dist/index.js npm run build:mcpb # build + pack dist-mcpb/xcreener.mcpb npm run lint npm run typecheck
The build produces a single bundled ESM file (dist/index.js) with all dependencies inlined via tsup, so both the npm package and the .mcpb bundle ship without node_modules.
MIT — see LICENSE.