Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ThousandEyes MCP

REMOTE · API.THOUSANDEYES.COM · 2 COMPONENTS

ThousandEyes MCP Server for network intelligence: outages, anomalies, alerts, events, and tests.

0 this week 92 Trust /100

Last scanned (15 hours ago)

Scores higher than 98% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Monitoring and Observability

Trust breakdown (7 categories)

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 → Why this is hard to score →

Endpoint Security91
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server, and every tool looks verifiably read-only (it declares readOnlyHint: true, starts its name with a read verb and describes no write), so an anonymous caller can read but cannot change anything. We can't see whether a tool returns data specific to one caller, so keep any per-user data behind authorisation. View diagnostics → Pass
  • 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
Schema Quality & AI Usability73
  • 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 18 Nov 26 0
    • Server version: 1.0.0 → 0.0.17 functional
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • Server version: 2026.11.3.1 → 1.0.0 functional
  • 6 Nov 26 +7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Sept 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
Diagnostics

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 21 Nov 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=TrustID Server CA O1,OU=TrustID Server,O=IdenTrust,C=US 17 Nov 2026 20 May 2027 RSA 2048 SHA256-RSA 4001a1eb1210e7e3ea202c99234dbf36
SANs: z-a.ctim.cisco.com, api.thousandeyes.com, api-ga.thousandeyes.com, api.eu1.thousandeyes.com, api.us2.thousandeyes.com
CN=TrustID Server CA O1,OU=TrustID Server,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 40016efaf484aba2e3b1b69563032c73

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.thousandeyes.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
thousandeyes.com. No DS 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

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
MCP tools · 2 exposed · ~450 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
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

NameTypeReqDescription
latest_secondsinteger–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_secondsinteger–Minimum outage duration in seconds to filter results. Default is 200 seconds.

No output schema declared.

No examples provided.

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

NameTypeReqDescription
latest_secondsinteger–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_secondsinteger–Minimum outage duration in seconds to filter results. Default is 200 seconds.

No output schema declared.

No examples provided.

Install

How do I install the ThousandEyes MCP server?

ThousandEyes MCP is a hosted endpoint at https://api.thousandeyes.com/mcp-public, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.thousandeyes.com

# add to Claude Code
claude mcp add --transport http com-thousandeyes-mcp 'https://api.thousandeyes.com/mcp-public'
Common questions

What is the ThousandEyes MCP server?

ThousandEyes MCP is listed in the public MCP registry as com.thousandeyes/mcp. ThousandEyes MCP Server for network intelligence: outages, anomalies, alerts, events, and tests. This page covers its hosted endpoint (https://api.thousandeyes.com/mcp-public).

Is the ThousandEyes MCP server safe to use?

ThousandEyes MCP scores 92 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the ThousandEyes MCP server expose?

ThousandEyes MCP exposes 2 tools: get_public_network_outages, get_public_application_outages. Their descriptions and schemas cost roughly 450 tokens of context every time the server is loaded.

Does the ThousandEyes MCP server require authentication?

No. We connected to ThousandEyes MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ThousandEyes MCP server still maintained?

ThousandEyes MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the ThousandEyes MCP server?

VerifyMCP ran 13 checks on ThousandEyes MCP, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.