Three-minute judge demo
See why WebMCP matters—without reading the whole appendix.
TrialBridge turns the same visible clinical-trial interface into typed, state-scoped browser capabilities. The agent does less guessing; the person keeps control.
No patient data required. The live check below uses only public capability metadata and one fixed, no-input method call.
Live current-browser check
Discover, then execute one safe method.
- Native APIChecking
- Public capability0/2 origin-scoped tools
- Security headers0/3 verified
- WebMCP enablementChecking
trialbridge_methodNo input, network request, model call, registry search, patient context, or write authority.
Not run. No tool has been executed.
Evidence boundary: this concise check proves only current-browser discovery and a fixed safe method. It does not prove model selection, registry execution, protected-state tools, Inspector behavior, or clinical quality.
Continue the visible journey
Three proofs. One human-controlled product.
- 01Discover
Two public tools follow the page origin.
The console above registers and verifies only the method and public-search capabilities.
Check this browser - 02Use the visible UI
Search Taiwan and worldwide registries.
Open the same declarative form a person sees and inspect the `胃癌 → gastric cancer` query bridge.
Open public 胃癌 search - 03Protect context
Private tools appear only after human confirmation.
The fictional workflow still requires masking, cloud organization, fact confirmation, and visible permission.
Open synthetic workflow
Technical appendix
Need every contract and evidence boundary?
The full lab keeps lifecycle diagnostics, live cloud-model selection, fixed public execution, Inspector acceptance, schemas, source links, and recorded receipts separate.