Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Stock verdicts, trend stage, P&F, breadth, macro regime, SEC filings. Free key: api.vanoe.ai/signup
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.
VANOE_API_KEY, VANOE_API_BASE_URLValues 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": {
"vanoe-intelligence": {
"command": "uvx",
"args": [
"vanoe-intelligence-mcp"
],
"env": {
"VANOE_API_KEY": "your-value",
"VANOE_API_BASE_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add vanoe-intelligence --env VANOE_API_KEY=your-value --env VANOE_API_BASE_URL=your-value -- uvx vanoe-intelligence-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"vanoe-intelligence": {
"command": "uvx",
"args": [
"vanoe-intelligence-mcp"
],
"env": {
"VANOE_API_KEY": "your-value",
"VANOE_API_BASE_URL": "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": {
"vanoe-intelligence": {
"type": "stdio",
"command": "uvx",
"args": [
"vanoe-intelligence-mcp"
],
"env": {
"VANOE_API_KEY": "your-value",
"VANOE_API_BASE_URL": "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.
VANOE_API_BASE_URL envThese 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 7, 2026
The registry name was verified with the GitHub account vanoe-ai, which owns the repo
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: VANOE_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.1.6) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, OpenTakeoff
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.
Construction takeoff for AI agents: load plans, set scale, measure, count, export with provenance.
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.
Get a free API key in ten seconds: [https://api.vanoe.ai/signup?src=mcp-readme](https://api.vanoe.ai/signup?src=mcp-readme) — 1,000 credits a month, no card. The key page also prints the hosted MCP URL to paste into Claude.ai or ChatGPT as a connector.
Exposes the Vanoe Market Intelligence API as tools any MCP-capable AI assistant (Claude Desktop, Claude Code, Cursor, etc.) can call directly: a composite 0–100 verdict per ticker, trend-stage analysis (current and a backtest-safe weekly history), Point & Figure signals, sector breadth, the macro risk regime, SEC insider and 8-K filings, the macro calendar, and your usage.
This is a thin authenticated client, not a free tier: every tool call is a real, metered call against your plan using your own API key, exactly like calling the REST API yourself. Get a free key (1,000 credits a month, no card) here: https://api.vanoe.ai/signup?src=mcp-readme
Informational data only. Not financial advice. See https://api.vanoe.ai/terms.
The same tools are served over MCP's streamable HTTP transport by the API itself, for clients that take a URL (Claude.ai custom connectors, ChatGPT, hosted agent platforms):
https://api.vanoe.ai/mcp with Authorization: Bearer , orhttps://api.vanoe.ai/mcp/k/ for clients that cannot send headers (the key page after signup prints this URL; treat it like a password).Stateless, JSON responses, metered exactly like the REST API. Use the package below when you want the server to run on your own machine.
Download vanoe-market-intelligence.mcpb and open it with Claude Desktop (macOS or Windows). It asks for your API key once, stores it securely, and installs the server itself using the uv runtime. Source of the bundle is in mcpb/; rebuild with npx @anthropic-ai/mcpb pack mcpb vanoe-market-intelligence.mcpb.
No install step is needed with uv — uvx fetches and runs the package on demand:
uvx vanoe-intelligence-mcp
Or install it permanently with pipx install vanoe-intelligence-mcp or pip install vanoe-intelligence-mcp, which puts a vanoe-intelligence-mcp command on your PATH.
Set one environment variable, VANOE_API_KEY. VANOE_API_BASE_URL is optional and defaults to https://api.vanoe.ai.
Claude Desktop (claude_desktop_config.json) and most other clients:
{
"mcpServers": { "vanoe": { "command": "uvx", "args": ["vanoe-intelligence-mcp"], "env": { "VANOE_API_KEY": "sk_live_your_key_here" } } } }
Claude Code:
claude mcp add vanoe -e VANOE_API_KEY=sk_live_your_key_here -- uvx vanoe-intelligence-mcp
Then ask your assistant things like *"What's the verdict on NVDA and why?"*, *"Which stage are AAPL, MSFT and AMD in?"*, or *"Is the macro regime risk-on right now?"* — it will call the tools below.
| Tool | API call | Credits |
|---|---|---|
get_verdict(ticker) | GET /v1/verdict/{ticker} | 5 |
get_stage(tickers) | GET /v1/signals/stage | 1 per ticker |
get_stage_history(ticker, weeks) | GET /v1/signals/stage/history | 5 |
get_pnf(tickers) | GET /v1/signals/pnf | 1 per ticker |
get_sector_breadth() | GET /v1/sector-breadth | 1 |
get_macro() | GET /v1/macro | 1 |
get_filings(ticker) | GET /v1/filings/{ticker} | 1 |
get_short_pressure(tickers) | GET /v1/signals/short-pressure | 1 per ticker |
get_calendar() | GET /v1/calendar | 1 |
get_usage() | GET /v1/usage | 0 |
Tools never raise. Any failure — missing key, network error, quota exceeded, an unknown ticker — comes back as {"error": {"code", "message", "http_status"}} carrying the API's own message, so the assistant can explain what happened instead of crashing the call.
Webhook management is deliberately not exposed: it is account administration, not something to do mid-conversation. Use the REST API for that.
git clone https://github.com/vanoe-ai/vanoe-intelligence-mcp.git
cd vanoe-intelligence-mcp python -m venv .venv && . .venv/bin/activate # Windows: .venv\Scripts\activate pip install -e '.[test]' pytest tests VANOE_API_BASE_URL=http://localhost:8000 VANOE_API_KEY=sk_live_… vanoe-intelligence-mcp
Source lives at https://github.com/vanoe-ai/vanoe-intelligence-mcp; issues and pull requests welcome. If you also run the API server locally, install this in its own virtualenv, separate from the API server's own requirements.txt: the mcp SDK pulls in a newer starlette than the API's FastAPI pin tolerates, and sharing one environment breaks the API server with Router.__init__() got an unexpected keyword argument 'on_startup'. End users never hit this (the MCP server runs on their machine, next to their assistant).
tests/manual_e2e_smoke.py runs the real server as a subprocess over stdio against a reachable API with a real key; it is not part of pytest.
The MCP Python SDK is on v2: the server class is mcp.server.mcpserver.MCPServer (older tutorials show FastMCP at a different import path).
python -m build
twine upload dist/*
Bump version in pyproject.toml first. The older INTEL_API_KEY / INTEL_API_BASE_URL variable names are still accepted for compatibility.