Cisco ThousandEyes MCP server
2 tools · Last check that passed 27 Oct 2026, 01:50 UTC
Cisco ThousandEyes' own public MCP server gives an agent the open application and network outages that ThousandEyes publishes from its Internet Insights, with no sign-in. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.
All 2 tools
| Tool | Counted as |
|---|---|
get_public_application_outages | Said to only read |
get_public_network_outages | Said to only read |
The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.
Recent checks
12 of the last 12 checks passed
A check passes when the server lists its tools. Checked at https://api.thousandeyes.com/mcp-public.
Recent changes
No change seen across the last 12 checks that passed.
From the scan of 27 Oct 2026, 01:52 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.
Know when Cisco ThousandEyes's tools change.
One email when Cisco ThousandEyes's official MCP server adds, removes or changes tools, with what changed. Nothing else.
What to watch for
- This is not ThousandEyes' main MCP server. That one, at api.thousandeyes.com/mcp, needs an API token or OAuth and can create and delete tests, alert rules and dashboards, and run instant tests that use up units. ThousandEyes' MCP server documentation
- ThousandEyes lists this address beside its main server in its registry entry, while its MCP documentation describes only the main server. ThousandEyes' entry in the official MCP registry
How to limit it
With Cisco ThousandEyes's own settings, as its documentation describes them. Stackduke has not tested them.
- ThousandEyes' registry entry asks for no sign-in at this address, so we recommend connecting it with no ThousandEyes credentials. ThousandEyes' entry in the official MCP registry
What Stackduke is designed to do
Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.
It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.