io.github.BojanKovachki/recovery-probe
NPM · RECOVERY-PROBE
Fail reads in web and Electron test apps, inspect recovery, and compare before/after evidence.
Available components
Last scanned (9 hours ago)
Scores higher than 39% 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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- 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 7 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 74% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 4 Nov 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.
- 2 Nov 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.
- 31 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.
- 29 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.
- 28 Oct 26 66
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 5 Nov 2026 · Analysed npm/recovery-probe@1.0.2
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 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
check_read_recovery Check that a page recovers when a read fails ~272
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint | string | yes | 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 | yes | 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 | yes | Page of a development or test app. |
No output schema declared.
No examples provided.
compare_reports Compare reports from before and after a change ~184
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.
| Name | Type | Req | Description |
|---|---|---|---|
| after | array | yes | Reports of the same check from after the change. |
| afterLabel | string | – | Name for the after side, such as the branch. |
| before | array | yes | Reports from before the change: report.json files or their folders. |
| beforeLabel | string | – | Name for the before side, such as main. |
No output schema declared.
No examples provided.
find_page_reads Find the reads behind a page ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| durationMs | integer | – | How long to watch after the page loads. |
| storageState | string | – | Playwright storage state file of a signed-in test account. |
| url | string | yes | Page of a development or test app. |
No output schema declared.
No examples provided.
find_suspects Find failure handling that can lose data ~176
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
network_fault_summary Show what the network faults did ~53
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_recovery_probe Run a Recovery Probe command ~145
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.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | yes | Command and arguments, for example ["observe", "--config", "observe.json", "--json"]. |
| timeoutMs | integer | – | – |
No output schema declared.
No examples provided.
set_network_faults Arm or remove network faults ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| restore | boolean | – | – |
| rules | array | – | – |
No output schema declared.
No examples provided.
start_network_faults Start a network fault proxy ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| port | integer | – | – |
No output schema declared.
No examples provided.
stop_network_faults Stop the network fault proxy ~23
Removes every fault, closes the proxy and returns its final summary.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_change Verify a code change with before and after evidence ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
npm · recovery-probe
claude mcp add bojankovachki-recovery-probe -- npx -y recovery-probe mcp
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.