Server Details
ThousandEyes MCP Server for network intelligence: outages, anomalies, alerts, events, and tests.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
2 toolsget_public_application_outagesGet Public Application OutagesRead-onlyInspect
Get Open Application Outages (No Authentication Required).
Returns a list of publicly available application outages from ThousandEyes Internet Insights. This endpoint does not require authentication and provides visibility into global application infrastructure outages.
Use this to:
Monitor current application outages affecting SaaS providers, cloud services, and web applications
Track macro-level impact of application-layer Internet events
Get real-time visibility into application infrastructure issues
Args:
latest_seconds: Time window in seconds to look back (default: 86400 = 24 hours)
minimum_outage_duration_seconds: Minimum duration filter (default: 200 seconds)Returns:
List of application outage events with details about affected infrastructure| Name | Required | Description | Default |
|---|---|---|---|
| latest_seconds | No | Time window in seconds to look back for outages. Default is 86400 (24 hours). Common values: 3600 (1h), 86400 (24h), 604800 (7d). | |
| minimum_outage_duration_seconds | No | Minimum outage duration in seconds to filter results. Default is 200 seconds. |
get_public_network_outagesGet Public Network OutagesRead-onlyInspect
Get Open Network Outages (No Authentication Required).
Returns a list of publicly available network and/or application outages from ThousandEyes Internet Insights. This endpoint does not require authentication and provides visibility into global Internet infrastructure outages.
Use this to:
Monitor current Internet outages affecting ISPs, DNS providers, CDNs, and SaaS providers
Track macro-level impact of Internet events
Get real-time visibility into infrastructure issues
Args:
latest_seconds: Time window in seconds to look back (default: 86400 = 24 hours)
minimum_outage_duration_seconds: Minimum duration filter (default: 200 seconds)Returns:
List of outage events with details about affected infrastructure| Name | Required | Description | Default |
|---|---|---|---|
| latest_seconds | No | Time window in seconds to look back for outages. Default is 86400 (24 hours). Common values: 3600 (1h), 86400 (24h), 604800 (7d). | |
| minimum_outage_duration_seconds | No | Minimum outage duration in seconds to filter results. Default is 200 seconds. |
Verify Ownership
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 verified, the connector will appear as claimed by you.
Last verification attempt failed.
Failed to fetch .well-known/glama.json: HTTP 401
Control your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
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!