io.github.carlosofscience/bulk-url-checker
REMOTE · MCP.BULKURLCHECKER.COM · SCANNED SEP 20
Validate up to 75,000 URLs per job (status, redirects, response times). OAuth 2.1.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 264 tokens (~52/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 20% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.carlosofscience/bulk-url-checker MCP server?
io.github.carlosofscience/bulk-url-checker is a hosted endpoint at https://mcp.bulkurlchecker.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.bulkurlchecker.com
claude mcp add --transport http carlosofscience-bulk-url-checker 'https://mcp.bulkurlchecker.com/mcp'
{
"mcpServers": {
"carlosofscience-bulk-url-checker": {
"url": "https://mcp.bulkurlchecker.com/mcp"
}
}
} {
"servers": {
"carlosofscience-bulk-url-checker": {
"type": "http",
"url": "https://mcp.bulkurlchecker.com/mcp"
}
}
} [mcp_servers.carlosofscience-bulk-url-checker] url = "https://mcp.bulkurlchecker.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"carlosofscience-bulk-url-checker": {
"type": "remote",
"url": "https://mcp.bulkurlchecker.com/mcp",
"enabled": true
}
}
} openclaw mcp add carlosofscience-bulk-url-checker --url 'https://mcp.bulkurlchecker.com/mcp' --transport streamable-http
mcp_servers:
carlosofscience-bulk-url-checker:
url: "https://mcp.bulkurlchecker.com/mcp" {
"McpServers": {
"carlosofscience-bulk-url-checker": {
"Transport": "http",
"Url": "https://mcp.bulkurlchecker.com/mcp"
}
}
} assistant mcp add carlosofscience-bulk-url-checker -t streamable-http -u 'https://mcp.bulkurlchecker.com/mcp'
{
"mcpServers": {
"carlosofscience-bulk-url-checker": {
"type": "http",
"url": "https://mcp.bulkurlchecker.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 0
- The server changed its declared name: url-checker → Bulk URL Checker security
- Tool “get_usage” rewrote its description, which is the text the model reads security
- Tool “get_verified_domains” rewrote its description, which is the text the model reads security
- Tool “submit_urls” rewrote its description, which is the text the model reads security
- Schema quality: 60 → 52 ▲ functional
- Schema quality: good → excellent functional
- Server version: 0.1.0 → 1.0.0 functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Aug 26 89
- Schema quality: 52 → 60 ▼ functional
- New tool “get_verified_domains” functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.bulkurlchecker.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.bulkurlchecker.com | CN=YE2,O=Let's Encrypt,C=US | 16 Aug 2026 | 14 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5964017fde7b52ca01cc5d7f2c7274987bb |
| SANs: mcp.bulkurlchecker.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.bulkurlchecker.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| bulkurlchecker.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="url-checker", resource_metadata="https://mcp.bulkurlchecker.com/.well-known/oauth-protected-resource"
Bearer realm="url-checker", resource_metadata="https://mcp.bulkurlchecker.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Document | https://mcp.bulkurlchecker.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.bulkurlchecker.com/mcp |
| Authorisation server | https://api.bulkurlchecker.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.bulkurlchecker.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.bulkurlchecker.com/mcp | HTTPS enforced | 308 | https://mcp.bulkurlchecker.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_job_results ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
get_job_status ~27
Get the current status and progress of a job.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
No output schema declared.
No examples provided.
get_usage ~20
Returns the number of URL checks currently available on this account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_verified_domains ~62
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 this API.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
submit_urls ~88
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 progresses.
| Name | Type | Req | Description |
|---|---|---|---|
| urls | array | yes | URLs to check. Each must include http:// or https:// scheme. |
No output schema declared.
No examples provided.
What is the io.github.carlosofscience/bulk-url-checker MCP server?
io.github.carlosofscience/bulk-url-checker is an MCP server listed in the public MCP registry as io.github.carlosofscience/bulk-url-checker. Validate up to 75,000 URLs per job (status, redirects, response times). OAuth 2.1. This page covers its hosted endpoint (https://mcp.bulkurlchecker.com/mcp).
Is the io.github.carlosofscience/bulk-url-checker MCP server safe to use?
io.github.carlosofscience/bulk-url-checker scores 91 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.carlosofscience/bulk-url-checker MCP server expose?
io.github.carlosofscience/bulk-url-checker exposes 5 tools: submit_urls, get_job_status, get_job_results, get_verified_domains, get_usage. Their descriptions and schemas cost roughly 264 tokens of context every time the server is loaded.
Does the io.github.carlosofscience/bulk-url-checker MCP server require authentication?
Yes. io.github.carlosofscience/bulk-url-checker asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.carlosofscience/bulk-url-checker MCP server still maintained?
io.github.carlosofscience/bulk-url-checker is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.