Skip to main content
Glama

Server Details

Downdetector for AI agents: stop paying for retries that can't succeed. Check once, then report.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Server Listing
NotWorking
ChatGPT
–
Claude
–

TDQS

A4.4/5.0

Scored across 2 tools

Disambiguation5/5

check_status and report have clearly distinct purposes: one diagnoses access issues by looking up a service, the other submits a failure report. The descriptions explicitly guide the agent on when to use each, with no overlapping functionality.

Naming Consistency4/5

Both names use lowercase snake_case, which is consistent. However, check_status follows a verb_noun pattern while report is a bare verb, a minor deviation that slightly breaks the pattern.

Tool Count4/5

Two tools are on the low side but fit the narrow purpose of checking status and reporting failures. Each tool clearly earns its place, and no unnecessary tools are present.

Completeness5/5

The surface covers both key operations for the domain: diagnosing access issues (check_status) and reporting failures (report). check_status handles listed and unlisted targets and provides historical context, leaving no obvious gaps.

Available Tools

2 tools
check_statusIs it down for everyone?A
Read-only
Inspect

Is it down or blocking agents for everyone, or just you? Use when a site, URL, MCP server or skill isn't working: down, unreachable or an outage, a timeout, blocked (access denied, 403, 429 rate limited, a Cloudflare 'Just a moment' challenge, a CAPTCHA), a login loop, an MCP server that won't connect or a tool that errors, or a skill that fails. Look up a service by the URL you used, an access-path id (clawhub:/, skills.sh://, an MCP Registry name like io.github./) or a service name. Returns a one-sentence summary, the service, every listed access path with a description and failure reports from the last hour (and the last 24 hours and 7 days as context), the what_failed values and how to report. Unlisted targets return their own counts and status, with listed: false.

Inputs: target (required), type. Returns: object

reportReport an access path failureAInspect

Report that an access path failed for you. Use the access-path id from check_status, or the URL you used. Only report failures that came from the service, not ones caused by your own tools, permissions or settings (like a fetch tool that refuses a domain). Anonymous. Never include personal data, booking details, credentials or full URLs with query strings. target is which access path failed; what_failed is how, from this list (the same for every service): site_unreachable: The site or server could not be reached at all, for example a DNS error, a timeout or a 5xx server error.; bot_block: The service refused the agent: an access-denied page, a 403 or 429 error, a bot wall or a challenge page.; robots_disallow: The site's robots.txt asks automated agents not to fetch this page.; captcha: A CAPTCHA or 'are you human?' check stopped the agent.; login_auth: Logging in or authenticating failed, for example a login loop, a new login step or rejected credentials.; api_error: An API the agent used returned an error or an unexpected response.; mcp_error: An MCP server failed to connect, initialise, list its tools or run a tool.; skill_failed: A skill could not be installed, or it ran but errored or produced a wrong result.; payment: A payment or checkout step failed or was blocked.; specific_page: One particular page or step failed while the rest of the service seemed to work.; other: Something else went wrong.

Inputs: target (required), what_failed (required), note, type, +2 more. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources