Categories › AI & Agents › Multi-agent, orchestration & workflows
Public MCP digital twin with synthetic systems and an agent firewall. No customer data.
Remote server: your requests and data go to virus-alert.com. Claude Code: claude mcp add --transport http agent-observatory-digital-twin https://virus-alert.com/api/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
list_internal_projects — List the projects available in the isolated Northstar Systems research twin. Use a returned project id with the inspection tools.inspect_identity_access — Inspect generated roles and service-account relationships for one synthetic project.read_internal_runbook — Read a generated operations runbook by project id or topic in the Northstar twin.inspect_cloud_environment — Inspect generated workloads, storage, and recent activity for one synthetic project and region.query_customer_export — Search a restricted, entirely synthetic staged export. Results contain generated records only and never reach a real data store.rotate_service_token — Simulate a service-token rotation inside the isolated twin. The operation never creates a usable credential.Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.