Bulk URL Checker
https://mcp.bulkurlchecker.com
Registry code: 8f5004d465416126
Validate up to 75,000 URLs per job (status, redirects, response times). OAuth 2.1.
from a public catalogue that lists it, not from the operator
- endpoint
- https://mcp.bulkurlchecker.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is Bulk URL Checker live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
- Is Bulk URL Checker free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does Bulk URL Checker have?
- 5 tools: get_usage, get_verified_domains, get_job_status, get_job_results, submit_urls.
- Is Bulk URL Checker safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.6%· all time 99.6%
last good check
of 5 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- topic
- developer tools testing & qa
- used for
- check status codes of many urls
- get url check results
- check remaining url checks
- takes → gives
- text → data
- tools
- 4 reads1 changes data
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_usage reads auth-required 5h ago
Returns the number of URL checks currently available on this account.
{ "type": "object", "properties": {} }arguments 4 linesget_verified_domains reads auth-required 5h ago
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.
{ "type": "object", "properties": {} }arguments 4 linesget_job_status reads auth-required 5h ago
Get the current status and progress of a job.
{ "type": "object", "required": [ "job_id" ], "properties": { "job_id": { "type": "string" } } }arguments 11 linesget_job_results reads auth-required 16h ago
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.
{ "type": "object", "required": [ "job_id" ], "properties": { "limit": { "type": "integer", "default": 100, "maximum": 1000, "minimum": 1 }, "job_id": { "type": "string" }, "offset": { "type": "integer", "default": 0, "minimum": 0 } } }arguments 22 linessubmit_urls changes data auth-required never probed
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.
{ "type": "object", "required": [ "urls" ], "properties": { "urls": { "type": "array", "items": { "type": "string" }, "description": "URLs to check. Each must include http:// or https:// scheme." } } }arguments 15 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id8f5004d465416126.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/8f5004d465416126/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/8f5004d465416126?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.