MCP server de bulk-url-checker
Commit 12 oct 2026Permite que un cliente de IA realice comprobaciones de estado HTTP a gran escala, detecte enlaces rotos y analice cadenas de redirección utilizando proxies residenciales gestionados.
También conocido como carlosofscience/bulkurlchecker-python, bulkurlchecker-python
- Stars
- 0
- Herramientas
- —
- Descargas, 30 días
- —
- Última versión
- 1.0.1
- Último commit
- 12 oct 2026
- Licencia
- MIT
¿Qué es bulk-url-checker MCP?
bulk-url-checker es un MCP server. Permite que un cliente de IA realice comprobaciones de estado HTTP a gran escala, detecte enlaces rotos y analice cadenas de redirección utilizando proxies residenciales gestionados.
Resumen generado a partir del README del proyecto
Acerca del MCP server de bulk-url-checker
Los desarrolladores utilizan esta herramienta para escanear miles de enlaces en busca de páginas rotas o bucles de redirección. Proporciona una forma de realizar comprobaciones de estado HTTP a gran escala y detectar errores de soft 404, donde una página devuelve un código de éxito pero muestra un mensaje de no encontrado. El servicio gestiona tareas complejas como la rotación de proxies residenciales, la limitación de velocidad por dominio y la clasificación de reintentos para que no tengas que implementarlas manualmente.
Los usuarios se conectan mediante un cliente de Python usando una API key para enviar listas de URLs. Para lotes pequeños, el método check_urls ofrece resultados inmediatos, mientras que los trabajos más grandes pueden enviarse y consultarse mediante un job ID para gestionar tareas de larga duración. El sistema admite varios formatos de salida, incluidos CSV, JSON y JSONL, e incluso puede enviar alertas automatizadas a través de webhooks, email o Slack. Está diseñado para escalar, ofreciendo funciones como claves de idempotencia para evitar envíos duplicados durante fallos de red.
Qué puedes hacer con él
- 1Detección de enlaces rotos en sitemaps extensosUn cliente de IA puede procesar un sitemap para identificar cada URL que esté rota actualmente o que devuelva un código de error.
- 2Identificación de errores engañosos de soft 404Los desarrolladores pueden encontrar páginas que devuelven incorrectamente un estado 200 OK a pesar de que el contenido indica que la página no existe.
- 3Análisis de cadenas de redirección complejasPuedes rastrear la ruta de una URL a través de múltiples saltos intermedios para ver el destino final.
- 4Automatización de auditorías de enlaces a gran escalaLos usuarios pueden pasar la salida de un extractor de sitemaps directamente al comprobador para generar un informe CSV de todos los enlaces del sitio.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar bulk-url-checker MCP
Formatos verificados el 10 nov 2026Instalar bulk-url-checker MCP en Claude Code
$ claude mcp add --transport http bulkurlchecker-python https://mcp.bulkurlchecker.com/mcpInstalar bulk-url-checker MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"bulkurlchecker-python": {
"url": "https://mcp.bulkurlchecker.com/mcp"
}
}
}Instalar bulk-url-checker MCP en VS Code
.vscode/mcp.json
{
"servers": {
"bulkurlchecker-python": {
"type": "http",
"url": "https://mcp.bulkurlchecker.com/mcp"
}
}
}Instalar bulk-url-checker MCP en Codex
~/.codex/config.toml
[mcp_servers.bulkurlchecker-python] url = "https://mcp.bulkurlchecker.com/mcp"
Instalar bulk-url-checker MCP en Gemini CLI
~/.gemini/settings.json
{
"mcpServers": {
"bulkurlchecker-python": {
"httpUrl": "https://mcp.bulkurlchecker.com/mcp"
}
}
}Configuración
BULKURLCHECKER_API_KEY
| Nombre | Descripción | Tipo |
|---|---|---|
| BULKURLCHECKER_API_KEY | — |
README
Ver en 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.
Preguntas sobre bulk-url-checker MCP
¿Cómo agrego bulk-url-checker MCP a Claude Code?
Ejecuta claude mcp add --transport http bulkurlchecker-python https://mcp.bulkurlchecker.com/mcp en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego bulk-url-checker MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Hay un nivel gratuito disponible?
Sí, las primeras 300 URLs son gratuitas y no se requiere tarjeta de crédito para empezar.
¿Cómo puedo evitar trabajos duplicados si ocurre un error de red durante el envío?
Puedes pasar una clave de idempotencia a los métodos submit o check_urls para asegurar que los reintentos devuelvan el resultado original sin crear un duplicado.
¿Puede el servicio detectar si una página es un 'soft 404'?
Sí, el motor puede marcar páginas que devuelven un estado 200 OK pero contienen contenido de 'no encontrado'.