原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Bulk Url Checker

作者:carlosofscience版本 1.0.1i★ –i在云端运行
注册名称io.github.carlosofscience/bulk-url-checker

安装

概览

作者提供的说明(英文原文)

Bulk HTTP status checker: up to 100,000 URLs per job, with redirect chains and response times.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

你需要

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude:

  1. 打开 Settings → Connectors
  2. 点击 Add custom connector
  3. 粘贴下面的地址,然后点击 Add
  4. 如果要求登录,请登录作者的服务
SettingsConnectors1+ Add2https://…3
https://mcp.bulkurlchecker.com/mcp

在终端中运行这条命令

claude mcp add --transport http bulk-url-checker https://mcp.bulkurlchecker.com/mcp

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "bulk-url-checker": {
      "url": "https://mcp.bulkurlchecker.com/mcp"
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "bulk-url-checker": {
      "type": "http",
      "url": "https://mcp.bulkurlchecker.com/mcp"
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

ChatGPT 只能连接互联网上的服务器:

  1. 打开网页版 ChatGPT → Settings → Connectors (Apps)
  2. 点击 Create 或 Add(部分套餐需要先在 Advanced 中开启 Developer mode)
  3. 粘贴下面的地址,起个名字,然后保存
  4. 如果要求登录,请登录作者的服务
SettingsConnectors1+ Create2https://…3
https://mcp.bulkurlchecker.com/mcp

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上,无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月7日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。

  • submit_urls

    Submits a list of URLs to be checked and returns a job_id. Lists of up to about 200 URLs complete inline, waiting up to 60 seconds, and the results are returned directly. Larger lists return immediately with the job_id alone, and their results become available as the job progress

  • get_job_status

    Get the current status and progress of a job.

  • get_job_results

    Fetch paginated results for a job. Each result has the URL, HTTP status code (null if unreachable), response time in ms, and an error message if the check failed.

  • get_verified_domains

    Lists the domains this account has proven ownership of. Checks against a verified domain run substantially faster than checks against an unverified one. Verification is interactive, requiring a DNS TXT record or a meta tag, and is done in the web dashboard rather than through thi

  • get_usage

    Returns the number of URL checks currently available on this account.

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 carlosofscience 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • ✓ 通过

    端点有响应

    在 116 毫秒内响应(HTTP 200)

  • – 不适用

    使用 OAuth 登录

    无需登录

  • ✓ 通过

    工具描述中没有隐藏指令

    已读取 5 个工具描述,未发现针对 AI 的隐藏指令

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 18365 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 18365 个服务器的 68% 更新
  • 基础检查结果等于或优于此分类中其他 18365 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Bulk Url Checker 安全吗?

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(1.0.1)于21天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。

有什么可以替代它?

同一分类中有:Spec Driven Development, Remote Desktop Commander, Funooy Krillion Reference

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者:formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新
安装

Remote Desktop Commander

作者:desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211前天更新
安装

Funooy Krillion Reference

作者:funooy.com

Funooy trivia references in six languages, with rules and fixed scoring. No daily spoilers.

在云端运行今天更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

bulkurlchecker

Python client for the Bulk URL Checker API.

Skip the proxy-rotation, rate-limiter, soft-404 detector, and retry classifier you would otherwise spend two weeks building. Submit thousands of URLs, get status codes, redirect chains, and broken-link detection back as plain Python objects. Backed by a managed cloud service with residential proxies and per-domain throttling.

Install

pip install bulkurlchecker

5-line example

from bulkurlchecker import Client

client = Client(api_key="uck_live_...") results = client.check_urls(["https://example.com", "https://example.org"]) for r in results.results: print(r.url, r.status_code, "BROKEN" if r.is_broken else "ok")

Get an API key at https://app.bulkurlchecker.com/dashboard/api-keys. First 300 URLs are free, no card required.

What you get back

results = client.check_urls(urls)

results.status # 'completed' | 'paused' | 'failed' | 'cancelled' results.timed_out # True if the wait deadline passed (job still running) results.total_urls # how many URLs the engine accepted results.completed_urls # how many it finished checking results.duplicates_removed results.invalid_urls_rejected

for r in results.results: r.url # the original URL you submitted r.final_url # after redirects r.status_code # 200, 301, 404, 429, 500, ... r.redirect_chain # list of intermediate URLs r.is_broken # True if the engine flagged this as broken r.is_soft_404 # True if 200 OK but page content says "not found" r.response_time_ms

Convenience properties:

results.broken # list of URLResult where is_broken == True results.soft_404s # list where is_soft_404 == True

Command-line usage

Install with the [cli] extra to get the bulkurlchecker command:

pip install 'bulkurlchecker[cli]'

export BULKURLCHECKER_API_KEY=uck_live_...

One URL per line in urls.txt → CSV on stdout

bulkurlchecker check urls.txt > report.csv

Pipe from anywhere

sitemap-extractor mydomain.com | bulkurlchecker check - --output jsonl > report.jsonl

Only show broken URLs, ad-hoc input

bulkurlchecker check --urls "https://example.com,https://example.org" --only-broken

Two-step (submit, then poll & fetch later)

JOB=$(bulkurlchecker submit urls.txt) bulkurlchecker status "$JOB" bulkurlchecker results "$JOB" --output csv > report.csv

Output formats: csv (default), json, jsonl. Run bulkurlchecker check --help for the full flag list.

Larger jobs: submit and poll

check_urls() blocks for up to 15 minutes server-side. For lists where the wait would time out, use the two-step pattern:

job = client.submit(my_500k_urls)

print(f"Submitted {job.job_id}, {job.total_urls} URLs queued")

Poll explicitly, or use the convenience method

done = client.wait_until_done(job.job_id, timeout=3600)

Stream results in pages

for batch in client.iter_results(job.job_id, page_size=1000): for r in batch: if r.is_broken: print(r.url, r.status_code)

Safe retries with idempotency_key

Pass an idempotency key on submit() or check_urls() to make retries safe under network failures. The server caches the response for 24 hours; a retry with the same key + same body returns the original result without creating a duplicate job.

import uuid

key = str(uuid.uuid4()) # generate once per logical request

First call: creates a new job.

job = client.submit(urls, idempotency_key=key)

Network blip, no clean response received? Just retry with the same

key -- you'll get the SAME job summary back, no duplicate submission.

same_job = client.submit(urls, idempotency_key=key)

job.job_id == same_job.job_id

Same idempotency_key + different urls returns 409 Conflict (raised as ValidationError) so client bugs that reuse a key against a new payload are caught loudly instead of silently mapping to the wrong cached response.

Receiving webhooks

When a job finishes, we POST to your registered endpoint with a signed payload. Verify the signature before trusting the body — anyone who knows your endpoint URL can otherwise send fake events.

from flask import Flask, request

from bulkurlchecker import verify_signature, InvalidSignatureError

SECRET = os.environ["MY_WEBHOOK_SECRET"] # the signing_secret we showed once

app = Flask(name)

@app.route("/webhook/bulkurlchecker", methods=["POST"]) def webhook(): try: verify_signature( request.get_data(), # RAW bytes — not request.get_json() request.headers.get("Bulkurlchecker-Signature", ""), SECRET, ) except InvalidSignatureError: return "", 401 event = request.get_json() if event["type"] == "job.completed": job_id = event"data"

... fetch results, update your DB, ping Slack, etc ...

return "", 200

Register endpoints + get secrets at https://app.bulkurlchecker.com/dashboard/webhooks (or via POST /api/v2/webhooks/endpoints).

verify_signature() enforces a 5-minute timestamp tolerance by default to defeat replays. Tune via tolerance_seconds=.

Error handling

All errors derive from BulkURLCheckerError. Catch specific subclasses when you want to branch on the failure mode:

from bulkurlchecker import (

Client, BulkURLCheckerError, AuthenticationError, RateLimitError, QuotaError, ValidationError, )

try: results = client.check_urls(urls) except QuotaError as e: print(f"Out of credits. Top up at https://app.bulkurlchecker.com/billing") except RateLimitError as e: print(f"Rate limited. Retry after {e.retry_after}s.") except AuthenticationError: print("API key rejected — check it's not revoked.") except ValidationError as e: print(f"Bad request: {e}") # bad URLs, too many URLs, etc. except BulkURLCheckerError as e: print(f"Other error: {e} (request_id={e.request_id})")

Every error carries status_code, code (server's machine-readable string), request_id (for support), and details (when the server provides them).

Why use this instead of writing your own checker with httpx + asyncio?

Honest answer: for ≤500 URLs you don't need this. The standard requests/httpx toolchain handles it fine.

The wall hits at scale:

ProblemRolling your ownThis SDK
Concurrencyasyncio + careful semaphoresdone
Proxy rotation across residential IPs$90+/mo Webshare / Bright Data subscription + custom codedone
Per-domain rate limiting (so you don't hammer one host)wire it yourselfdone
Distinguishing real 403 from "you got blocked" 403guess and checkdone
Detecting soft 404s (200 OK + "not found" body)regex / heuristic per templatedone
Retry classification (transient vs permanent)tune for weeksdone
Long-running job state (resume after crash)Redis + queue + worker infradone
Engineer time, weeks 1-4$$$nothing, ship today

If you've already lost a weekend to httpx + proxy rotation, you know what we're talking about.

Pricing

  • First month on us: 15,000 URL checks on the Starter plan, no credit card. The first time an API or SDK integration runs successfully, the trial grows to a month of Pro: 50,000 URL checks, once per account.
  • After that: 300 URL checks a month are included on every account.
  • Starter: $9/month or $90/year, 15,000 URLs/month
  • Pro: $29/month or $290/year, 50,000 URLs/month
  • Agency: $99/month or $990/year, 200,000 URLs/month

Scheduled checks, with email, Slack and webhook alerts, are included on every plan. One-time credit packs start at $5 for 3,000 checks, and pack credits roll over. Current prices: https://bulkurlchecker.com/#pricing

Links

Stability

The SDK follows semver. While we're at 0.x, breaking changes can land in minor releases (we'll always note them in CHANGELOG.md). Once we hit 1.0 you can pin major versions safely.

License

MIT. See LICENSE.

问 PopNx