bulk-url-checker MCP server
io.github.carlosofscience/bulk-url-checkercarlosofsciencestreamable-httpv1.0.1Scanned
Bulk HTTP status checker: up to 100,000 URLs per job, with redirect chains and response times.
5 tools: 1 can delete or cancel things and 4 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the bulk-url-checker MCP server can do
The bulk-url-checker MCP server is published by the GitHub account carlosofscience. It has 5 tools. It can delete or cancel things (1 tool: submit_urls). 4 tools only read.
2 tools bring in text other people can write (submit_urls and get_usage).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 16, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Deletes or cancels 1Claude Code: deny
submit_urlsSubmits a list of URLs to be checked and returns a job_id.Reads text others writeNo findings
Why it is in this group
- The name "submit_urls" says "submit": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Submit URLs for checking
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
Only reads 4Show 4 read-only tools
get_job_resultsFetch paginated results for a job.No findings
Why it is in this group
- The name "get_job_results" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get job results
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_job_statusGet the current status and progress of a job.No findings
Why it is in this group
- The name "get_job_status" says "get": a word for reading.
Description, as the server wrote it Get the current status and progress of a job.
Annotations the server declares
- title: Get job status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_usageReturns the number of URL checks currently available on this account.Reads text others writeNo findings
Why it is in this group
- The name "get_usage" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Returns the number of URL checks currently available on this account.
Annotations the server declares
- title: Get credit balance
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_verified_domainsLists the domains this account has proven ownership of.No findings
Why it is in this group
- The name "get_verified_domains" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get verified domains
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:03 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.bulkurlchecker.com/.well-known/oauth-protected-resource
- Authorization servers
- https://api.bulkurlchecker.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 destructive). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.bulkurlchecker.com/mcp: tools/list returned 5 tools to an anonymous client, including submit_urls (destructive)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http bulk-url-checker https://mcp.bulkurlchecker.com/mcpclaude mcp add --transport http bulk-url-checker https://mcp.bulkurlchecker.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__bulk-url-checker__get_job_status",
"mcp__bulk-url-checker__get_job_results",
"mcp__bulk-url-checker__get_verified_domains",
"mcp__bulk-url-checker__get_usage"
],
"ask": [],
"deny": [
"mcp__bulk-url-checker__submit_urls"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bulk-url-checker. Review it before you use it.
Capability tags behind 2 rules
- mcp__bulk-url-checker__submit_urls untrusted-input
- mcp__bulk-url-checker__get_usage untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.carlosofscience/bulk-url-checker/verify?hash=1f63e2397c5dc8fadbca3c10ef4d898ea25a6c47c10c0afdcbf7376308e1d667" | jq -e '.changed == false'Pinned hash 1f63e2397c5d, from Nov 16, 2026, 13:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.carlosofscience/bulk-url-checker/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.carlosofscience/bulk-url-checker)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:26 UTC.
bulk-url-checker MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the bulk-url-checker MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the bulk-url-checker MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: submit_urls.
Can the bulk-url-checker MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the bulk-url-checker MCP server have?
- 5 tools: 1 destructive, 4 read. submit_urls, get_job_status, get_job_results, get_verified_domains and get_usage.
Does the bulk-url-checker MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the bulk-url-checker MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the bulk-url-checker MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.