Local MCP capabilities provider for Expo
Nothing to run from here
Recovery Probe is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
trust score
10
tools declared
local
runs on your machine
—
downloads a day
What it does
Fail reads in web and Electron test apps, inspect recovery, and compare before/after evidence.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user recovery-probe-mcp '--' npx -y recovery-probe mcp
# 2 — ask your agent for something these tools do
# find_page_reads, check_read_recovery, find_suspects and 7 more
Recovery Probe costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
BOAll 1 server
BojanKovachki1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Recovery Probe as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user recovery-probe-mcp '--' npx -y recovery-probe mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Page of a development or test app. |
| durationMs | integer | no | How long to watch after the page loads. |
| storageState | string | no | Playwright storage state file of a signed-in test account. |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Page of a development or test app. |
| endpoint | string | yes | Origin and path of the GET read to fail, as find_page_reads lists it. |
| 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 it |
| readyText | string | no | Text the ready element must contain. |
| recovery | string | no | — |
| retrySelector | string | no | Required when recovery is "retry". |
| faults | array | no | Which faults to apply; all of … by default. |
| times | integer | no | How many consecutive requests each fault fails. |
| timeoutMs | integer | no | — |
| storageState | string | no | — |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| paths | array | no | Files and directories to scan, relative to the working directory. Default: all of it. |
| changedSince | string | no | Git reference, such as main: scan only the files changed since it, uncommitted and untracked ones included. |
| includeTests | boolean | no | Scan test files too. |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| before | array | yes | Reports from before the change: report.json files or their folders. |
| after | array | yes | Reports of the same check from after the change. |
| beforeLabel | string | no | Name for the before side, such as main. |
| afterLabel | string | no | Name for the after side, such as the branch. |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| baseline | boolean | no | Record the runs from before the change instead of verifying it. |
| plan | string | no | The plan file, relative to the working directory. Default: .recovery-probe/verify.json. |
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:…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| args | array | yes | Command and arguments, for example ["observe", "--config", "observe.json", "--json"]. |
| timeoutMs | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| port | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rules | array | no | — |
| restore | boolean | no | — |
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.
No parameter schema on file.
Removes every fault, closes the proxy and returns its final summary.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Recovery Probe or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 93 / 100
Release 1.0.2 · scanned 30 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings10 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digestbf1194704f2194a6103e3de756ce885fdf86805fad862663f0bb87770fc93711
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can execute shell commands or code
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestbf1194704f2194a6
Scanned2026-10-30
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.0.2. Pin a release below and the command asks for exactly that one.
1.0.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Recovery Probe can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.