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

io.tooloracle/registeroracle

REMOTE · TOOLORACLE.IO · SCANNED SEP 23

RegisterOracle - 10-tool DORA Art.28 register: ICT third-party, contracts, criticality.

Available components

0 this week 77 Trust /100
Trust breakdown (7 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 → 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
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 611 tokens (~61/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 Coverage85
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 54% 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
Install

How do I install the io.tooloracle/registeroracle MCP server?

io.tooloracle/registeroracle is a hosted endpoint at https://tooloracle.io/register/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

# add to Claude Code
claude mcp add --transport http io-tooloracle-registeroracle 'https://tooloracle.io/register/mcp/'
// .cursor/mcp.json
{
  "mcpServers": {
    "io-tooloracle-registeroracle": {
      "url": "https://tooloracle.io/register/mcp/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-tooloracle-registeroracle": {
      "type": "http",
      "url": "https://tooloracle.io/register/mcp/"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.io-tooloracle-registeroracle]
url = "https://tooloracle.io/register/mcp/"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-tooloracle-registeroracle": {
      "type": "remote",
      "url": "https://tooloracle.io/register/mcp/",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-tooloracle-registeroracle --url 'https://tooloracle.io/register/mcp/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-tooloracle-registeroracle:
    url: "https://tooloracle.io/register/mcp/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-tooloracle-registeroracle": {
      "Transport": "http",
      "Url": "https://tooloracle.io/register/mcp/"
    }
  }
}
# add to Vellum
assistant mcp add io-tooloracle-registeroracle -t streamable-http -u 'https://tooloracle.io/register/mcp/'
// mcp.json
{
  "mcpServers": {
    "io-tooloracle-registeroracle": {
      "type": "http",
      "url": "https://tooloracle.io/register/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.

  • 26 Aug 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
  • 25 Aug 26 76
    • 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
  • 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
  • 30 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
  • 26 Jul 26 0

    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 23 Sept 2026 · Probed https://tooloracle.io/register/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/register/mcp/ Verified 200
http (plaintext) http://tooloracle.io/register/mcp/ HTTPS enforced 308 https://tooloracle.io/register/mcp/
MCP tools · 10 exposed · ~611 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. 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 →

Tool Tokens
concentration_risk ~34

Analyze ICT concentration risks across providers, countries, cloud types. DORA Art. 29 requires assessment of ICT concentration risk.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ctpp_check ~55

Assess if a provider might qualify as Critical Third-Party Provider (CTPP) under DORA Art. 31-44. CTTPPs face direct ESA oversight.

NameTypeReqDescription
provider_idstringyesProvider ID to assess

No output schema declared.

No examples provided.

export_its ~31

Export Register of Information in ITS-compliant format for supervisory reporting.

NameTypeReqDescription
formatstringExport format

No output schema declared.

No examples provided.

gap_analysis ~29

Identify gaps in the Register — missing fields, incomplete entries, missing exit plans, LEI coverage issues.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_provider ~37

Get full details, risk flags, and ITS completeness of a specific provider.

NameTypeReqDescription
provider_idstringyesProvider ID from list_providers

No output schema declared.

No examples provided.

health_check ~13

Server and data status.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_providers ~59

List all ICT third-party providers in the Register of Information with optional filters.

NameTypeReqDescription
countrystring
criticalitystring
searchstringSearch by name/type/function
service_typestring

No output schema declared.

No examples provided.

register_provider ~288

Add or update an ICT third-party provider in the DORA Register of Information (Art. 28). Tracks all ITS-required fields: LEI, service type, criticality, data location, exit plan, etc.

NameTypeReqDescription
annual_cost_eurnumberAnnual cost in EUR
audit_rightsboolean
certificationsstring
cloud_typestring
contract_endstringContract end (YYYY-MM-DD)
contract_startstringContract start (YYYY-MM-DD)
countrystringCountry of HQ (ISO 3166-1 alpha-2)
criticalitystring
data_locationstringData storage/processing location
exit_plan_existsbooleanExit strategy documented?
function_supportedstringBusiness function supported
last_risk_assessmentstring
leistringLegal Entity Identifier (20-char)
notesstring
notification_clauseboolean
provider_idstringUnique ID (auto-generated if empty)
provider_namestringyesName of ICT third-party provider
recovery_slastring
service_typestring
subcontractingbooleanUses sub-outsourcing?
substitutabilitystring

No output schema declared.

No examples provided.

register_stats ~29

Dashboard summary: provider counts, criticality distribution, ITS field completeness, exit plan and LEI coverage.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

validate_roi ~36

Validate entire Register of Information against DORA ITS requirements. Checks all mandatory fields, exit plans for critical providers, LEI coverage, etc.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the io.tooloracle/registeroracle MCP server?

io.tooloracle/registeroracle is an MCP server listed in the public MCP registry as io.tooloracle/registeroracle. RegisterOracle - 10-tool DORA Art.28 register: ICT third-party, contracts, criticality. This page covers its hosted endpoint (https://tooloracle.io/register/mcp/).

Is the io.tooloracle/registeroracle MCP server safe to use?

io.tooloracle/registeroracle scores 77 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/registeroracle MCP server expose?

io.tooloracle/registeroracle exposes 10 tools: register_provider, list_providers, get_provider, validate_roi, concentration_risk, and 5 more. Their descriptions and schemas cost roughly 611 tokens of context every time the server is loaded.

Does the io.tooloracle/registeroracle MCP server require authentication?

No. We connected to io.tooloracle/registeroracle without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.tooloracle/registeroracle MCP server still maintained?

io.tooloracle/registeroracle 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.