io.github.iqingyoung/429-throttle-mcp
NPM · 429-THROTTLE-MCP · SCANNED SEP 22
带速率限制的 MCP HTTP 代理：滑动窗口+令牌桶控速，长程任务不再 429
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
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 15 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 532 tokens (~106/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
How do I install the io.github.iqingyoung/429-throttle-mcp server?
io.github.iqingyoung/429-throttle-mcp runs locally as an npm package, launched with npx -y 429-throttle-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · 429-throttle-mcp
claude mcp add iqingyoung-429-throttle-mcp -- npx -y 429-throttle-mcp
{
"mcpServers": {
"iqingyoung-429-throttle-mcp": {
"command": "npx",
"args": [
"-y",
"429-throttle-mcp"
]
}
}
} {
"servers": {
"iqingyoung-429-throttle-mcp": {
"command": "npx",
"args": [
"-y",
"429-throttle-mcp"
]
}
}
} codex mcp add iqingyoung-429-throttle-mcp -- npx -y 429-throttle-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"iqingyoung-429-throttle-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"429-throttle-mcp"
],
"enabled": true
}
}
} openclaw mcp add iqingyoung-429-throttle-mcp --command npx --arg -y --arg 429-throttle-mcp
mcp_servers:
iqingyoung-429-throttle-mcp:
command: "npx"
args: ["-y", "429-throttle-mcp"] {
"McpServers": {
"iqingyoung-429-throttle-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"429-throttle-mcp"
]
}
}
} assistant mcp add iqingyoung-429-throttle-mcp -t stdio -c npx -a -y 429-throttle-mcp
{
"mcpServers": {
"iqingyoung-429-throttle-mcp": {
"command": "npx",
"args": [
"-y",
"429-throttle-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 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.
- 12 Sept 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.
- 10 Sept 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.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 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.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Sept 2026 · Analysed npm/429-throttle-mcp@1.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
begin_task ~78
开始一个限流观测任务区间，返回 taskId。长任务开始前调用，结束后用 end_task 取复盘报告（用时/调用次数/原定用时/第几轮并发会超时）。
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | 任务名（可选，便于辨识） |
No output schema declared.
No examples provided.
call_api ~187
通过限流代理发送 HTTP 请求。所有外部 API 调用建议经此工具。 参数：url（必填）/ method（可选，默认 GET）/ body（可选，JSON 字符串）/ headers（可选，JSON 字符串）。 返回：API 响应内容 + 速率限制用量快照。被限流时返回 RATE_LIMIT_EXCEEDED 及建议等待秒数。 仅允许 http/https。请求 30 秒超时，响应最多返回前 10000 字符。
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | 请求体，JSON 字符串（POST/PUT 时使用） |
| headers | string | – | 自定义请求头，JSON 字符串 |
| method | string | – | HTTP 方法，如 GET / POST / PUT |
| url | string | yes | 目标 API 的完整 URL |
No output schema declared.
No examples provided.
end_task ~95
结束 begin_task 开启的区间，返回本次任务复盘：实际用时、调用次数、被限流次数、原定串行用时、以及按给定并发度第几轮会触顶。
| Name | Type | Req | Description |
|---|---|---|---|
| concurrency | number | – | 假设每轮并发调用数，默认 1（串行） |
| taskId | string | yes | begin_task 返回的 taskId |
No output schema declared.
No examples provided.
get_rate_limit_status ~34
查询当前速率限制使用情况。返回已用/剩余调用次数和 Token 数、建议与统计。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
set_rate_limit ~138
动态调整速率限制参数（实时生效无需重启）。callsPerMinute / tokensPerMinute 可选。 注意：非正数会被拒绝；callsPerMinute > 120 或 tokensPerMinute > 2000000 属于超大值， 可能触发上游平台真实限流，首次调用会返回 needsConfirmation，需带 confirm=true 再次调用确认。
| Name | Type | Req | Description |
|---|---|---|---|
| callsPerMinute | number | – | 每分钟最大调用次数 |
| confirm | boolean | – | 设置超大值时的二次确认标记 |
| tokensPerMinute | number | – | 每分钟最大 Token 数 |
No output schema declared.
No examples provided.
What is the io.github.iqingyoung/429-throttle-mcp server?
io.github.iqingyoung/429-throttle-mcp is listed in the public MCP registry as io.github.iqingyoung/429-throttle-mcp. 带速率限制的 MCP HTTP 代理：滑动窗口+令牌桶控速，长程任务不再 429. This page covers its npm package (429-throttle-mcp).
Is the io.github.iqingyoung/429-throttle-mcp server safe to use?
io.github.iqingyoung/429-throttle-mcp scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. 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 io.github.iqingyoung/429-throttle-mcp server expose?
io.github.iqingyoung/429-throttle-mcp exposes 5 tools: call_api, get_rate_limit_status, set_rate_limit, begin_task, end_task. Their descriptions and schemas cost roughly 532 tokens of context every time the server is loaded.
Is the io.github.iqingyoung/429-throttle-mcp server still maintained?
io.github.iqingyoung/429-throttle-mcp is still listed as active in the MCP registry. We last reached this channel on 22 September 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 io.github.iqingyoung/429-throttle-mcp server under?
io.github.iqingyoung/429-throttle-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.