Vanoe Intelligence Mcp

io.github.peerorenPublished by GitHub account peerorenv0.1.5Updated Oct 2, 2026

Stock verdicts, trend stage, P&F, breadth, macro regime, SEC filings. Free key: api.vanoe.ai/signup

VerifiedSTDIODesktop onlyFinance Data & Analytics

Server details

Identifier: io.github.peeroren/vanoe-intelligence-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account peeroren for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.peeroren%2Fvanoe-intelligence-mcp.svg)](https://sourceweft.com/mcp/io.github.peeroren%2Fvanoe-intelligence-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server that gives an assistant metered access to Vanoe market intelligence: stock verdicts, trend stages, Point & Figure signals, breadth, macro and

What you can do: Retrieve a composite 0–100 verdict per ticker, with reasoning context from the API
When to use it: Use it when you want an assistant to answer questions about individual stocks, trend stages, sector breadth, the macro risk regime, SEC insider and 8-K filings, or the macro calendar, and you are willing to pay per call in credits.
Requirements: A local Python runtime; the README suggests uvx, pipx or pip. A Vanoe API key set in the VANOE_API_KEY environment variable (older INTEL_API_KEY is also accepted); VANOE_API_BASE_URL is optional and defaults to the hosted API. Network access to the Vanoe API. A paid or free-credit plan, since every call is metered.

Before you install

Every tool call is a real, metered call against your plan and consumes credits (for example 5 per verdict, 1 per ticker for stage, P&F and short pressure), so usage costs money or quota. The API key is a secret; the README notes the key-in-URL hosted form should be treated like a password. Ticker queries and your key are sent to the third-party Vanoe API. Output is informational data only and not financial advice.

Installation

In SourceWeft

Open Vanoe Intelligence Mcp in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Vanoe Market Intelligence MCP server

[PyPI] [NVDA verdict] [AAPL verdict]

Get a free API key in ten seconds: 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.

Hosted endpoint (no install)

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 <your key>, or
https://api.vanoe.ai/mcp/k/<your key> 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.

Claude Desktop: one-click install

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.

Install

No install step is needed with uv — uvx fetches and runs the package on demand:

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.

Configure your MCP client

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:

json

{  "mcpServers": {    "vanoe": {      "command": "uvx",      "args": ["vanoe-intelligence-mcp"],      "env": { "VANOE_API_KEY": "sk_live_your_key_here" }    }  }}

{  "mcpServers": {    "vanoe": {      "command": "uvx",      "args": ["vanoe-intelligence-mcp"],      "env": { "VANOE_API_KEY": "sk_live_your_key_here" }    }  }}

Claude Code:

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.

Tools

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.

Development

git clone https://github.com/vanoe-ai/vanoe-intelligence-mcp.gitcd vanoe-intelligence-mcppython -m venv .venv && . .venv/bin/activate     # Windows: .venv\Scripts\activatepip install -e '.[test]'pytest testsVANOE_API_BASE_URL=http://localhost:8000 VANOE_API_KEY=sk_live_… vanoe-intelligence-mcp

git clone https://github.com/vanoe-ai/vanoe-intelligence-mcp.gitcd vanoe-intelligence-mcppython -m venv .venv && . .venv/bin/activate     # Windows: .venv\Scripts\activatepip install -e '.[test]'pytest testsVANOE_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).

Releasing

Bump version in pyproject.toml first. The older INTEL_API_KEY / INTEL_API_BASE_URL variable names are still accepted for compatibility.

Source: README.md at commit 7350ec7

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.1.5LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts