429-throttle-mcp

MCPcommunity
v1.2.0io.github.iqingyoungUnknownUpdated 1mo agonpmGitHub

带速率限制的 MCP HTTP 代理：滑动窗口+令牌桶控速，长程任务不再 429

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Package
Authorio.github.iqingyoung
LicenseUnknown
Version1.2.0
Sourcenpm+mcp-registry
npm429-throttle-mcp
GitHubiqingyoung/429-throttle-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface5 tools · none privileged
Security scan✓ Cleanv1.3.0 · 28d agoHow well does this scan work?
EvalsNone
IndexedAug 26, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

5 tools · none privileged
Statically extracted from the published packagev1.3.0 · 28d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

call_api通过限流代理发送 HTTP 请求。所有外部 API 调用建议经此工具。 参数：url（必填）/ method（可选，默认 GET）/ body（可选，JSON 字符串或对象）/ headers（可选，JSON 字符串或对象）。 返回：API 响应内容 + 速率限制用量快照。被限流时返回 RATE_LIMIT_EXCEEDED 及建议等待秒数； 单次请求超过每分钟 token 总额时返回 REQUEST_EXCEEDS_WINDOW（等待无效，需减小请求体）。 仅允许 http/https。请求 30 秒超时，最多跟随 5 次重定向（跨域时剥离敏感头），响应最多返回 200KB 并以 trun…

通过限流代理发送 HTTP 请求。所有外部 API 调用建议经此工具。 参数：url（必填）/ method（可选，默认 GET）/ body（可选，JSON 字符串或对象）/ headers（可选，JSON 字符串或对象）。 返回：API 响应内容 + 速率限制用量快照。被限流时返回 RATE_LIMIT_EXCEEDED 及建议等待秒数； 单次请求超过每分钟 token 总额时返回 REQUEST_EXCEEDS_WINDOW（等待无效，需减小请求体）。 仅允许 http/https。请求 30 秒超时，最多跟随 5 次重定向（跨域时剥离敏感头），响应最多返回 200KB 并以 trun…

No input schema was published for this tool.

get_rate_limit_status查询当前速率限制使用情况。返回已用/剩余调用次数和 Token 数、建议与统计。

查询当前速率限制使用情况。返回已用/剩余调用次数和 Token 数、建议与统计。

No input schema was published for this tool.

set_rate_limitNo description published

This tool published no description. Forge does not invent one.

begin_task开始一个限流观测任务区间，返回 taskId。长任务开始前调用，结束后用 end_task 取复盘报告（用时/调用次数/原定用时/第几轮并发会超时）。

开始一个限流观测任务区间，返回 taskId。长任务开始前调用，结束后用 end_task 取复盘报告（用时/调用次数/原定用时/第几轮并发会超时）。

No input schema was published for this tool.

end_task结束 begin_task 开启的区间，返回本次任务复盘：实际用时、调用次数、被限流次数、原定串行用时、以及按给定并发度第几轮会触顶。

结束 begin_task 开启的区间，返回本次任务复盘：实际用时、调用次数、被限流次数、原定串行用时、以及按给定并发度第几轮会触顶。

No input schema was published for this tool.

4 of 5 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

带速率限制的 MCP HTTP 代理：滑动窗口+令牌桶控速，长程任务不再 429

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

5 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-15 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.