io.tooloracle/resilienceoracle
REMOTE · TOOLORACLE.IO · SCANNED SEP 23
ResilienceOracle - 10 operational resilience tools: BIA, RTO/RPO, scenario testing.
Available components
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 → Why this is hard to 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.tooloracle/resilienceoracle MCP server?
io.tooloracle/resilienceoracle is a hosted endpoint at https://tooloracle.io/resilience/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · tooloracle.io
claude mcp add --transport http io-tooloracle-resilienceoracle 'https://tooloracle.io/resilience/mcp/'
{
"mcpServers": {
"io-tooloracle-resilienceoracle": {
"url": "https://tooloracle.io/resilience/mcp/"
}
}
} {
"servers": {
"io-tooloracle-resilienceoracle": {
"type": "http",
"url": "https://tooloracle.io/resilience/mcp/"
}
}
} [mcp_servers.io-tooloracle-resilienceoracle] url = "https://tooloracle.io/resilience/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-tooloracle-resilienceoracle": {
"type": "remote",
"url": "https://tooloracle.io/resilience/mcp/",
"enabled": true
}
}
} openclaw mcp add io-tooloracle-resilienceoracle --url 'https://tooloracle.io/resilience/mcp/' --transport streamable-http
mcp_servers:
io-tooloracle-resilienceoracle:
url: "https://tooloracle.io/resilience/mcp/" {
"McpServers": {
"io-tooloracle-resilienceoracle": {
"Transport": "http",
"Url": "https://tooloracle.io/resilience/mcp/"
}
}
} assistant mcp add io-tooloracle-resilienceoracle -t streamable-http -u 'https://tooloracle.io/resilience/mcp/'
{
"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.
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.
- 30 Aug 26 0
- Stability: 0.97 → pass security
- 29 Aug 26 0
- Stability: pass → 0.97 functional
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 72
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Aug 26 0
- 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 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 23 Sept 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=YE2,O=Let's Encrypt,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6375d594a6b9fdf6754e5a9a3d1f38b0dbd |
| SANs: mcp.tooloracle.io, tooloracle.io, www.tooloracle.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 |
Background: What to check on a remote MCP endpoint →
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=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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/ |
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 →
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)).
| Name | Type | Req | Description |
|---|---|---|---|
| communication_plan | boolean | – | – |
| crisis_drill_conducted | boolean | – | – |
| crisis_team_defined | boolean | – | – |
| customer_notification_process | boolean | – | – |
| escalation_matrix | boolean | – | – |
| internal_communication | boolean | – | – |
| media_handling | boolean | – | – |
| regulator_notification_process | boolean | – | – |
No output schema declared.
No examples provided.
evidence_bundle ~39
Collect BCM/DRP evidence for audit — systems, BIA, test records.
| Name | Type | Req | Description |
|---|---|---|---|
| system_id | string | – | Optional: 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.
| Name | Type | Req | Description |
|---|---|---|---|
| backup_frequency | string | – | – |
| backup_location | string | – | – |
| criticality | string | – | – |
| data_classification | string | – | – |
| department | string | – | – |
| description | string | – | – |
| failover_site | string | – | – |
| notes | string | – | – |
| owner | string | – | – |
| provider | string | – | – |
| system_id | string | – | – |
| system_name | string | yes | – |
No output schema declared.
No examples provided.
rto_rpo_check ~33
Validate RTO/RPO targets against actual backup/failover capabilities.
| Name | Type | Req | Description |
|---|---|---|---|
| system_id | string | – | – |
No output schema declared.
No examples provided.
scenario_library ~26
DORA-relevant test scenario library (10 scenarios).
| Name | Type | Req | Description |
|---|---|---|---|
| severity | string | – | – |
No output schema declared.
No examples provided.
set_bia ~117
Set Business Impact Analysis data — RTO, RPO, MTPD, financial impact.
| Name | Type | Req | Description |
|---|---|---|---|
| customers_affected | integer | – | – |
| dependencies | string | – | – |
| financial_impact_per_hour | number | – | – |
| mtpd_hours | number | – | – |
| recovery_priority | integer | – | – |
| regulatory_impact | string | – | – |
| reputational_impact | string | – | – |
| rpo_hours | number | – | – |
| rto_hours | number | – | – |
| system_id | string | yes | – |
No output schema declared.
No examples provided.
test_register ~114
Register a DR/BCM test execution with results and evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| evidence_ref | string | – | – |
| issues_found | string | – | – |
| participants | string | – | – |
| remediation_actions | string | – | – |
| result | string | yes | – |
| rpo_achieved_hours | number | – | – |
| rto_achieved_hours | number | – | – |
| scenario | string | yes | – |
| system_id | string | – | – |
| test_date | string | – | – |
| test_type | string | – | – |
No output schema declared.
No examples provided.
What is the io.tooloracle/resilienceoracle MCP server?
io.tooloracle/resilienceoracle is an MCP server listed in the public MCP registry as io.tooloracle/resilienceoracle. ResilienceOracle - 10 operational resilience tools: BIA, RTO/RPO, scenario testing. This page covers its hosted endpoint (https://tooloracle.io/resilience/mcp/).
Is the io.tooloracle/resilienceoracle MCP server safe to use?
io.tooloracle/resilienceoracle scores 74 out of 100 on VerifyMCP. 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.tooloracle/resilienceoracle MCP server expose?
io.tooloracle/resilienceoracle exposes 10 tools: register_system, set_bia, rto_rpo_check, test_register, scenario_library, and 5 more. Their descriptions and schemas cost roughly 582 tokens of context every time the server is loaded.
Does the io.tooloracle/resilienceoracle MCP server require authentication?
No. We connected to io.tooloracle/resilienceoracle without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.tooloracle/resilienceoracle MCP server still maintained?
io.tooloracle/resilienceoracle is still listed as active in the MCP registry. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.