MCP
Canonical MCP gateway, tool registry, capability graph, and integration broker.
Validate MCP in BrowserOps
BrowserOps checks the public page, metadata, accessibility, console state, network failures, trace propagation, and screenshot evidence without taking over MCP's product role.
- Target
- https://mcp.platphormnews.com
- Journey
- PlatPhorm MCP homepage smoke
Held in memory only and sent in the authorization header.
Boundary
Public preview validates intent. Cloudflare runs create real browser evidence. Downstream delivery is tracked as a handoff and is never marked accepted without a response.
Integration run state
Preview the BrowserOps plan publicly, then use the operator key for a protected Cloudflare browser check.
Live Public Connectivity
MCP public surfaces are reachable; configure a BrowserOps receive-handoff route before claiming downstream delivery.
health
200passed
trace echoed
apiDocs
200passed
trace echoed
llms
200passed
trace echo not confirmed
mcp
200passed
trace echoed
handoffReceiver
no responsedegraded
trace echo not confirmed
Cloudflare Browser Runtime
BrowserOps runs for MCP use cloudflare-browser-run. Cloudflare is configured; D1 stores run metadata and R2 stores artifacts. Session metadata records BrowserOps run ID, journey ID, and target service without storing credentials.
Capability Mapping
BrowserOps may call
- tools/list
- resources/list
- capability_graph
BrowserOps may receive
- tools/call:run_browserops_journey
- resources/read:browserops_evidence
Transport and Boundary
- Preferred transports
- mcp, openapi
- API docs
- https://mcp.platphormnews.com/api/docs
- MCP status
- https://mcp.platphormnews.com/.well-known/mcp.json
- Auth boundary
- Read-only MCP introspection may be public-safe; tool calls use BrowserOps-managed service credentials or service-to-service authorization.
Handoff Examples
MCP remains the tool registry; BrowserOps only executes browser work for trusted targets after authorization is satisfied.