Our MCP server runs at https://mcp.bulkurlchecker.com/mcp and works as a connector in any client that speaks the Model Context Protocol. OAuth 2.1 with dynamic client registration. No API key paste, no environment variables.
Pick the host you use. Each install takes about 30 seconds and walks you through OAuth on first tool call.
https://mcp.bulkurlchecker.com/mcphttps://mcp.bulkurlchecker.com/mcpclaude mcp add --transport http url-checker https://mcp.bulkurlchecker.com/mcphttps://mcp.bulkurlchecker.com/mcp with transport streamable-httphttps://mcp.bulkurlchecker.com/mcp/.well-known/oauth-authorization-server handles dynamic client registration (RFC 7591) automaticallytools=[{"type":"mcp"}], LangChain MCP adapter, and any custom clientFour tools, fully annotated per the MCP spec (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) so the host can show you accurate "this will modify state" warnings.
Submit a list of URLs to be checked. Returns a job_id. For ~200 URLs it waits inline (up to 60s) and returns the results directly; larger jobs return early so the agent can poll. Costs 1 credit per URL.
Get the current status (pending / processing / paused / completed / failed / cancelled) and progress (URLs checked, URLs remaining) for a job.
Fetch paginated results for a job. Each result has the URL, HTTP status code, response time in ms, redirect chain, and an error reason if the check failed.
Return the current credit balance for the authenticated API key. Useful before submitting a large job.
We use OAuth 2.1 with PKCE and dynamic client registration (RFC 7591). What that means in practice:
The host (Claude.ai, ChatGPT, etc.) registers itself with our server the first time you connect — you don't have to manage client IDs or secrets. When you grant access, you sign in with your Bulk URL Checker account, click Allow, and the host receives a token bound to your account. You can revoke that token anytime from your dashboard.
Note for security teams: the host never sees your password — it goes directly to our auth provider (Clerk). Tool calls arrive with a bearer token; we resolve that to your user, charge against your credit balance, and return only your own data.
Once installed, just ask. Here are a few patterns that work well:
Check whether these 50 backlinks are still live and tell me which ones redirect or 404.
Best for SEO audits. The agent will call submit_urls, wait for completion, then summarize the failures with status codes.
I just had Claude write a research summary with 30 citations. Verify each URL works.
AI content QA before publishing. Catches hallucinated citations and rotted links in one pass.
Submit these 5,000 URLs from my docs site. Return when 80% are done.
Larger batches get a job_id and the agent polls get_job_status until threshold met, then fetches paginated results.
We use analytics cookies to improve your experience. Opt out anytime in Cookie Settings. Privacy Policy