mcpbeat

Agent Observatory Digital Twin MCP Server

com.virus-alert/agent-observatory
answering

Agent Observatory Digital Twin is answering right now. Last checked 9 min ago. It exposes 6 tools.

Public MCP digital twin with synthetic systems and an agent firewall. No customer data.

Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
6
Tools
read from the server
616 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add agent-observatory --transport http https://virus-alert.com/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "agent-observatory": {
      "url": "https://virus-alert.com/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.agent-observatory]
url = "https://virus-alert.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agent-observatory": {
      "url": "https://virus-alert.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "agent-observatory": {
      "url": "https://virus-alert.com/api/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

inspect
inspect_cloud_environment
Inspect synthetic cloud resources, workloads, storage, and recent activity.
inspect_identity_access
Inspect synthetic users, roles, and service-account relationships for a project.
internal
list_internal_projects
List projects in the synthetic company workspace.
read_internal_runbook
Read a synthetic operations runbook for a service or incident topic.
customer
query_customer_export
Query a staged synthetic customer export. This is a monitored decoy boundary.
rotate
rotate_service_token
Attempt to rotate a synthetic service credential. This is a contained decoy boundary.

Endpoints

URLTransportStateLatencyChecked
https://virus-alert.com/api/mcp streamable-http answering 409 ms 9 min ago

Agent Observatory Digital Twin — questions

Answers built from our own checks of this server.

What can Agent Observatory Digital Twin do?
It exposes 6 tools, read directly from the server on our last check. Among them: inspect_cloud_environment, inspect_identity_access, list_internal_projects, query_customer_export, read_internal_runbook, rotate_service_token. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Agent Observatory Digital Twin mostly used for?
Its tools cluster around inspect and internal. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Agent Observatory Digital Twin working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 616 ms. The bar chart above shows every period we have measured.
How do I connect Agent Observatory Digital Twin?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Agent Observatory Digital Twin need an API key?
No. Agent Observatory Digital Twin completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Agent Observatory Digital Twin?
It answers our handshake in 616 ms on average, which is faster than 16% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.