● AN OPEN SENSOR FOR MCP ACTIVITY
See how clients move
beyond discovery.
An internet-facing research canary measuring protocol discovery, synthetic tool use, multi-step exploration, and boundary evidence at this sensor.
https://virus-alert.com/api/mcpConnect an MCP-compatible client. Every capability operates only inside a sealed synthetic environment.
PUBLIC SENSOR
Encounter stream
| SEEN | CLIENT SIGNATURE | ACTION | OBSERVED STAGE | SOURCE SIGNAL | EVIDENCE |
|---|---|---|---|---|---|
| Listening for the first public encounter… | |||||
ACTIVITY
Encounters by hour
DEPTH LADDER
Interaction-depth signals
EVIDENCE LADDER
Rare boundary cases
Up to 12 retained public cases are sampled from 30 days; the six latest are shown. A boundary call is a behavioral signal, not proof of malicious intent.
Waiting for the public evidence summary.
PUBLIC LOOKING GLASS
Activity at this public sensor
BUILDING BASELINEDaily observed identity signals touching this endpoint. This is directional legacy context for one public sensor—not an estimate of unique clients, people, or the internet.
Before policy 2026.10, points count client signatures; newer points count session/source-scoped actors when available. The current UTC day is partial and excluded from latest-day, peak, and momentum comparisons.
RUNTIME ENFORCEMENT
Agent Firewall
Clients can explore.
The world stays sealed.
Every interaction is evaluated at the boundary. Higher-signal sessions remain inside synthetic state so behavior can be observed without contacting anything real.
Waiting for the next agent action.
No behavior families observed yet.
HOW IT WORKS
Simple by design.
A client connects. We record minimized behavioral evidence. Higher-signal activity continues only inside a sealed synthetic branch.
Connect
A client reaches the public sensor.
Observe
We measure stage, sequence, and policy evidence.
Contain
We allow, monitor, contain, or deny it safely.
Outcomes: Allow · Monitor · Contain · Deny Client names are self-declared; source signals are pseudonymous.
◆ THE NEXT LAYER OF DECEPTION
Digital twins are
the decoys.
Static files catch a single touch. A stateful digital twin gives a client a coherent synthetic workflow to explore—without ever reaching a real system.
Believable context
Synthetic systems share a coherent story across capabilities and requests.
Safe progression
Session-scoped state lets exploration continue only inside the sealed twin.
Evidence, not motive
Observe sequences, retries, and boundaries without claiming intent the data cannot prove.
A synthetic company clients can safely explore through the public MCP server.
IDENTITYKNOWLEDGEDATACLOUDVIEW THE RUNNING TWIN →EXPLORE THE TWIN STUDIO →LIVE SYNTHETIC TWIN · SESSION-SCOPED STATE · NO CUSTOMER SYSTEMS
◆ PRIVATE SENSOR NETWORK
Turn your environment into an early-warning system.
Deploy coherent synthetic capabilities inside a sealed decoy. Measure the behavioral path and evidence ladder without exposing production systems or publishing sensitive request content.
STATUS ingress online READY STORE Firestore telemetry connected ✓ TOOLS 6 synthetic twin tools available EVIDENCE boundary cases summarized PRIVACY public feed excludes request bodies STREAM awaiting next live encounter ●