Stripe MCP
MCP server integrating with Stripe - tools for customers, products, payments, and more.
Discover social and commerce APIs without login; authenticate for API calls and account data.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 11/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 31/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 JustOneAPI。按照 https://mcp.popnx.com/i/justoneapi-official-justoneapi.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(mcp.justoneapi.com) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
JustOneAPIhttps://mcp.justoneapi.com/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsJustOneAPI
用 JustOneAPI 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 JustOneAPI,或回答中出现 JustOneAPI 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
JustOneAPIhttps://mcp.justoneapi.com/mcp开启新聊天,输入前先从插件列表中选择 JustOneAPI
用 JustOneAPI 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 JustOneAPI,或回答中出现 JustOneAPI 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user justoneapi https://mcp.justoneapi.com/mcp应能看到 JustOneAPI 在列表中并显示已连接
用 JustOneAPI 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 JustOneAPI,或回答中出现 JustOneAPI 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 JustOneAPI 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 JustOneAPI,或回答中出现 JustOneAPI 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 JustOneAPI 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 JustOneAPI,或回答中出现 JustOneAPI 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://mcp.justoneapi.com/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user justoneapi https://mcp.justoneapi.com/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"justoneapi": {
"url": "https://mcp.justoneapi.com/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"justoneapi": {
"type": "http",
"url": "https://mcp.justoneapi.com/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月18日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
search_endpointsFind JustOneAPI endpoint candidates from natural language. Returns endpoint_id candidates; call get_endpoint_schema next.
get_endpoint_schemaGet the full schema and parameter contract for an endpoint_id returned by search_endpoints.
call_endpointValidate params and make one JustOneAPI endpoint call by endpoint_id. The call may incur charges under the bound API Token's current pricing and budget. Params should use snake_case names from get_endpoint_schema.
get_account_balanceGet the current JustOneAPI token's available balance and currency. Use this when the user asks about account balance, remaining balance, or whether the token can continue calling APIs.
get_usage_summaryGet the current JustOneAPI token's API usage and spending summary, including recent call trends and spending trends.
list_platformsList supported JustOneAPI platforms and endpoint counts.
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 justoneapi-official 验证,该账户拥有此仓库
代码最后更新于6天前
使用 MIT
在 333 毫秒内响应(HTTP 200)
无需登录
已读取 6 个工具描述,未发现针对 AI 的隐藏指令
云端地址最近 4 次检查中有 4 次响应 · 最近一次 333 ms · 检查于 2026年11月18日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/justoneapi-official-justoneapi)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于6天前,最新版本(2.0.1)于10天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:Stripe MCP, flightclaw, Trade It, Marketplace Ad Pros: Amazon Ads & Seller Central, idealo MCP Server
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP server integrating with Stripe - tools for customers, products, payments, and more.
Search ~300 airlines and book flights with a checkout link. OAuth sign-in by email code.
Connect brokerage accounts to AI assistants: holdings, orders, asset lookup, and approved trading.
Amazon Ads, Seller Central, Vendor Central and AMC data for AI agents. Read-only by default.
Search products, compare prices and discover deals across 6 European markets with your AI assistant.
| 本项 JustOneAPI | Stripe MCP | flightclaw | Trade It | Marketplace Ad Pros: Amazon Ads & Seller Central | idealo MCP Server | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 是 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 4/4 | 4/4 | 5/5 | 4/4 | 4/4 |
| 许可证 | MIT | MIT | MIT | CC0-1.0 | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
简体中文 | English
Use JustOneAPI in MCP clients such as ChatGPT, Codex, Cursor, Hermes Agent, and other AI assistant tools.
JustOneAPI MCP helps your assistant find the right JustOneAPI endpoint, inspect the required parameters, and call APIs through your JustOneAPI authorization.
JustOneAPI MCP supports remote Streamable HTTP and local stdio. Current verified and compatibility paths include:
As of October 22, 2026, ChatGPT CIMD connections can fail during authorization and are temporarily not recommended. Entering the URL and choosing OAuth alone can select CIMD automatically. A working DCR connection does not establish CIMD compatibility. CIMD guidance will resume after server-side network access and the complete authorization flow have been verified; migration alone does not establish availability. Existing working DCR connections can remain in use.
Compatibility depends on OAuth registration support and account or workspace policy. Clients without OAuth can keep using a legacy API Token header or local stdio.
Production supports DCR OAuth. Use this URL and explicitly select DCR using the client instructions below:
https://mcp.justoneapi.com/mcp
Compatible clients discover the protected-resource metadata, redirect you to auth.justoneapi.com, and ask for the MCP scopes shown on the consent page. No JustOneAPI API Token needs to be pasted into the client. Entry points, OAuth registration methods, and account restrictions vary by client. ChatGPT discovery can prefer CIMD, so check the selected registration method.
Developer mode in settings if your account requires it. Open Plugins and select + → Add custom MCP server. Enter a name, description, and the /mcp URL above. Choose OAuth, expand Advanced OAuth settings, and wait for discovery. Set Registration method to Dynamic Client Registration (DCR). Confirm Registration URL is https://auth.justoneapi.com/oauth2/register, select the scopes you need, then create and install the plugin. No client ID, client secret, or static API Token is required. Sign in to JustOneAPI and approve access when connecting or invoking a protected tool. If DCR is unavailable, use the Codex DCR setup below or contact support instead of repeatedly retrying default CIMD.codex mcp add justoneapi \
--url https://mcp.justoneapi.com/mcp
codex mcp login justoneapi \ --oauth-client-registration dcr
Codex CLI and the Codex IDE extension share MCP configuration. ChatGPT web connections are configured separately and do not inherit the DCR choice from a Codex login. See the official OpenAI MCP documentation and OpenAI authentication documentation.
An authorization request with client_id=https://chatgpt.com/oauth/client.json uses CIMD. Check the registration method in advanced settings. Other problems can also cause invalid_request. If DCR fails, send support the time, registration method, and error message without API Tokens, authorization codes, or other credentials.
OAuth for Claude.ai, Claude Desktop, and Claude Code remains under compatibility testing and is not yet offered as a generally supported OAuth connection. Claude Code can use an existing API Token with --header "Authorization: Bearer your_token"; do not treat the generic JSON below as a Claude Code configuration.
The authorization page shows the requested scopes. An account owner selects an existing API Token or creates a dedicated one; a Token Member can only use the Token assigned to that member. Disconnecting the app later revokes only its OAuth connection; it does not disable or delete the linked API Token.
The existing header-based connection remains supported for compatibility:
{
"mcpServers": { "justoneapi": { "url": "https://mcp.justoneapi.com/mcp", "headers": { "Authorization": "Bearer your_token" } } } }
As of 2026-08-25, npm latest is still the legacy 1.0.1 package, not the v2 implementation in this repository. If you require local stdio, pin the version so the legacy CLI is not mistaken for the hosted v2 service:
{
"mcpServers": { "justoneapi": { "command": "npx", "args": ["-y", "justoneapi-mcp@1.0.1"], "env": { "JUSTONEAPI_TOKEN": "your_token" } } } }
Legacy 1.0.1 supports Node.js 18 or newer, and its tool layout is not the same as the hosted v2 service. OAuth applies only to the remote Worker; stdio continues to read JUSTONEAPI_TOKEN locally. Update this version guidance after v2 is actually published to an npm dist-tag.
Catalog builds and dynamic releases use built-in public-safety validation and require no operator security registry or secret. Runtime API and account calls return the upstream payload without MCP-layer response truncation.
The hosted server allows anonymous initialize, tools/list, ping, and the initialization notification. The catalog tools list_platforms, search_endpoints, and get_endpoint_schema also work without a Token or login. They only read the public catalog; they do not query an account or call a paid API.
Stateless clients using protocol 2026-07-28 can use anonymous server/discover instead of the legacy initialization handshake.
Only call_endpoint, get_account_balance, and get_usage_summary require an API Token or OAuth authorization. Missing credentials return HTTP 401; clients can use the Bearer challenge to discover the authorization server. Public tools are advertised as noauth, and protected tools retain their OAuth scopes.
OAuth users select the API Token to link on the authorization page and do not paste it into the client. The existing API Token remote compatibility method uses:
Authorization: Bearer your_token
or, for local stdio:
JUSTONEAPI_TOKEN=your_token
Local stdio uses the environment variable above. Never commit a real Token to a repository.
Protected OAuth calls use these least-privilege scopes:
mcp:api:call — call a JustOneAPI endpoint.mcp:account:read — view balance and usage.The existing mcp:catalog:read scope remains supported for compatibility with previous OAuth grants, but catalog queries no longer require it. Supplied invalid or expired OAuth credentials are rejected rather than silently treated as anonymous.
call_endpoint may incur charges under the API Token linked during OAuth and its current pricing, permissions, balance, and budget. It validates the endpoint and parameters before obtaining a short-lived delegation token, then makes exactly one upstream dispatch. It does not automatically retry an uncertain timeout, network failure, or HTTP 502/503/504 result.
Legacy API Tokens are still sent to the JustOneAPI backend in the established query/form format. OAuth access and delegation tokens are never put in backend URLs or form bodies; delegation tokens are sent only as an Authorization Bearer header.
Production currently runs in dual mode. OAuth is additive and feature-flagged, and these switches remain the deployment and rollback boundary:
JUSTONEAPI_OAUTH_MODE=off keeps the remote service legacy-only and hides OAuth discovery metadata.JUSTONEAPI_OAUTH_MODE=dual accepts both existing API Tokens and standard OAuth on the exact https://mcp.justoneapi.com origin.workers.dev routes remain legacy-only, even if the variable is set to dual.The Worker uses private_key_jwt for Authorization Server introspection and RFC 8693 token exchange. Store the private JWK set and active kid as Worker secrets; never commit .dev.vars, PEM files, or private JWK sets. Rotate keys by publishing old and new public keys first, switching the active kid second, and removing the retired key only after the overlap period.
npm 2.0 will first be published under the next dist-tag through OIDC trusted publishing. After the exact published artifact passes the Node.js 20, 22, and 24 smoke checks, an operator promotes it separately with npm 2FA using npm dist-tag add justoneapi-mcp@2.0.0 latest. This is never automated with an NPM_TOKEN. See RELEASE.md.
Ask your MCP client naturally:
Find the Xiaohongshu note comments API and tell me which parameters are required.
More examples:
Which Douyin APIs can get video details?
Call the Xiaohongshu note comments API with this note ID: xxxxx.
List the Weibo search-related APIs and explain when to use each one.
Continue to the next page of results.
Check my JustOneAPI balance.
Show my recent API usage and spending.
The API returned code 400. Help me check which parameter might be wrong.
The API returned code 601 or 602. What does it mean?
The assistant can search available JustOneAPI endpoints, explain required parameters, call the selected API after you provide the needed values, and help interpret common response codes.
MIT