Developer · Remote MCP server
ThousandEyes MCP
ThousandEyes MCP Server for network intelligence: outages, anomalies, alerts, events, and tests.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.thousandeyes/mcp- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-01-29
- Updated
- 2026-01-29
- Publisher
- com.thousandeyes
- Namespace
- Namespace verified by the MCP Registry via the domain thousandeyes.com · how
- Website
- www.thousandeyes.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.thousandeyes.com/mcp | Authorization (required, secret) |
| Streamable HTTP | https://api.thousandeyes.com/mcp-public | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Endpoint
https://api.thousandeyes.com/mcp(HTTP)- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
- Endpoint
https://api.thousandeyes.com/mcp-public(HTTP)- Reachable
- Yes (HTTP 200)
- Handshake
- thousandeyes-mcp-open 1.0.0 · protocol 2025-06-18
- Tools discovered
- 2:
get_public_network_outages,get_public_application_outages - Checked on
- 2026-10-05
How to connect ThousandEyes MCP
ThousandEyes MCP is a remote MCP server: there is nothing to install. Its endpoints are https://api.thousandeyes.com/mcp and https://api.thousandeyes.com/mcp-public, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| ThinkReviewLive PR/MR code reviews via review_url_code. OAuth or portal Bearer auth. | Remote · HTTPLive check: sign-in required |
| ThinkrunBrowser control + session recording MCP for AI coding agents (Claude Code, Cursor) - real Chrome. | Local · stdio |
| THORLocal memory for coding agents. A rule with a runnable proof can refuse a wrong command. | Local · stdio |
| ThoughtProofPre-action gate: verify before pay/trade/write/deploy. execute=true only on ALLOW. | Local · stdio |
| Thread MindGit-friendly memory for AI coding: a tree of thread summaries with inherited context. | Local · stdio |
| thread-keeperMulti-agent shared brain across Claude, Codex, Antigravity, Gemini, Copilot, and VS Code. | Local · stdio |
| Threadctx MCPShared memory MCP server for AI coding agents - local by default, team-shared via threadctx.dev. | Local · stdio |
| three.ws BrainList LLM providers and run chat completions through the three.ws multi-provider router. | Local · stdio |