Skip to content

Interactive workbench / A deliberate action, a visible record

Keep the session open.
Keep the boundary visible.

Open a bounded session, inspect capabilities and explicitly request calls against an artifact held inside a confining sandbox.

The console shows data from an existing record or an assessment you explicitly request. Opening this page does not start a scan, open a sandbox or invoke a tool.

MCP Sentinel · operator console

Server console

Pick a product in the rail and a target to scan. The coverage-aware verdict, the category-to-evidence drill, and the scan replay appear once the scan completes. Open one from the registry.

Interactive workbench

Browse a server's tools, resources, and prompts, invoke them in our egress-denied jail, and chain one tool's output into another - all against our own fetched copy (ADR-007 T3). A live endpoint stays browse-only.

Surface

This deployment is not serving target surfaces, so there is nothing to browse here. That is a missing surface, not an empty one: it does not mean the targets you add have no tools.

Open a session to begin.

No chain yet. Feed one tool's output into another's input to draw an edge - each edge is labelled by how the connection was established (witnessed in the jail, inferred statically, or mere co-existence). An empty canvas is a coverage gap, never a clean bill of health.

LIVESession calls - as they happen, not a signed replay

No calls yet. Each invoke appends one immutable entry here. Nothing is a clean result until it is invoked and answered without an error; a refusal, an error, or an answer that is the tool's own error is shown as a gap.

Live registry dataPick a target above to run a scan.

02

A call has an answer.
An answer has a history.

Interactive calls require a healthy worker and a sandbox that proves filesystem confinement and blocked network egress. Session records retain responses, failed calls and handle lineage; an error answer is never presented as a clean result.

The portrait is an explanation of the feature. Operational results appear in the console itself.

Follow evidence and provenance

From an operation to a report

Keep the answer connected to its source.

Use the canonical server report to inspect findings and their assessment context. Exports and configured signatures carry that record forward without turning a missing observation into a successful check.

Explore reports and proof
Console · MCP Sentinel