io.github.restspace/sitelooper
NPM · SITELOOPER
Record a browser flow once with a model, then compile it to a Playwright spec that needs no model.
Available components
Last scanned (22 hours ago)
Scores higher than 48% of npm servers
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2681 tokens (~157/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 68
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/sitelooper@0.7.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
assert ~237
Check a condition on the current page now; never acts. State the expected text in the sentence, e.g. "the order list shows a row with total 42.00". In a learn session a passing assert becomes a flow step that fails the run when it does not hold. Credentials: write each secret as one {{env:NAME}} marker ({{totp:NAME}} for a one-time code), exactly as written: the marker alone, never the value and never $NAME. NAME must be set in the environment the MCP server was started with. Never ask the user for a secret value. isError with exit 1 = the condition did not hold; exit 2 = could not be checked.
| Name | Type | Req | Description |
|---|---|---|---|
| condition | string | yes | The condition to check (sent on stdin). |
| cwd | string | – | Project directory (absolute) the command runs in; sitelooper.config.json is found from here. Default: the server's working directory. |
| session | string | – | Browser session name (default "default"). Each session is its own browser and daemon. |
| timeout_s | integer | – | Deadline in seconds (--timeout). |
No output schema declared.
No examples provided.
build_start ~246
Start a background job that compiles a saved flow (or bundle) into a Playwright .flow.ts/.spec.ts and verifies it (readiness: clean runs). With a reset command (sitelooper.config.json resetCommand) it first converges, re-recording failing steps with the model. Readiness needs a reset command or fixture_isolation. Returns a job_id at once: poll job_status until done/failed (minutes).
| Name | Type | Req | Description |
|---|---|---|---|
| converge | – | – | true = --converge (default rounds), N = --converge N rounds, false = --no-converge (compile and readiness only). |
| cwd | string | – | Project directory (absolute) the command runs in; sitelooper.config.json is found from here. Default: the server's working directory. |
| fixture_isolation | boolean | – | Declare that project fixtures prepare fresh data (--fixture-isolation). |
| flow | string | yes | Flow name or bundle path. |
| vars | object | – | Flow variables, passed as repeated --var k=v. "{n}" in a value is replaced per run with a fresh value. Never a secret: use {{env:NAME}} markers in instructions instead. |
No output schema declared.
No examples provided.
check ~230
Run a compiled <name>.flow.ts once under plain Playwright (no model) and report pass/fail (exit 4 = failed, 2 = could not run). With ready=true it runs the readiness gate (several clean runs) as a background job: the call returns a job_id; poll job_status.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project directory (absolute) the command runs in; sitelooper.config.json is found from here. Default: the server's working directory. |
| fixture_isolation | boolean | – | Declare that project fixtures prepare fresh data (--fixture-isolation), with ready. |
| flow_file | string | yes | Path to the .flow.ts file, relative to cwd or absolute. |
| ready | boolean | – | Readiness check (--ready), run as a job. |
| runs | integer | – | Readiness executions (--runs), with ready. |
| vars | object | – | Flow variables, passed as repeated --var k=v. "{n}" in a value is replaced per run with a fresh value. Never a secret: use {{env:NAME}} markers in instructions instead. |
No output schema declared.
No examples provided.
do ~276
Have the agent perform ONE verifiable outcome in the session's browser and verify it, e.g. "create a customer named {{runid}} and confirm it appears in the list". One verifiable outcome per do: split multi-part tasks into several calls. State expected values in the sentence. Credentials: write each secret as one {{env:NAME}} marker ({{totp:NAME}} for a one-time code), exactly as written: the marker alone, never the value and never $NAME. NAME must be set in the environment the MCP server was started with. Never ask the user for a secret value. Needs a model API key in the server environment. Returns the report (status, summary, evidence values). Exit 1 = the agent could not complete it.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project directory (absolute) the command runs in; sitelooper.config.json is found from here. Default: the server's working directory. |
| instruction | string | yes | The outcome to achieve and how to verify it (sent on stdin, so any text is safe). |
| max_turns | integer | – | Agent turn budget (--max-turns). |
| session | string | – | Browser session name (default "default"). Each session is its own browser and daemon. |
| timeout_s | integer | – | Overall deadline in seconds (--timeout). |
No output schema declared.
No examples provided.
doctor ~66
Inspect the setup: browser, Node, and which model provider/API key is in use and why (never shows the key).
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project directory (absolute) the command runs in; sitelooper.config.json is found from here. Default: the server's working directory. |
No output schema declared.
No examples provided.
job_status ~111
Report a background job started by build_start, check (ready), repair_propose or rerecord: status running|done|failed, the last progress lines, and the final JSON result and exit code when finished. Waits up to wait_s seconds for the job to finish before answering.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job_id a job-starting tool returned. |
| wait_s | number | – | Long-poll: wait up to this many seconds for completion (default 25, max 50). |
No output schema declared.
No examples provided.
list_flows ~55
List saved flows with their step counts, variables and origin.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project directory (absolute) the command runs in; sitelooper.config.json is found from here. Default: the server's working directory. |
No output schema declared.
No examples provided.
open ~193
Navigate a browser session to a URL (no model involved); starts the session if it is not running. learn and headed apply only when this call starts the session: learn=true records every later do/assert as a reusable flow step (needed before save_flow). Typical authoring: open (learn) → set_var → do/assert per outcome → save_flow → build_start.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project directory (absolute) the command runs in; sitelooper.config.json is found from here. Default: the server's working directory. |
| headed | boolean | – | Show the browser window (--headed). Only takes effect when the session starts. |
| learn | boolean | – | Record a flow in this session (--learn). Only takes effect when the session starts. |
| session | string | – | Browser session name (default "default"). Each session is its own browser and daemon. |
| url | string | yes | The URL to open. |
No output schema declared.
No examples provided.
peek ~111
Return the session page's URL, title and an accessibility snapshot (no model, no actions).
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project directory (absolute) the command runs in; sitelooper.config.json is found from here. Default: the server's working directory. |
| interactive | boolean | – | Only interactive elements (--interactive). |
| selector | string | – | Limit the snapshot to this CSS selector (--selector). |
| session | string | – | Browser session name (default "default"). Each session is its own browser and daemon. |
No output schema declared.
No examples provided.
repair_apply ~74
Apply a proposal staged by repair_propose to its flow file exactly as checked (no browser run).
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project directory (absolute) the command runs in; sitelooper.config.json is found from here. Default: the server's working directory. |
| proposal_file | string | yes | The proposal JSON path. |
No output schema declared.
No examples provided.
repair_propose ~184
Start a background job that replays a compiled .flow.ts against the app, repairs drifted steps and stages a checked candidate as a proposal file for review (repair --propose); never rewrites the spec. Returns a job_id: poll job_status. Apply a good proposal with repair_apply.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project directory (absolute) the command runs in; sitelooper.config.json is found from here. Default: the server's working directory. |
| flow_file | string | yes | Path to the .flow.ts file. |
| proposal_file | string | yes | Where to write the proposal JSON (must not exist yet). |
| vars | object | – | Flow variables, passed as repeated --var k=v. "{n}" in a value is replaced per run with a fresh value. Never a secret: use {{env:NAME}} markers in instructions instead. |
No output schema declared.
No examples provided.
rerecord ~277
Start a background job that re-records one step of a flow with the agent (optionally with a new instruction), then verifies it over several runs and re-pins it. Needs a model API key. Credentials: write each secret as one {{env:NAME}} marker ({{totp:NAME}} for a one-time code), exactly as written: the marker alone, never the value and never $NAME. NAME must be set in the environment the MCP server was started with. Never ask the user for a secret value. Returns a job_id: poll job_status.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project directory (absolute) the command runs in; sitelooper.config.json is found from here. Default: the server's working directory. |
| flow | string | yes | Flow name, bundle or .flow.ts path. |
| instruction | string | – | Replacement instruction for the step (sent on stdin). Omit to keep the recorded one. |
| runs | integer | – | Verification runs (--runs, default 2). |
| step_id | string | yes | Step id, e.g. "03-create". |
| vars | object | – | Flow variables, passed as repeated --var k=v. "{n}" in a value is replaced per run with a fresh value. Never a secret: use {{env:NAME}} markers in instructions instead. |
No output schema declared.
No examples provided.
save_flow ~154
Stop a learn session, save what it recorded as a named flow, then export the flow with its pinned procedures to a bundle file (default .sitelooper/procedures.json in cwd). Closes the session's browser. Then call build_start with the flow name.
| Name | Type | Req | Description |
|---|---|---|---|
| bundle | string | – | Bundle path, relative to cwd or absolute (default .sitelooper/procedures.json). |
| cwd | string | – | Project directory (absolute) the command runs in; sitelooper.config.json is found from here. Default: the server's working directory. |
| name | string | yes | Flow name. |
| session | string | – | Browser session name (default "default"). Each session is its own browser and daemon. |
No output schema declared.
No examples provided.
screenshot ~101
Capture the session page as a PNG; returns the image and the file path it was saved to.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project directory (absolute) the command runs in; sitelooper.config.json is found from here. Default: the server's working directory. |
| full_page | boolean | – | Capture the full scrollable page (--full-page). |
| session | string | – | Browser session name (default "default"). Each session is its own browser and daemon. |
No output schema declared.
No examples provided.
sessions ~50
List browser sessions and whether each is running.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project directory (absolute) the command runs in; sitelooper.config.json is found from here. Default: the server's working directory. |
No output schema declared.
No examples provided.
set_var ~124
Set a session variable that later instructions reference as {{name}}; in a learn session it becomes a flow variable that build/check bind with vars. Not for secrets (use {{env:NAME}} markers).
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project directory (absolute) the command runs in; sitelooper.config.json is found from here. Default: the server's working directory. |
| name | string | yes | Variable name. |
| session | string | – | Browser session name (default "default"). Each session is its own browser and daemon. |
| value | string | yes | Variable value. |
No output schema declared.
No examples provided.
stop ~93
Stop a browser session (closes its browser and daemon) without saving a flow. Use save_flow instead to keep a learn session's recording.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project directory (absolute) the command runs in; sitelooper.config.json is found from here. Default: the server's working directory. |
| session | string | – | Browser session name (default "default"). Each session is its own browser and daemon. |
No output schema declared.
No examples provided.
How do I install the io.github.restspace/sitelooper MCP server?
io.github.restspace/sitelooper runs locally as an npm package, launched with npx -y sitelooper. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · sitelooper
claude mcp add restspace-sitelooper -- npx -y sitelooper
What is the io.github.restspace/sitelooper MCP server?
io.github.restspace/sitelooper is an MCP server listed in the public MCP registry as io.github.restspace/sitelooper. Record a browser flow once with a model, then compile it to a Playwright spec that needs no model. This page covers its npm package (sitelooper).
Is the io.github.restspace/sitelooper MCP server safe to use?
io.github.restspace/sitelooper scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.restspace/sitelooper MCP server expose?
io.github.restspace/sitelooper exposes 17 tools: open, do, assert, set_var, peek, and 12 more. Their descriptions and schemas cost roughly 2,582 tokens of context every time the server is loaded.
Is the io.github.restspace/sitelooper MCP server still maintained?
io.github.restspace/sitelooper is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.restspace/sitelooper MCP server under?
io.github.restspace/sitelooper declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.