bulk-url-checker
Server Details
Validate up to 75,000 URLs per job (status, redirects, response times). OAuth 2.1.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.2/5 across 4 of 4 tools scored. Lowest: 3.5/5.
Each tool has a clearly distinct purpose: submitting URLs, checking job status, fetching results, and retrieving credit balance. No overlap or ambiguity.
All tools follow a consistent verb_noun pattern in snake_case (e.g., get_job_status, submit_urls), making them predictable and easy to understand.
With 4 tools, the server is well-scoped for its purpose. Each tool serves a necessary function without redundancy or unnecessary complexity.
The tool set covers the full lifecycle: submission, status polling, result retrieval, and usage tracking. No obvious gaps for a bulk URL checker.
Available Tools
4 toolsget_job_resultsRead-onlyIdempotentInspect
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 | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| job_id | Yes | ||
| offset | No |
get_job_statusRead-onlyIdempotentInspect
Get the current status and progress of a job.
| Name | Required | Description | Default |
|---|---|---|---|
| job_id | Yes |
get_usageRead-onlyIdempotentInspect
Return the current credit balance for this API key.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
submit_urlsDestructiveInspect
Submit a list of URLs to be checked. Returns a job_id that can be polled via get_job_status or fetched via get_job_results. For up to ~200 URLs this tool waits for completion (up to 60 seconds) and returns the results directly; for larger jobs it returns early with job_id and the agent should poll.
| Name | Required | Description | Default |
|---|---|---|---|
| urls | Yes | URLs to check. Each must include http:// or https:// scheme. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!