io.tooloracle/reporting
REMOTE · TOOLORACLE.IO
ReportingOracle — 16 regulatory reporting tools: BaFin, ESMA, FINREP, COREP, ICAAP, ILAAP.
Available components
Last scanned (19 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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 16 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 Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 630 tokens (~39/item across 16 items; 16 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 Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 14% 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 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 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
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 16 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 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
- 28 Sept 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
- 25 Sept 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 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
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 21 Nov 2026 · Probed https://tooloracle.io/reporting/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 | 12 Nov 2026 | 10 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 56ada3c3c9667f6eeefdd0b9dbc93811aa2 |
| 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 |
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. | DS published | 38690 | 8 | Verified |
| tooloracle.io. | DS published | 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 'none'; frame-ancestors 'none'; base-uri 'none'; form-action '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/reporting/mcp/ | Verified | 200 | |
| http (plaintext) | http://tooloracle.io/reporting/mcp/ | HTTPS enforced | 308 | https://tooloracle.io/reporting/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 →
annual_report ~49
Annual ICT risk management report for board + NCA (Art. 6(5)). Auto-fills from AmpelOracle.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | – |
| year | integer | – | – |
No output schema declared.
No examples provided.
approve_report ~48
Approve a draft report (4-eyes). Status: draft → approved.
| Name | Type | Req | Description |
|---|---|---|---|
| approved_by | string | yes | – |
| entity_id | string | yes | – |
| report_id | string | yes | – |
No output schema declared.
No examples provided.
deadline_tracker ~35
All DORA reporting deadlines per entity with days-until countdown.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | Optional — empty for general deadlines |
No output schema declared.
No examples provided.
get_report ~32
Get full report content by report_id.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | yes | – |
| report_id | string | yes | – |
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.
incident_report ~150
Generate ITS 2024/1772 incident report for BaFin (initial/intermediate/final). Art. 19-20. Deadlines: 4h/72h/30d.
| Name | Type | Req | Description |
|---|---|---|---|
| affected_clients | string | – | – |
| affected_services | string | – | – |
| containment | string | – | – |
| description | string | – | – |
| detection_date | string | – | – |
| entity_id | string | – | – |
| incident_id | string | – | – |
| remediation | string | – | – |
| report_type | string | – | initial|intermediate|final |
| root_cause | string | – | – |
| severity | string | – | major|significant |
| title | string | – | – |
No output schema declared.
No examples provided.
incident_status ~28
Track all incident reports per entity with deadlines and overdue status.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | – |
No output schema declared.
No examples provided.
management_letter ~47
Generate management response letter to findings. 4-eyes principle.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | – |
| finding_ids | string | – | Comma-separated finding IDs (empty=all open) |
No output schema declared.
No examples provided.
nca_submission_status ~31
Track all NCA submissions with deadlines, status, overdue alerts.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | – |
No output schema declared.
No examples provided.
obligation_map ~29
Reporting obligations DORA-RPT-01 to RPT-08 with deadlines and cross-jurisdiction.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ping ~10
Connectivity test.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
report_templates ~20
Available ITS/RTS report templates with mandatory fields count.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
roi_export ~43
Generate Register of Information ITS export (Art. 28(3)). Pulls providers from AmpelOracle, checks ITS mandatory fields.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | – |
No output schema declared.
No examples provided.
roi_validate ~27
Validate Register of Information against ITS mandatory fields per provider.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | – |
No output schema declared.
No examples provided.
sync_from_ampel ~30
Pull latest entity data from AmpelOracle for report population.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | – |
No output schema declared.
No examples provided.
tlpt_report ~40
Generate TLPT results summary for NCA submission (Art. 26(8)). Pulls from TestOracle.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | – |
No output schema declared.
No examples provided.
How do I install the io.tooloracle/reporting MCP server?
io.tooloracle/reporting is a hosted endpoint at https://tooloracle.io/reporting/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-reporting 'https://tooloracle.io/reporting/mcp/'
What is the io.tooloracle/reporting MCP server?
io.tooloracle/reporting is an MCP server listed in the public MCP registry as io.tooloracle/reporting. ReportingOracle, 16 regulatory reporting tools: BaFin, ESMA, FINREP, COREP, ICAAP, ILAAP. This page covers its hosted endpoint (https://tooloracle.io/reporting/mcp/).
Is the io.tooloracle/reporting MCP server safe to use?
io.tooloracle/reporting scores 76 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/reporting MCP server expose?
io.tooloracle/reporting exposes 16 tools: incident_report, incident_status, roi_export, roi_validate, tlpt_report, and 11 more. Their descriptions and schemas cost roughly 630 tokens of context every time the server is loaded.
Does the io.tooloracle/reporting MCP server require authentication?
No. We connected to io.tooloracle/reporting without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.tooloracle/reporting MCP server still maintained?
io.tooloracle/reporting is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.tooloracle/reporting MCP server?
VerifyMCP ran 12 checks on io.tooloracle/reporting, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.tooloracle/reporting: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.