quota-mcp
OCI · GHCR.IO/LIMITCOOL/QUOTA-MCP:0.3.2
Usage & quota tracker for AI subscription accounts (StepFun, Command Code)
Available components
Last scanned (7 hours ago)
Scores higher than 79% of OCI servers
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 26 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 488 tokens (~81/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 47. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +6
- Stability: unverified → 0.40 ▲ functional
- 28 Sept 26 +32
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Sept 26 9
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Analysed oci/ghcr.io/limitcool/quota-mcp:0.3.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
quota_check_alerts ~109
当前触发中的告警：剩余额度低于阈值、订阅/账期即将到期、console 会话掉线需重新登录、API key 失效、节流窗口超限。无告警时返回空列表。同一条告警不重复返回，恢复后会自动消失。
| Name | Type | Req | Description |
|---|---|---|---|
| history | null|integer | – | 附带最近多少条历史（含已恢复），0 = 只要触发中的 |
No output schema declared.
No examples provided.
quota_list_accounts ~88
列出全部已登记的 AI 订阅账户（StepFun / Command Code），返回掩码视图：套餐、订阅到期、剩余额度（console 面的真实数据）、会话/密钥状态。provider 可传 stepfun / commandcode / all。
| Name | Type | Req | Description |
|---|---|---|---|
| provider | null|string | – | stepfun|commandcode|all，默认 all |
No output schema declared.
No examples provided.
quota_probe_account ~103
实时探测一个账户：打上游接口拉取最新用量/额度/会话状态。StepFun 返回订阅、5 小时/周/订阅额度、名下 access key；Command Code 返回 5 小时/周/月度窗口与账期统计。
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | stepfun 或 commandcode |
| service | string | yes | 账户槽位名，如 ai-412848664332275700 |
No output schema declared.
No examples provided.
quota_probe_all ~67
串行探测全部账户并刷新缓存。账户多或有网络黑洞时会比较慢（每个账户数秒）。只看缓存数据用 quota_list_accounts 就够。
| Name | Type | Req | Description |
|---|---|---|---|
| provider | null|string | – | stepfun|commandcode|all，默认 all |
No output schema declared.
No examples provided.
quota_report ~65
定时播报用的汇总 payload：两个平台全部账户的关键数字（套餐、到期、剩余额度、会话状态、窗口用量、请求统计）+ 当前告警。适合 hermes cron 拉取后整理成消息投递。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
quota_status ~56
汇总：各 provider 账户数、服务中/被限流/key 失效/需重新登录的数量，以及每个账户的一句话状态。适合被问「我的额度还剩多少」时直接回答。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the quota-mcp server?
quota-mcp runs locally as a container image, launched with docker run --rm -i -e QUOTA_MCP_MASTER_KEY -e QUOTA_MCP_DB ghcr.io/limitcool/quota-mcp:0.3.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/limitcool/quota-mcp:0.3.2
claude mcp add limitcool-quota-mcp -- docker run --rm -i -e QUOTA_MCP_MASTER_KEY -e QUOTA_MCP_DB ghcr.io/limitcool/quota-mcp:0.3.2
This image reads QUOTA_MCP_MASTER_KEY and QUOTA_MCP_DB. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the quota-mcp server?
quota-mcp is listed in the public MCP registry as io.github.limitcool/quota-mcp. Usage & quota tracker for AI subscription accounts (StepFun, Command Code). This page covers its container image (ghcr.io/limitcool/quota-mcp:0.3.2).
Is the quota-mcp server safe to use?
quota-mcp scores 51 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the quota-mcp server expose?
quota-mcp exposes 6 tools: quota_check_alerts, quota_list_accounts, quota_probe_account, quota_probe_all, quota_report, quota_status. Their descriptions and schemas cost roughly 488 tokens of context every time the server is loaded.
Is the quota-mcp server still maintained?
quota-mcp is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the quota-mcp server under?
quota-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.