# RECOVER — Safe Next-Step Decisions After Machine Failures (remote · recover-api-production-bbba.up.railway.app)

Deterministic next-step decisions after failed API, MCP, automation, or AI-agent actions.

- Trust score: 66/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-20

## Components

- remote · `recover-api-production-bbba.up.railway.app`: 66/100 (this document), [markdown](https://verifymcp.io/servers/gsterlingpress-recover/recover-api-production-bbba.md), [page](https://verifymcp.io/servers/gsterlingpress-recover/recover-api-production-bbba)

## Channel facts

- Endpoint: `https://recover-api-production-bbba.up.railway.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-08-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 350 tokens (~350/item across 1 items; 1 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**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http gsterlingpress-recover https://recover-api-production-bbba.up.railway.app/mcp
```

### Codex

```toml
[mcp_servers.gsterlingpress-recover]
url = "https://recover-api-production-bbba.up.railway.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gsterlingpress-recover": {
      "type": "remote",
      "url": "https://recover-api-production-bbba.up.railway.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add gsterlingpress-recover --url https://recover-api-production-bbba.up.railway.app/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  gsterlingpress-recover:
    url: "https://recover-api-production-bbba.up.railway.app/mcp"
```

### Other

```json
{
  "mcpServers": {
    "gsterlingpress-recover": {
      "type": "http",
      "url": "https://recover-api-production-bbba.up.railway.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-08-20 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-18 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-16 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-14 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-13 (score 62, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-12 (score 62)

First indexed and scored.

## MCP tools (1)

### `recover_decide` (~273 tokens)

Use immediately after an API, MCP tool, automation, or agent action fails and before retrying. Especially use after timeouts, 5xx/429 responses, uncertain execution, or any side-effecting action that may already have completed. Returns the safest deterministic next action: RETRY_NOW, WAIT, REPAIR_REQUEST, VERIFY_FIRST, ESCALATE, or ABORT. Do not use before an action or for successful actions.

Input parameters:

- `attempt` (number): Current attempt number.
- `error` (string): Short failure/error message.
- `headers` (object): Relevant response headers such as Retry-After.
- `idempotencyKey` (boolean): True if a valid idempotency key protects a retry.
- `maxAttempts` (number): Maximum allowed attempts if known.
- `method` (string): HTTP/action method when known, e.g. GET, POST, PATCH, DELETE.
- `providerRetryable` (boolean): True only when the provider explicitly marks the failure retryable.
- `sideEffect` (boolean): True if the failed action could create, modify, send, charge, delete, or otherwise change external state.
- `status` (number): Failure HTTP/status code when available.
- `uncertainExecution` (boolean): True when it is unknown whether the action completed before the failure became visible.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/gsterlingpress-recover/recover-api-production-bbba#diagnostics

## Score history

- 2026-08-20: 66
- 2026-08-19: 65
- 2026-08-18: 65
- 2026-08-17: 64
- 2026-08-16: 64
- 2026-08-15: 63
- 2026-08-14: 63
- 2026-08-13: 62
- 2026-08-12: 62

## Links

- Remote endpoint: https://recover-api-production-bbba.up.railway.app/mcp
- Repository: https://github.com/GSterlingPress/recover-api
- Changelog RSS feed: https://verifymcp.io/servers/gsterlingpress-recover/recover-api-production-bbba.xml
- Changelog JSON feed: https://verifymcp.io/servers/gsterlingpress-recover/recover-api-production-bbba.json
- HTML version of this page: https://verifymcp.io/servers/gsterlingpress-recover/recover-api-production-bbba