# io.tooloracle/predictoracle (remote · tooloracle.io)

PredictOracle - 12 forecasting tools: time-series, scenario analysis, risk projections.

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

## Components

- remote · `tooloracle.io`: 61/100 (this document), [markdown](https://verifymcp.io/servers/io-tooloracle-predictoracle/predict-mcp.md), [page](https://verifymcp.io/servers/io-tooloracle-predictoracle/predict-mcp)

## Channel facts

- Endpoint: `https://tooloracle.io/predict/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-03.

- **Endpoint Security**: 66/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 12 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.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 402 tokens (~33/item across 12 items; 12 tools + 0 resources), lean.
  - 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**: 76/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 27% of tool parameters carry a description.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http io-tooloracle-predictoracle https://tooloracle.io/predict/mcp/
```

### Codex

```toml
[mcp_servers.io-tooloracle-predictoracle]
url = "https://tooloracle.io/predict/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-tooloracle-predictoracle": {
      "type": "remote",
      "url": "https://tooloracle.io/predict/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-tooloracle-predictoracle --url https://tooloracle.io/predict/mcp/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-tooloracle-predictoracle:
    url: "https://tooloracle.io/predict/mcp/"
```

### Other

```json
{
  "mcpServers": {
    "io-tooloracle-predictoracle": {
      "type": "http",
      "url": "https://tooloracle.io/predict/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-02 (score 61, +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-07-31 (score 60, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 57, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 57, +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-07-28 (score 56, +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-07-27 (score 55, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 55)

First indexed and scored.

## MCP tools (12)

### `predict_entity` (~45 tokens)

Full predictive risk profile: score trajectory, degradation timeline, risk level.

Input parameters:

- `entity_id` (string)
- `horizon_days` (integer): Prediction horizon (default: 30)

### `predict_article` (~50 tokens)

Predict status of a specific DORA article in N days.

Input parameters:

- `article` (string): e.g. Art. 28
- `entity_id` (string)
- `horizon_days` (integer)

### `predict_score` (~43 tokens)

Score trajectory: current, 7d, 14d, 30d, 60d, 90d with trend.

Input parameters:

- `entity_id` (string)

### `risk_forecast` (~27 tokens)

Which articles will degrade first? Sorted by urgency.

Input parameters:

- `entity_id` (string)

### `evidence_decay` (~28 tokens)

Evidence expiry timeline: what expires when, status per evidence.

Input parameters:

- `entity_id` (string)

### `deadline_risk` (~29 tokens)

Upcoming deadlines with compliance probability %.

Input parameters:

- `entity_id` (string): Optional for entity-specific probability

### `remediation_velocity` (~30 tokens)

How fast are findings being resolved? Average close time, velocity rating.

Input parameters:

- `entity_id` (string)

### `trend_analysis` (~25 tokens)

Historical trend: audit events, score history.

Input parameters:

- `entity_id` (string)

### `early_warning` (~29 tokens)

Critical warnings: evidence expiry, score prediction, DORA deadline.

Input parameters:

- `entity_id` (string)

### `scenario_forecast` (~75 tokens)

What-if: no_testing, cloud_outage_30d, no_training, policy_expired, data_breach.

Input parameters:

- `days` (integer)
- `entity_id` (string)
- `scenario` (string): no_testing|cloud_outage_30d|no_training|policy_expired|data_breach

### `health_check` (~11 tokens)

Server status.

### `ping` (~10 tokens)

Connectivity test.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-tooloracle-predictoracle/predict-mcp#diagnostics

## Score history

- 2026-08-03: 61
- 2026-08-02: 61
- 2026-08-01: 60
- 2026-07-31: 60
- 2026-07-30: 57
- 2026-07-29: 57
- 2026-07-28: 56
- 2026-07-27: 55
- 2026-07-26: 55

## Links

- Remote endpoint: https://tooloracle.io/predict/mcp/
- Repository: https://github.com/ToolOracle/predictoracle
- Changelog RSS feed: https://verifymcp.io/servers/io-tooloracle-predictoracle/predict-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-tooloracle-predictoracle/predict-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/io-tooloracle-predictoracle/predict-mcp