Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.tooloracle/resilienceoracle

REMOTE · TOOLORACLE.IO · SCANNED AUG 3

ResilienceOracle - 10 operational resilience tools: BIA, RTO/RPO, scenario testing.

Available components

+7 this week 59 Trust /100
Trust breakdown (6 categories)

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. How we score →

Endpoint Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability49
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 582 tokens (~58/item across 10 items; 10 tools + 0 resources), lean.Pass
  • 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 Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 2% of tool parameters carry a description.Partial
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · tooloracle.io

# add to Claude Code
claude mcp add --transport http io-tooloracle-resilienceoracle https://tooloracle.io/resilience/mcp/
# ~/.codex/config.toml
[mcp_servers.io-tooloracle-resilienceoracle]
url = "https://tooloracle.io/resilience/mcp/"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-tooloracle-resilienceoracle": {
      "type": "remote",
      "url": "https://tooloracle.io/resilience/mcp/",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-tooloracle-resilienceoracle --url https://tooloracle.io/resilience/mcp/ --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-tooloracle-resilienceoracle:
    url: "https://tooloracle.io/resilience/mcp/"
// mcp.json
{
  "mcpServers": {
    "io-tooloracle-resilienceoracle": {
      "type": "http",
      "url": "https://tooloracle.io/resilience/mcp/"
    }
  }
}

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

Changelog

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.

  • 3 Aug 26 +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.

  • 1 Aug 26 +4
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 +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.

  • 27 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 51

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Probed https://tooloracle.io/resilience/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=tooloracle.io CN=YE1,O=Let's Encrypt,C=US 15 Jul 2026 13 Oct 2026 ECDSA 256 ECDSA-SHA384 5f17476491787e67dfd3d995c4c2b1679c9
SANs: mcp.tooloracle.io, tooloracle.io, www.tooloracle.io
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
DNSSEC secure

Validation of tooloracle.io. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
tooloracle.io. present 45856 8 Verified
tooloracle.io. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: https:; font-src 'self' data: https://fonts.gstatic.com; connect-src 'self' https://api.feedoracle.io https://tooloracle.io https://*.tooloracle.io https://fonts.googleapis.com wss://*.tooloracle.io; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none';
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=()
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://tooloracle.io/resilience/mcp/ Verified 200
http (plaintext) http://tooloracle.io/resilience/mcp/ HTTPS enforced 308 https://tooloracle.io/resilience/mcp/
MCP tools — 10 exposed · ~582 tokens

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.

Tool Tokens
bcm_gap_analysis ~17

BCM plan completeness analysis across all systems.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

crisis_plan_check ~95

Validate crisis communication plan elements (Art. 11(7)).

NameTypeReqDescription
communication_planboolean
crisis_drill_conductedboolean
crisis_team_definedboolean
customer_notification_processboolean
escalation_matrixboolean
internal_communicationboolean
media_handlingboolean
regulator_notification_processboolean

No output schema declared.

No examples provided.

evidence_bundle ~39

Collect BCM/DRP evidence for audit — systems, BIA, test records.

NameTypeReqDescription
system_idstringOptional: scope to one system

No output schema declared.

No examples provided.

health_check ~11

Server status.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

recovery_status ~19

Recovery readiness dashboard — how many systems are DR-ready.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

register_system ~111

Register a business-critical ICT system for BCM tracking.

NameTypeReqDescription
backup_frequencystring
backup_locationstring
criticalitystring
data_classificationstring
departmentstring
descriptionstring
failover_sitestring
notesstring
ownerstring
providerstring
system_idstring
system_namestringyes

No output schema declared.

No examples provided.

rto_rpo_check ~33

Validate RTO/RPO targets against actual backup/failover capabilities.

NameTypeReqDescription
system_idstring

No output schema declared.

No examples provided.

scenario_library ~26

DORA-relevant test scenario library (10 scenarios).

NameTypeReqDescription
severitystring

No output schema declared.

No examples provided.

set_bia ~117

Set Business Impact Analysis data — RTO, RPO, MTPD, financial impact.

NameTypeReqDescription
customers_affectedinteger
dependenciesstring
financial_impact_per_hournumber
mtpd_hoursnumber
recovery_priorityinteger
regulatory_impactstring
reputational_impactstring
rpo_hoursnumber
rto_hoursnumber
system_idstringyes

No output schema declared.

No examples provided.

test_register ~114

Register a DR/BCM test execution with results and evidence.

NameTypeReqDescription
evidence_refstring
issues_foundstring
participantsstring
remediation_actionsstring
resultstringyes
rpo_achieved_hoursnumber
rto_achieved_hoursnumber
scenariostringyes
system_idstring
test_datestring
test_typestring

No output schema declared.

No examples provided.