MCP
Canonical MCP gateway, tool registry, capability graph, and integration broker.
Validate MCP in BrowserOps
Preview the plan publicly or launch the trusted-domain browser check using the server-side Vercel PLATPHORM_API_KEY when no key is entered.
Live Public Connectivity
MCP public surfaces are reachable; configure a BrowserOps receive-handoff route before claiming downstream delivery.
health
200passed
trace echo not confirmed
apiDocs
200passed
trace echo not confirmed
llms
200passed
trace echo not confirmed
mcp
200passed
trace echo not confirmed
handoffReceiver
404degraded
trace echo not confirmed
Browserbase Runtime
Protected BrowserOps runs for MCP use browserbase. Browserbase is configured, project is configured, and session metadata records BrowserOps run ID, journey ID, and target service without storing target URLs in Browserbase metadata.
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; protected tool calls require PLATPHORM_API_KEY.
Handoff Examples
MCP remains the tool registry; BrowserOps only executes protected browser work after authorization.