ThousandEyes MCP
REMOTE · API.THOUSANDEYES.COM · 2 COMPONENTS · SCANNED AUG 3
ThousandEyes MCP Server for network intelligence: outages, anomalies, alerts, events, and tests.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 450 tokens (~225/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.thousandeyes.com
claude mcp add --transport http com-thousandeyes-mcp https://api.thousandeyes.com/mcp-public
[mcp_servers.com-thousandeyes-mcp] url = "https://api.thousandeyes.com/mcp-public"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-thousandeyes-mcp": {
"type": "remote",
"url": "https://api.thousandeyes.com/mcp-public",
"enabled": true
}
}
} openclaw mcp add com-thousandeyes-mcp --url https://api.thousandeyes.com/mcp-public --transport streamable-http
mcp_servers:
com-thousandeyes-mcp:
url: "https://api.thousandeyes.com/mcp-public" {
"mcpServers": {
"com-thousandeyes-mcp": {
"type": "http",
"url": "https://api.thousandeyes.com/mcp-public"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://api.thousandeyes.com/mcp-public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.thousandeyes.com,O=Cisco Systems Inc.,L=San Jose,ST=California,C=US | CN=HydrantID Server CA O1,OU=HydrantID Trusted Certificate Service,O=IdenTrust,C=US | 7 Feb 2026 | 11 Feb 2027 | RSA 2048 | SHA256-RSA | 40019c3566bd5425e44513581a3147fe |
| SANs: api.thousandeyes.com, api-ga.thousandeyes.com, api.eu1.thousandeyes.com, api.us2.thousandeyes.com | ||||||
| CN=HydrantID Server CA O1,OU=HydrantID Trusted Certificate Service,O=IdenTrust,C=US (CA) | CN=IdenTrust Commercial Root CA 1,O=IdenTrust,C=US | 12 Dec 2019 | 12 Dec 2029 | RSA 2048 | SHA256-RSA | 40016efb0a205cfaebe18f71d73abb78 |
DNSSEC insecure
Validation of api.thousandeyes.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| thousandeyes.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.thousandeyes.com/mcp-public | Verified | 200 | |
| http (plaintext) | http://api.thousandeyes.com/mcp-public | HTTPS enforced | 301 | https://api.thousandeyes.com:443/mcp-public |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
get_public_application_outages Get Public Application Outages ~224
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 | Type | Req | Description |
|---|---|---|---|
| latest_seconds | integer | — | 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 | integer | — | Minimum outage duration in seconds to filter results. Default is 200 seconds. |
No output schema declared.
No examples provided.
get_public_network_outages Get Public Network Outages ~226
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 | Type | Req | Description |
|---|---|---|---|
| latest_seconds | integer | — | 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 | integer | — | Minimum outage duration in seconds to filter results. Default is 200 seconds. |
No output schema declared.
No examples provided.