What it does
Read-only MCP for AI usage profiles, leaderboards, stats, and docs; no writes or private data.
- Connects 在云端运行
- Account or key No key needed
- Category 开发者工具
可搭配使用
教 AI 做这类工作的 Skill,可与本项一起使用
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
graphify
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
为什么排在这里
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 20/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
安装
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 UsageMax public observability。按照 https://mcp.popnx.com/i/symbaiex-usagemax.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(usagemax.com) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
打开 Claude 的 Connectors 页面
CustomizeConnectors
点击“Add” → “Custom” → “Web”,填写这 2 项
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Name · 名称UsageMax public observabilityRemote MCP server URL · 地址https://usagemax.com/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
在聊天中开启
+ConnectorsUsageMax public observability
试一试
用 UsageMax public observability 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 UsageMax public observability,或回答中出现 UsageMax public observability 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
在网页版 ChatGPT 打开添加 MCP 的页面
Plugins+Add custom MCP server
填写名称和地址
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Name · 名称UsageMax public observabilityConnection · 地址https://usagemax.com/mcp在聊天中选择 UsageMax public observability
开启新聊天,输入前先从插件列表中选择 UsageMax public observability
试一试
用 UsageMax public observability 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 UsageMax public observability,或回答中出现 UsageMax public observability 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
打开终端
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
粘贴这条命令并按 Enter
claude mcp add --transport http --scope user usagemax https://usagemax.com/mcp在 Claude Code 中输入 /mcp
应能看到 UsageMax public observability 在列表中并显示已连接
试一试
用 UsageMax public observability 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 UsageMax public observability,或回答中出现 UsageMax public observability 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
在 Cursor 中以 Agent 模式打开 AI 聊天
试一试
用 UsageMax public observability 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 UsageMax public observability,或回答中出现 UsageMax public observability 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
在 VS Code 中以 Agent 模式打开 AI 聊天
试一试
用 UsageMax public observability 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 UsageMax public observability,或回答中出现 UsageMax public observability 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://usagemax.com/mcpJSON 设置在下方“开发者专用”中
开发者专用:终端命令和 JSON 设置
通过网页连接
Claude Code
claude mcp add --transport http --scope user usagemax https://usagemax.com/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"usagemax": {
"url": "https://usagemax.com/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"usagemax": {
"type": "http",
"url": "https://usagemax.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月14日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
public_profileRead one opt-in public UsageMax profile and aggregate statistics.
leaderboardRead the public UsageMax leaderboard (maximum 100 rows).
network_statsRead aggregate public UsageMax network statistics and render the optional inline observability view.
ask_siteAsk a bounded natural-language question about UsageMax and receive cited public resources.
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 SYMBaiEX 验证,该账户拥有此仓库
- ✓ 通过
仍在维护
代码最后更新于前天
- ✓ 通过
有许可证
使用 MIT
- ✓ 通过
端点有响应
在 921 毫秒内响应(HTTP 200)
- – 不适用
使用 OAuth 登录
无需登录
- ✓ 通过
工具描述中没有隐藏指令
已读取 4 个工具描述,未发现针对 AI 的隐藏指令
作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/symbaiex-usagemax)讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“开发者工具”中的其他服务器比较i
- 星标数多于此分类中其他 6103 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 6103 个服务器的 36% 更新
- 基础检查结果等于或优于此分类中其他 6103 个服务器的 99%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
UsageMax public observability 安全吗?
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
它还在维护吗?
GitHub 仓库最后更新于前天,最新版本(1.0.0)于2个月前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
有什么可以替代它?
同一分类中有:GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
功能相近的其他选择
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| 本项 UsageMax public observability | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 是 | 否 | 否 |
| 基础检查 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| 许可证 | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
UsageMax
Your AI work, in perspective.
A private-by-default usage ledger for people and teams building with AI.
Live app · Docs · Integrations · Pricing · How we count · Issues
UsageMax reconciles the AI usage histories already on your computers into one clear view of tokens, model mix, tracked cost, sessions, and activity. The open-source CLI performs bounded local scans and uploads aggregate snapshots to the versioned UsageMax API.
The short version: one-shot collector, private by default, public only by
choice. Prompts and completions never leave the computer.
What you get
| Surface | Purpose |
|---|---|
| Private workspace | Compare computers, providers, models, projects, and cost centers in one tenant-scoped view. |
| Public profile | Opt-in profile, leaderboard, activity, model mix, cost estimate, and streaks. |
| Collector API | Installation-bound, write-only snapshots and content-free telemetry. |
| `usagemax` CLI | A bunx-friendly scanner with archive recovery, safe diagnostics, and optional OS scheduling. |
| Agent interfaces | Bounded OpenAPI, MCP, Markdown, WebMCP, A2A, and installable skill surfaces. |
The physical HUD/screen project is intentionally separate from this repository. It can consume UsageMax telemetry, but it is not required to use the platform.
Connect a computer
1. Create a link code
Sign in at usagemax.com/account, choose Link a computer, give it a name, and copy the one-use command. The code is valid for ten minutes and can be used once.
2. Link and sync
Run the command on the computer or WSL distribution that owns the history:
bunx usagemax link UMX-XXXX-XXXX-XXXX-XXXX
Optional explicit name; the account keeps this name for the installation.
bunx usagemax link UMX-XXXX-XXXX-XXXX-XXXX --name "Work laptop"
The first link performs a full one-shot sync. Every installation receives a stable random ID, so relinking or renaming it rotates its key without creating a duplicate device.
3. Reconcile when you choose
bunx usagemax sync --dry-run --explain # inspect the bounded plan
bunx usagemax sync # upload changed usage bunx usagemax sync --full # reconcile all retained history bunx usagemax status --remote # check the saved credential safely
CLI updates and progress
The CLI checks npm's latest dist-tag at most twice per day. Run usagemax update to check the live npm release and install that exact version through Bun or npm; use --check for a read-only check. Run usagemax update sync to hand a command to the checked release without typing @latest, or set USAGEMAX_AUTO_UPDATE=1 for an explicit automatic handoff. Use --no-update-check or set USAGEMAX_DISABLE_UPDATE_CHECK=1 in offline environments. Interactive terminals show a small stderr progress line; JSON, quiet, CI, and scheduled runs remain machine-readable and quiet.
Coverage and correctness
UsageMax pins ccusage v20.0.51 and uses its 19 adapters: Amp, Antigravity, Claude Code, Cline, Codebuff, Codex, GitHub Copilot CLI, Factory Droid, Gemini CLI, Goose, Grok Build, Hermes, Kilo Code, Kimi CLI, OpenClaw, OpenCode, Pi, Qwen Code, and ZCode. Named Pi-format stores are discovered as well.
The collector recognizes supported provider overrides, bounded home locations, Claude Desktop sessions, .cc-mirror, renamed Claude/Codex backup folders, and supported Windows homes from WSL. Normal syncs inspect known locations and immediate home entries; they do not crawl the whole disk.
bunx usagemax doctor # metadata-only coverage check
bunx usagemax doctor --deep --json # retained-history audit bunx usagemax sync --archives # one-time compressed-history recovery bunx usagemax report # local ccusage report bunx usagemax status --json # version, coverage, checkpoints, and link state bunx usagemax update --json # machine-readable npm release check
Full scans can catalog retained history from 2024 onward. A readable file inventory is not proof that an aggregate parser consumed every file and day. UsageMax reports those two states separately; counter decreases and missing rows remain protected unless the parser explicitly certifies its coverage. Unknown models stay unattributed; unknown pricing stays unknown.
Cursor, Windsurf, Aider, Continue, Roo Code, hosted agents, direct provider API traffic, and enterprise billing systems do not all expose a stable local ledger. Feed those through the native or OTLP/HTTP JSON contract, or use a provider billing export when local evidence is unavailable.
Privacy and resource use
| Stays on the computer | May be uploaded |
|---|---|
| Prompts and completions | Aggregate token counters |
| Source code and file contents | Provider, model, and source names |
| Project paths and tool payloads | Dates, costs, and coverage state |
| Provider credentials and secrets | Opaque SHA-256 session identities |
The CLI is short-lived. It skips unchanged inventories, parses only the necessary date range, uses a local lock to prevent overlap, and never downloads a package per run. Optional scheduling invokes the same one-shot process and backs off after failures.
bun install -g usagemax
usagemax service install # approximately every 15 minutes usagemax service install --every 30 usagemax service status usagemax service uninstall
Scheduling is opt-in. macOS uses a user LaunchAgent, Linux/WSL uses a user systemd timer, and Windows uses Task Scheduler. Sleeping or battery-powered computers are not needlessly woken.
Credentials and safe diagnostics
UsageMax has separate credentials for website sign-in, one-use linking, and collector writes. A collector key is exactly umx_ followed by 64 lowercase hexadecimal characters. It is generated server-side, displayed once, stored locally with user-only permissions, and stored by UsageMax only as a SHA-256 hash.
For an Advanced · custom telemetry collector key, pipe the secret through stdin. Never put it in a command-line argument, URL, request body, repository, or log:
set +x
set -o pipefail printf '%s' "$USAGEMAX_COLLECTOR_TOKEN" \ | bunx usagemax token status \ --json \ | jq -r '[.httpStatus, (if .ingestAuthorized then 1 else 0 end)] | @tsv'
token status and telemetry test are included in CLI 0.3.12. If a fresh environment still has an older npm tag, run usagemax update token status or use node packages/cli/src/cli.js token status from this repository until the new package is published.
To prove the authenticated write path, send one content-free agent_state event with all token and cost values set to zero:
set +x
set -o pipefail printf '%s' "$USAGEMAX_COLLECTOR_TOKEN" \ | bunx usagemax telemetry test \ --token-stdin \ --json
This writes one observability event and does not change token or spend totals. An unbound advanced key becomes bound to this CLI installation on its first accepted write. The CLI returns a non-zero exit code if the credential cannot ingest or the API rejects the event.
The numeric projection is deliberately small:
| Result | Meaning |
|---|---|
200 1 | Recognized, active, and authorized to ingest. |
200 0 | Recognized but blocked; inspect the redacted JSON status. |
409 0 | The installation UUID does not match the key binding. |
401 0 | The format/key was not accepted; the server does not reveal which reason. |
The read-only diagnostic reports credential type, scopes, activation state, profile/name, binding state, and last accepted/rejected write. It never returns the token, its hash, or the authorized UUID. Advanced keys are active immediately; they bind on the first valid write. Linked CLI keys are bound during the link exchange.
Agent and developer surfaces
| Surface | URL |
|---|---|
| OpenAPI | openapi.json |
| Agent capability view | /?mode=agent |
| Public MCP | server-card.json |
| Documentation MCP | /docs-mcp |
| A2A card | agent-card.json |
| Skills index | agent-skills/index.json |
| MCP Registry metadata | server.json |
| Skill source and install docs | skills/ · skills.sh |
| Auth guide | /auth.md |
Public reads are bounded and unauthenticated. The public MCP servers are stateless, read-only, and do not expose private workspace data or collector credentials. Collector ingestion is a separate authenticated API boundary.
Repository map
src/ Next.js web app, public routes, docs, and UI
convex/ Convex schema, authorization, ingestion, and projections packages/cli/ Distributable usagemax package docs/ Architecture, contracts, coverage, operations, and releases skills/ Direct-installable agent skills and source notes server.json MCP Registry submission metadata for the public remote server
For the documentation map, start with docs/README.md. It separates public product and integration guidance from contributor, operator, release, and historical records.
MCP Registry and skills.sh status
The public MCP server is published in the official Registry as io.github.SYMBaiEX/usagemax@1.0.0. The server.json file is the versioned source metadata for that listing; it contai