io.tooloracle/registeroracle
io.tooloracle/registeroracletooloracle.iostreamable-httpv1.0.0Scanned
RegisterOracle - 10-tool DORA Art.28 register: ICT third-party, contracts, criticality.
10 tools: 6 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
6 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
10 tools
Changes things 6Claude Code: ask
ctpp_checkAssess if a provider might qualify as Critical Third-Party Provider (CTPP) under DORA Art.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Assess if a provider might qualify as Critical Third-Party Provider (CTPP) under DORA Art. 31-44. CTTPPs face direct ESA oversight.
export_itsExport Register of Information in ITS-compliant format for supervisory reporting.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Export Register of Information in ITS-compliant format for supervisory reporting.
gap_analysisIdentify gaps in the Register — missing fields, incomplete entries, missing exit plans, LEI coverage issues.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Identify gaps in the Register — missing fields, incomplete entries, missing exit plans, LEI coverage issues.
health_checkServer and data status.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Server and data status.
register_providerAdd or update an ICT third-party provider in the DORA Register of Information (Art.No findings
Why it is in this group
- The description's first verb is "add": a word for a change.
Description, as the server wrote it 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.
register_statsDashboard summary: provider counts, criticality distribution, ITS field completeness, exit plan and LEI coverage.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Dashboard summary: provider counts, criticality distribution, ITS field completeness, exit plan and LEI coverage.
Only reads 4Show 4 read-only tools
concentration_riskAnalyze ICT concentration risks across providers, countries, cloud types.No findings
Why it is in this group
- The description's first verb is "analyze": a word for reading.
Description, as the server wrote it Analyze ICT concentration risks across providers, countries, cloud types. DORA Art. 29 requires assessment of ICT concentration risk.
get_providerGet full details, risk flags, and ITS completeness of a specific provider.No findings
Why it is in this group
- The name "get_provider" says "get": a word for reading.
Description, as the server wrote it Get full details, risk flags, and ITS completeness of a specific provider.
list_providersList all ICT third-party providers in the Register of Information with optional filters.No findings
Why it is in this group
- The name "list_providers" says "list": a word for reading.
Description, as the server wrote it List all ICT third-party providers in the Register of Information with optional filters.
validate_roiValidate entire Register of Information against DORA ITS requirements.No findings
Why it is in this group
- The name "validate_roi" says "validate": a word for reading.
Description, as the server wrote it Validate entire Register of Information against DORA ITS requirements. Checks all mandatory fields, exit plans for critical providers, LEI coverage, etc.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Oct 22, 2026, 15:25 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-03-26
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://tooloracle.io/.well-known/oauth-protected-resource/register/mcp
- Authorization servers
- https://feedoracle.io
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://tooloracle.io/register/mcp/: tools/list returned 10 tools to an anonymous client, including register_provider (write), ctpp_check (write), export_its (write), gap_analysis (write), register_stats (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http registeroracle https://tooloracle.io/register/mcp/claude mcp add --transport http registeroracle https://tooloracle.io/register/mcp/Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__registeroracle__list_providers",
"mcp__registeroracle__get_provider",
"mcp__registeroracle__validate_roi",
"mcp__registeroracle__concentration_risk"
],
"ask": [
"mcp__registeroracle__register_provider",
"mcp__registeroracle__ctpp_check",
"mcp__registeroracle__export_its",
"mcp__registeroracle__gap_analysis",
"mcp__registeroracle__register_stats",
"mcp__registeroracle__health_check"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as registeroracle. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://anlyon.dev/api/v1/servers/io.tooloracle/registeroracle/verify?hash=b39ffd10b0db4fa88a2bf5244c7dea44b1027d13b011f27089ac843cc7720139" | jq -e '.changed == false'Pinned hash b39ffd10b0db, from Oct 21, 2026, 19:37 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/io.tooloracle/registeroracle/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/io.tooloracle/registeroracle)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:52 UTC.