reporting MCP server
io.tooloracle/reportingtooloracle.iostreamable-httpv1.0.0Scanned
ReportingOracle — 16 regulatory reporting tools: BaFin, ESMA, FINREP, COREP, ICAAP, ILAAP.
16 tools: 11 change things and 5 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
With Anlyon
11 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the reporting MCP server can do
The reporting MCP server is published by tooloracle.io, a domain the MCP Registry verified. It has 16 tools. It can create or change data (11 tools: incident_report, roi_export, tlpt_report, annual_report and 7 more), but cannot delete data. 5 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 21, 2026, version 1.0.0.
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.
16 tools
Changes things 11Claude Code: ask
annual_reportAnnual ICT risk management report for board + NCA (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 Annual ICT risk management report for board + NCA (Art. 6(5)). Auto-fills from AmpelOracle.
approve_reportApprove a draft report (4-eyes).No findings
Why it is in this group
- The name "approve_report" says "approve": a word for a change.
Description, as the server wrote it Approve a draft report (4-eyes). Status: draft → approved.
deadline_trackerAll DORA reporting deadlines per entity with days-until countdown.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 All DORA reporting deadlines per entity with days-until countdown.
health_checkServer 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 status.
incident_reportGenerate ITS 2024/1772 incident report for BaFin (initial/intermediate/final).No findings
Why it is in this group
- The description's first verb is "generate": a word for a change.
Description, as the server wrote it Generate ITS 2024/1772 incident report for BaFin (initial/intermediate/final). Art. 19-20. Deadlines: 4h/72h/30d.
management_letterGenerate management response letter to findings.No findings
Why it is in this group
- The description's first verb is "generate": a word for a change.
Description, as the server wrote it Generate management response letter to findings. 4-eyes principle.
obligation_mapReporting obligations DORA-RPT-01 to RPT-08 with deadlines and cross-jurisdiction.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 Reporting obligations DORA-RPT-01 to RPT-08 with deadlines and cross-jurisdiction.
report_templatesAvailable ITS/RTS report templates with mandatory fields count.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 Available ITS/RTS report templates with mandatory fields count.
roi_exportGenerate Register of Information ITS export (Art.No findings
Why it is in this group
- The description's first verb is "generate": a word for a change.
Description, as the server wrote it Generate Register of Information ITS export (Art. 28(3)). Pulls providers from AmpelOracle, checks ITS mandatory fields.
sync_from_ampelPull latest entity data from AmpelOracle for report population.No findings
Why it is in this group
- The name "sync_from_ampel" says "sync": a word for a change.
Description, as the server wrote it Pull latest entity data from AmpelOracle for report population.
tlpt_reportGenerate TLPT results summary for NCA submission (Art.No findings
Why it is in this group
- The description's first verb is "generate": a word for a change.
Description, as the server wrote it Generate TLPT results summary for NCA submission (Art. 26(8)). Pulls from TestOracle.
Only reads 5Show 5 read-only tools
get_reportGet full report content by report_id.No findings
Why it is in this group
- The name "get_report" says "get": a word for reading.
Description, as the server wrote it Get full report content by report_id.
incident_statusTrack all incident reports per entity with deadlines and overdue status.No findings
Why it is in this group
- The name "incident_status" says "status": a word for reading.
Description, as the server wrote it Track all incident reports per entity with deadlines and overdue status.
nca_submission_statusTrack all NCA submissions with deadlines, status, overdue alerts.No findings
Why it is in this group
- The name "nca_submission_status" says "status": a word for reading.
Description, as the server wrote it Track all NCA submissions with deadlines, status, overdue alerts.
pingConnectivity test.No findings
Why it is in this group
- The name "ping" says "ping": a word for reading.
Description, as the server wrote it Connectivity test.
roi_validateValidate Register of Information against ITS mandatory fields per provider.No findings
Why it is in this group
- The name "roi_validate" says "validate": a word for reading.
Description, as the server wrote it Validate Register of Information against ITS mandatory fields per provider.
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 Nov 20, 2026, 19:31 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
- 11
- 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/reporting/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 11 tools that change things (11 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://tooloracle.io/reporting/mcp/: tools/list returned 16 tools to an anonymous client, including incident_report (write), roi_export (write), tlpt_report (write), annual_report (write), management_letter (write) and 6 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 reporting https://tooloracle.io/reporting/mcp/claude mcp add --transport http reporting https://tooloracle.io/reporting/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__reporting__incident_status",
"mcp__reporting__roi_validate",
"mcp__reporting__nca_submission_status",
"mcp__reporting__get_report",
"mcp__reporting__ping"
],
"ask": [
"mcp__reporting__incident_report",
"mcp__reporting__roi_export",
"mcp__reporting__tlpt_report",
"mcp__reporting__annual_report",
"mcp__reporting__management_letter",
"mcp__reporting__deadline_tracker",
"mcp__reporting__report_templates",
"mcp__reporting__obligation_map",
"mcp__reporting__sync_from_ampel",
"mcp__reporting__approve_report",
"mcp__reporting__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 reporting. 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://radar.anlyon.com/api/v1/servers/io.tooloracle/reporting/verify?hash=1a5882d830a45e4f078008017515ae2647ef03ce371ec0cf0e6d669995f46b32" | jq -e '.changed == false'Pinned hash 1a5882d830a4, from Nov 21, 2026, 17:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.tooloracle/reporting/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.tooloracle/reporting)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:52 UTC.
reporting MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the reporting MCP server safe?
- No scan can promise that. What its definitions show: 16 tools, 11 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the reporting MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the reporting MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the reporting MCP server have?
- 16 tools: 11 write, 5 read. incident_report, roi_export, tlpt_report, annual_report, management_letter, deadline_tracker, report_templates, obligation_map and 8 more.
Does the reporting MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the reporting MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the reporting MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.