bulk-url-checker MCP server
Commit 12 Okt 2026Memungkinkan AI client untuk melakukan pengecekan status HTTP skala besar, mendeteksi broken link, dan menganalisis rantai redirect menggunakan managed residential proxies.
Juga dikenal sebagai carlosofscience/bulkurlchecker-python, bulkurlchecker-python
- Stars
- 0
- Tools
- —
- Unduhan, 30 hari
- —
- Versi terbaru
- 1.0.1
- Commit terakhir
- 12 Okt 2026
- Lisensi
- MIT
Apa itu bulk-url-checker MCP?
bulk-url-checker adalah MCP server. Memungkinkan AI client untuk melakukan pengecekan status HTTP skala besar, mendeteksi broken link, dan menganalisis rantai redirect menggunakan managed residential proxies.
Ringkasan dibuat dari README proyek
Tentang bulk-url-checker MCP server
Developer menggunakan tool ini untuk memindai ribuan link guna mencari broken pages atau redirect loops. Tool ini menyediakan cara untuk melakukan pengecekan status HTTP skala besar dan mendeteksi error soft 404, di mana sebuah halaman mengembalikan kode sukses tetapi menampilkan pesan tidak ditemukan. Layanan ini mengelola tugas kompleks seperti rotasi residential proxy, per-domain throttling, dan klasifikasi retry sehingga Anda tidak perlu membangunnya secara manual.
User terhubung melalui Python client menggunakan API key untuk melakukan submit daftar URL. Untuk batch yang lebih kecil, method check_urls memberikan hasil instan, sementara job yang lebih besar dapat di-submit dan dipantau menggunakan job ID untuk menangani tugas yang berjalan lama. Sistem ini mendukung berbagai format output termasuk CSV, JSON, dan JSONL, bahkan dapat mengirim alert otomatis melalui webhook, email, atau Slack. Tool ini dirancang untuk skala besar, menawarkan fitur seperti idempotency keys untuk mencegah duplikasi submission saat terjadi kegagalan jaringan.
Apa yang bisa Anda lakukan dengannya
- 1Mendeteksi broken link pada sitemap besarAI client dapat memproses sitemap untuk mengidentifikasi setiap URL yang saat ini rusak atau mengembalikan kode error.
- 2Mengidentifikasi error soft 404 yang menyesatkanDeveloper dapat menemukan halaman yang secara tidak sengaja mengembalikan status 200 OK meskipun kontennya menunjukkan bahwa halaman tersebut hilang.
- 3Menganalisis rantai redirect yang kompleksAnda dapat melacak jalur sebuah URL melalui beberapa hop perantara untuk melihat destinasi akhirnya.
- 4Mengotomatisasi audit link skala besarUser dapat mengalirkan output dari sitemap extractor secara langsung ke checker untuk menghasilkan laporan CSV dari seluruh link situs.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal bulk-url-checker MCP
Format diverifikasi 10 Nov 2026Instal bulk-url-checker MCP di Claude Code
$ claude mcp add --transport http bulkurlchecker-python https://mcp.bulkurlchecker.com/mcpInstal bulk-url-checker MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"bulkurlchecker-python": {
"url": "https://mcp.bulkurlchecker.com/mcp"
}
}
}Instal bulk-url-checker MCP di VS Code
.vscode/mcp.json
{
"servers": {
"bulkurlchecker-python": {
"type": "http",
"url": "https://mcp.bulkurlchecker.com/mcp"
}
}
}Instal bulk-url-checker MCP di Codex
~/.codex/config.toml
[mcp_servers.bulkurlchecker-python] url = "https://mcp.bulkurlchecker.com/mcp"
Instal bulk-url-checker MCP di Gemini CLI
~/.gemini/settings.json
{
"mcpServers": {
"bulkurlchecker-python": {
"httpUrl": "https://mcp.bulkurlchecker.com/mcp"
}
}
}Konfigurasi
BULKURLCHECKER_API_KEY
| Nama | Deskripsi | Tipe |
|---|---|---|
| BULKURLCHECKER_API_KEY | — |
README
Lihat di GitHubbulkurlchecker
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"]["job_id"]
# ... 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:
| Problem | Rolling your own | This SDK |
|---|---|---|
| Concurrency | asyncio + careful semaphores |
done |
| Proxy rotation across residential IPs | $90+/mo Webshare / Bright Data subscription + custom code | done |
| Per-domain rate limiting (so you don't hammer one host) | wire it yourself | done |
| Distinguishing real 403 from "you got blocked" 403 | guess and check | done |
| Detecting soft 404s (200 OK + "not found" body) | regex / heuristic per template | done |
| Retry classification (transient vs permanent) | tune for weeks | done |
| Long-running job state (resume after crash) | Redis + queue + worker infra | done |
| 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.
Pertanyaan tentang bulk-url-checker MCP
Bagaimana cara menambahkan bulk-url-checker MCP ke Claude Code?
Jalankan claude mcp add --transport http bulkurlchecker-python https://mcp.bulkurlchecker.com/mcp di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan bulk-url-checker MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Apakah tersedia tier gratis?
Ya, 300 URL pertama tersedia gratis dan Anda tidak memerlukan kartu kredit untuk memulai.
Bagaimana cara mencegah duplikasi job jika terjadi error jaringan saat submission?
Anda dapat menyertakan idempotency key pada method submit atau check_urls untuk memastikan retry akan mengembalikan hasil asli tanpa membuat duplikasi.
Apakah layanan ini bisa mendeteksi jika sebuah halaman adalah 'soft 404'?
Ya, engine ini dapat menandai halaman yang mengembalikan status 200 OK tetapi berisi konten 'not found'.