SolidInvoice
Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.
Screen and score stocks with the Quality Screener engine: filters, custom scores, and history.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 20/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Quality Screener。按照 https://mcp.popnx.com/i/quality-screener-qscreener.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(mcp.qualityscreener.io) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Quality Screenerhttps://mcp.qualityscreener.io/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsQuality Screener
用 Quality Screener 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Quality Screener,或回答中出现 Quality Screener 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Quality Screenerhttps://mcp.qualityscreener.io/mcp开启新聊天,输入前先从插件列表中选择 Quality Screener
用 Quality Screener 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Quality Screener,或回答中出现 Quality Screener 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user qscreener https://mcp.qualityscreener.io/mcp应能看到 Quality Screener 在列表中并显示已连接
用 Quality Screener 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Quality Screener,或回答中出现 Quality Screener 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 Quality Screener 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Quality Screener,或回答中出现 Quality Screener 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 Quality Screener 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Quality Screener,或回答中出现 Quality Screener 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://mcp.qualityscreener.io/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user qscreener https://mcp.qualityscreener.io/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"qscreener": {
"url": "https://mcp.qualityscreener.io/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"qscreener": {
"type": "http",
"url": "https://mcp.qualityscreener.io/mcp"
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 quality-screener 验证,该账户拥有此仓库
代码最后更新于今天
使用 MIT
在 225 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/quality-screener-qscreener)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于今天,最新版本(0.1.0)于4个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:SolidInvoice, Signal8, Journalit, Beancount.io, Tapetide - Indian Stock Market MCP
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.
SEC filings, dilution, insider & institutional ownership, and political-trade data for AI agents.
Trading journal in Obsidian. Ask Claude or ChatGPT about your trades; edits are previewed first.
Query, edit, and reconcile a hosted Beancount ledger: BQL, reports, files, and bank imports.
48 tools for ~8,000 NSE & BSE stocks: quotes, screener, financials, filings, FII/DII, options
| 本项 Quality Screener | SolidInvoice | Signal8 | Journalit | Beancount.io | Tapetide - Indian Stock Market MCP | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 否 | 否 | 是 | 否 | 否 | 是 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 4/6 | 5/5 | 4/4 | 4/4 | 5/5 |
| 许可证 | MIT | MIT | MIT | NOASSERTION | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
A standalone Model Context Protocol (MCP) server that exposes the Quality Screener stock-screening engine as tools for AI agents (Claude, Cursor, and any other MCP client).
The served universe is ≈40,000 scored companies across 100+ countries and 67 exchanges (canonical listings as of 14 Nov 2026; Argentine .BA symbols and preferred shares are excluded). Quality Screener is for informational and educational purposes only and does not constitute investment advice.
Once connected, an agent can screen and filter the scored universe, compute custom quality scores, inspect score history, manage saved scoring systems, and generate shareable screen links — acting as the signed-in user, against the same data they see in the web dashboard.
CustomScoreConfig┌─────────────┐ MCP (stdio | streamable-HTTP) ┌──────────────────┐ HTTPS ┌──────────────────────┐
│ AI agent │ ────────────────────────────────► │ qscreener-mcp │ ────────► │ Quality Screener API │ │ (MCP client)│ ◄──────────────────────────────── │ (this server) │ ◄──────── │ (FastAPI backend) │ └─────────────┘ tool calls / JSON └──────────────────┘ REST └──────────────────────┘
Each MCP tool maps to one Quality Screener REST endpoint. The server attaches the caller's bearer token to every outbound request (header X-Stobot-CLI-Token, Authorization: Bearer … also accepted) and returns the decoded JSON. There is no business logic in the server itself — it is a typed, authenticated façade over the API.
It runs in two transport modes:
| Transport | Use | Authentication |
|---|---|---|
stdio (default) | A local agent (e.g. Claude Code) launches the server as a subprocess | Token from $QSCREENER_TOKEN or ~/.config/qscreener/credentials.json |
streamable-http | A remote, externally reachable deployment (e.g. Railway) | End-to-end MCP OAuth 2.0 — the client opens the browser once, then sends the token automatically; or a per-request X-Stobot-CLI-Token header |
Over HTTP the MCP endpoint is served at /mcp.
The easiest way to use the server is to point your MCP client at the hosted deployment. No token to copy — the client triggers a browser sign-in on first connect:
{
"mcpServers": { "qscreener": { "type": "streamable-http", "url": "https://mcp.qualityscreener.io/mcp" } } }
On first use your browser opens the Quality Screener sign-in page. Approve once, and the agent stays connected. You need a Quality Screener account; the agent inherits exactly your access.
Requires uv.
# Install dependencies
uv sync
uv run qscreener-mcp
QSCREENER_MCP_TRANSPORT=streamable-http QSCREENER_MCP_PORT=8080 \ QSCREENER_API_URL=http://localhost:8001 \ uv run qscreener-mcp
With Docker:
docker build -t qscreener-mcp .
docker run --rm -p 8080:8080 \ -e QSCREENER_API_URL=https://your-backend.example.com \ -e QSCREENER_MCP_PUBLIC_URL=http://localhost:8080 \ qscreener-mcp
By default the container runs the streamable-http transport on port 8080.
All configuration is via environment variables, resolved at startup.
| Env var | Default | Meaning | |
|---|---|---|---|
QSCREENER_API_URL | http://localhost:8001 | Base URL of the Quality Screener backend API the tools call | |
QSCREENER_MCP_TRANSPORT | stdio | stdio, streamable-http, or sse | |
QSCREENER_WEBSITE_URL | http://localhost:3001 | Web-app base URL used to build the OAuth browser-login link and shareable screen URLs | |
QSCREENER_MCP_PUBLIC_URL | `http://localhost:{PORT\ | 8080} (or https://$VERCEL_URL` on Vercel) | Publicly reachable base URL of this server; used as the OAuth issuer and callback URL |
QSCREENER_OAUTH_SIGNING_KEY | — | HMAC key for signed OAuth state, authorization codes, and client registrations. Required on Vercel; optional on a single long-lived process | |
PORT | — | Bind port for HTTP transports (Railway sets this automatically) | |
QSCREENER_MCP_PORT | 8080 | Bind port fallback when PORT is unset | |
QSCREENER_MCP_HOST | 0.0.0.0 | Bind host for HTTP transports | |
QSCREENER_TOKEN | — | Bearer-token override for stdio mode (single user) | |
QSCREENER_CONFIG_DIR | ~/.config/qscreener | Directory holding credentials.json for stdio mode |
The server resolves a bearer token for each call with the following precedence:
X-Stobot-CLI-Token, then Authorization: Bearer .token field.For a streamable-http deployment, authentication is fully automated via the MCP OAuth flow:
/oauth/callback.The token is validated on each request by calling the backend's /v1/cli/auth/whoami endpoint, so a revoked or expired token is rejected immediately. The server never persists user tokens. Access tokens *are* the CLI token, so they need no local store. Pending login state, authorization codes, and dynamically registered clients are HMAC-signed JWTs when QSCREENER_OAUTH_SIGNING_KEY is set, which is what a multi-instance host (Vercel) needs; a single process without the key keeps the original in-memory behaviour.
Mint a token through the browser login flow and store it locally, then run the server over stdio:
qscreener auth login # opens the web app, stores a token
cat ~/.config/qscreener/credentials.json # the "token" field is your bearer token
Or set QSCREENER_TOKEN directly for CI / scripted use.
All tools require authentication. Filters use OR logic within a filter and AND logic across filters. Market caps are always in USD.
| Tool | Signature | Description |
|---|---|---|
auth_status | auth_status() | Whether a token is present and which user it authenticates as. |
account_profile | account_profile() | The signed-in user's profile (email, username, organization). |
health | health() | API and database health check. |
| Tool | Signature | Description |
|---|---|---|
scores_top | scores_top(limit=20) | Top tickers by quality score, as a {ticker: score} map. |
scores_list | scores_list(ticker=None, sectors=None, industries=None, countries=None, currencies=None, exchanges=None, min_score=None, max_score=None, min_market_cap_usd=None, max_market_cap_usd=None, sort_by="quality_score", sort_order="desc", offset=0, limit=50, include_duplicates=False) | List scored tickers with optional filters. |
scores_show | scores_show(ticker) | Full score row(s) for a single ticker. |
scores_for_tickers | scores_for_tickers(tickers, scoring_system_id=None) | Current scores for a specific list of tickers, under default scoring or a saved scoring system. Unknown tickers are omitted. |
scores_statistics | scores_statistics(sectors=None, min_score=None, max_score=None, min_market_cap_usd=None, max_market_cap_usd=None) | Min / max / average score statistics for a filtered universe. |
scores_market_cap | scores_market_cap(sectors=None, min_score=None) | Aggregated total market cap (USD) for a filtered universe. |
score_compute | score_compute(config, scoring_universe=None, sectors=None, industries=None, regions=None, countries=None, currencies=None, exchanges=None, min_market_cap_usd=None, max_market_cap_usd=None, sort_by="quality_score", sort_order="desc", offset=0, limit=50, include_duplicates=False) | Compute custom scores from a CustomScoreConfig. scoring_universe picks the peer group (changes the scores); the other filters select rows (do not). |
| Tool | Signature | Description |
|---|---|---|
screen_share | screen_share(config) | Persist a CustomScoreConfig and return a public, copy-pasteable share link (url, slug, created, view_count). Content-addressed: an identical config returns the same link. |
| Tool | Signature | Description |
|---|---|---|
filters_list | filters_list() | Available filter values (sectors, industries, countries, currencies, exchanges). |
tickers_list | tickers_list(limit=None) | Available tickers, optionally truncated to limit. |
tickers_search | tickers_search(query) | Search available tickers by case-insensitive substring. |
Dates are YYYY-MM-DD. Pass scoring_system_id to compute history against a saved scoring system instead of the default quality score.
| Tool | Signature | Description |
|---|---|---|
history_ticker | history_ticker(ticker, start=None, end=None, scoring_system_id=None) | Score history for a single ticker over a date range. |
history_batch | history_batch(tickers, start=None, end=None, scoring_system_id=None) | Score history for several tickers at once. |
history_top | history_top(top=10, scoring_system_id=None) | Fetch the current top-N tickers and return their score history. |
A scoring system is a named, reusable CustomScoreConfig stored against your account.
| Tool | Signature | Description |
|---|---|---|
systems_list | systems_list() | List your saved scoring systems. |
systems_show | systems_show(system_id) | Show a saved scoring system by ID. |
systems_create | systems_create(name, config, description=None) | Create a saved scoring system from a config object. |
systems_update | systems_update(system_id, name=None, config=None, description=None) | Update a saved scoring system. |
systems_delete | systems_delete(system_id) | Delete a saved scoring system. |
systems_apply | systems_apply(system_id) | Apply a saved scoring system (increments its usage count). |
CustomScoreConfigscore_compute, screen_share, and the systems_* tools accept a CustomScoreConfig object describing how to weight financial metrics. Its shape mirrors the score builder in the web dashboard: weighted metric groups, each containing w