# io.github.BojanKovachki/recovery-probe (npm · recovery-probe) Fail reads in web and Electron test apps, inspect recovery, and compare before/after evidence. - Trust score: 70/100 (medium) - Change this week: +3 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - npm · `recovery-probe`: 70/100 (this document), [markdown](https://verifymcp.io/servers/bojankovachki-recovery-probe/recovery-probe.md), [page](https://verifymcp.io/servers/bojankovachki-recovery-probe/recovery-probe) ## Channel facts - Registry: `npm` - Package: `recovery-probe` - Version: `1.0.2` - Transport: `stdio` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Supply Chain Security**: 100/100 - No malware found by supply-chain analysis. - No known CVEs affecting this package version or its production dependencies. - No install/post-install scripts declared. - No production dependencies, so there is no dependency health to assess. - **Provenance & Transparency**: 48/100 - Source repository is publicly reachable at the declared URL. - Provenance check failed: no build-provenance attestation is published. - Clear OSI-approved license (MIT). - Actively maintained (last published 7 days ago). - Publishes a security disclosure policy (SECURITY.md). - **Schema Quality & AI Usability**: 62/100 - AI-judged instruction clarity (good). - Context-footprint check failed: tool/resource definitions use about 1538 tokens (~153/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 27/100 - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 91/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 74% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 60/100 - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. ## Install ### How do I install the io.github.BojanKovachki/recovery-probe MCP server? io.github.BojanKovachki/recovery-probe runs locally as an npm package, launched with npx -y recovery-probe mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add bojankovachki-recovery-probe -- npx -y recovery-probe mcp ``` ### Cursor ```json { "mcpServers": { "bojankovachki-recovery-probe": { "command": "npx", "args": [ "-y", "recovery-probe", "mcp" ] } } } ``` ### VS Code ```json { "servers": { "bojankovachki-recovery-probe": { "command": "npx", "args": [ "-y", "recovery-probe", "mcp" ] } } } ``` ### Codex ```bash codex mcp add bojankovachki-recovery-probe -- npx -y recovery-probe mcp ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "bojankovachki-recovery-probe": { "type": "local", "command": [ "npx", "-y", "recovery-probe", "mcp" ], "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add bojankovachki-recovery-probe --command npx --arg -y --arg recovery-probe --arg mcp ``` ### Hermes ```yaml mcp_servers: bojankovachki-recovery-probe: command: "npx" args: ["-y", "recovery-probe", "mcp"] ``` ### Netclaw ```json { "McpServers": { "bojankovachki-recovery-probe": { "Transport": "stdio", "Command": "npx", "Arguments": [ "-y", "recovery-probe", "mcp" ] } } } ``` ### Vellum ```bash assistant mcp add bojankovachki-recovery-probe -t stdio -c npx -a -y recovery-probe mcp ``` ### Other ```json { "mcpServers": { "bojankovachki-recovery-probe": { "command": "npx", "args": [ "-y", "recovery-probe", "mcp" ] } } } ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-04 (score 70, +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. ### 2026-11-02 (score 69, +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. ### 2026-10-31 (score 68, +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. ### 2026-10-29 (score 67, +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. ### 2026-10-28 (score 66) First indexed and scored. ## MCP tools (10) ### `find_page_reads` (~110 tokens) Find the reads behind a page Opens a page in headless Chromium and lists the JSON GET requests it makes while it loads. Use it to choose the endpoint for check_read_recovery. Only successful page fetch and XHR reads are seen; native, IPC and service-worker traffic is not. Input parameters: - `durationMs` (integer): How long to watch after the page loads. - `storageState` (string): Playwright storage state file of a signed-in test account. - `url` (string, required): Page of a development or test app. ### `check_read_recovery` (~272 tokens) Check that a page recovers when a read fails Loads the page healthy, then fails one GET endpoint with each fault kind and checks that the ready marker comes back: by itself (recovery "automatic") or after clicking retrySelector ("retry"). Returns an outcome per fault, why the healthy baseline failed if it did, the text the screen showed under a fault it did not recover from, and the report folder, which includes fix-brief.md and reproduce.mjs. Input parameters: - `endpoint` (string, required): Origin and path of the GET read to fail, as find_page_reads lists it. - `faults` (array): Which faults to apply; all of http-error, connection-failure, invalid-json by default. - `readySelector` (string, required): CSS selector of the one element that is visible only once that read has rendered its data. It must match exactly one element: for a list, choose its container or a single item, not a selector every i… - `readyText` (string): Text the ready element must contain. - `recovery` (string) - `retrySelector` (string): Required when recovery is "retry". - `storageState` (string) - `timeoutMs` (integer) - `times` (integer): How many consecutive requests each fault fails. - `url` (string, required): Page of a development or test app. ### `start_network_faults` (~79 tokens) Start a network fault proxy Starts a loopback HTTPS proxy for an app's own connections (an SDK, a main process, a CLI or a test run). Start the app or tests with the returned environment; connections pass until set_network_faults arms rules. Faults apply to whole connections per host: HTTPS stays end to end. Input parameters: - `port` (integer) ### `set_network_faults` (~61 tokens) Arm or remove network faults Replaces the armed rules, or removes them all with restore: true. Windows count from this call. Set dropOpen on a rule so clients that keep connections open have to reconnect. Input parameters: - `restore` (boolean) - `rules` (array) ### `network_fault_summary` (~53 tokens) Show what the network faults did Reports how many connections went through the proxy and, for the armed rules, how many each matched and faulted. A rule that faulted nothing means the app did not use the proxy or the host name is wrong. ### `stop_network_faults` (~23 tokens) Stop the network fault proxy Removes every fault, closes the proxy and returns its final summary. ### `find_suspects` (~176 tokens) Find failure handling that can lose data Reads JavaScript and TypeScript sources, without running them, for two patterns: UNKNOWN_AS_EMPTY (a failed or unexpected read becomes an empty collection, so "unknown" looks like "none") and FAILURE_ONLY_LOGGED (a read stores its data when it succeeds, but its failure is only logged). Each suspect names the read to fail and the check that proves or dismisses it. Use changedSince "main" to scan only what a branch changed. Needs TypeScript in the project. Input parameters: - `changedSince` (string): Git reference, such as main: scan only the files changed since it, uncommitted and untracked ones included. - `includeTests` (boolean): Scan test files too. - `paths` (array): Files and directories to scan, relative to the working directory. Default: all of it. ### `compare_reports` (~184 tokens) Compare reports from before and after a change Compares reports of the same check from before and after a change, such as main and a branch, and returns a verdict (IMPROVED, PARTLY_IMPROVED, REGRESSED, MIXED, UNCHANGED, INCONCLUSIVE or NOT_COMPARABLE), what happened to each problem, and a Markdown block for a pull request. A problem counts as gone only when a complete run after the change checked it, so a run that stopped early is never a fix. Give several reports per side for repeated runs. Input parameters: - `after` (array, required): Reports of the same check from after the change. - `afterLabel` (string): Name for the after side, such as the branch. - `before` (array, required): Reports from before the change: report.json files or their folders. - `beforeLabel` (string): Name for the before side, such as main. ### `verify_change` (~150 tokens) Verify a code change with before and after evidence Call with baseline true before changing the code, and without it before saying the change is done. The plan file lists the checks that prove the change. Verify reruns them, compares the runs with the baseline, and scans the lines changed since the plan base for suspects. VERIFIED needs every check improved or clean with complete runs on both sides, and no suspect on a changed line; otherwise the reasons say what to resolve. Do not call a change done while it is NOT_VERIFIED. Input parameters: - `baseline` (boolean): Record the runs from before the change instead of verifying it. - `plan` (string): The plan file, relative to the working directory. Default: .recovery-probe/verify.json. ### `run_recovery_probe` (~145 tokens) Run a Recovery Probe command Runs a Recovery Probe command that has no dedicated tool, such as check and discover for an Electron app or an attached browser, action, observe (with --steps, --network or --files), refresh, reads, windows, android --list or doctor (setup checks), and returns its exit code and output. Commands: check, discover, action, reads, windows, observe, refresh, android, doctor. Pass --json where the command supports it. See the package docs for each command's configuration. Input parameters: - `args` (array, required): Command and arguments, for example ["observe", "--config", "observe.json", "--json"]. - `timeoutMs` (integer) ## Diagnostics Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/bojankovachki-recovery-probe/recovery-probe#diagnostics ## Score history - 2026-11-05: 70 - 2026-11-04: 70 - 2026-11-03: 69 - 2026-11-02: 69 - 2026-11-01: 68 - 2026-10-31: 68 - 2026-10-30: 67 - 2026-10-29: 67 - 2026-10-28: 66 ## Common questions ### What is the io.github.BojanKovachki/recovery-probe MCP server? io.github.BojanKovachki/recovery-probe is an MCP server listed in the public MCP registry as io.github.BojanKovachki/recovery-probe. Fail reads in web and Electron test apps, inspect recovery, and compare before/after evidence. This page covers its npm package (recovery-probe). ### Is the io.github.BojanKovachki/recovery-probe MCP server safe to use? io.github.BojanKovachki/recovery-probe scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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.BojanKovachki/recovery-probe MCP server expose? io.github.BojanKovachki/recovery-probe exposes 10 tools: find_page_reads, check_read_recovery, start_network_faults, set_network_faults, network_fault_summary, and 5 more. Their descriptions and schemas cost roughly 1,253 tokens of context every time the server is loaded. ### Is the io.github.BojanKovachki/recovery-probe MCP server still maintained? io.github.BojanKovachki/recovery-probe is still listed as active in the MCP registry. We last reached this channel on 5 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.BojanKovachki/recovery-probe MCP server under? io.github.BojanKovachki/recovery-probe declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls. ### What did VerifyMCP test on the io.github.BojanKovachki/recovery-probe MCP server? VerifyMCP ran 16 checks on io.github.BojanKovachki/recovery-probe, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out. ## Links - npm package: https://www.npmjs.com/package/recovery-probe - Socket report: https://socket.dev/npm/package/recovery-probe - Repository: https://github.com/BojanKovachki/recovery-probe - Changelog RSS feed: https://verifymcp.io/servers/bojankovachki-recovery-probe/recovery-probe.xml - Changelog JSON feed: https://verifymcp.io/servers/bojankovachki-recovery-probe/recovery-probe/changelog.json - Trust report (JSON): https://verifymcp.io/servers/bojankovachki-recovery-probe/recovery-probe.json - HTML version of this page: https://verifymcp.io/servers/bojankovachki-recovery-probe/recovery-probe