Reporting

io.tooloraclePublished by tooloracle.ioOfficial publisherv1.0.0Updated Oct 24, 2026

ReportingOracle — 16 regulatory reporting tools: BaFin, ESMA, FINREP, COREP, ICAAP, ILAAP.

The publisher's own server: Accessoracle

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

A remote MCP endpoint offering 16 regulatory reporting tools covering BaFin, ESMA, FINREP, COREP, ICAAP and ILAAP.

What you can do
ReportingOracle exposes 16 tools for regulatory reporting work, spanning German and European frameworks: BaFin, ESMA, FINREP, COREP, ICAAP and ILAAP. It runs as a remote streamable HTTP endpoint at tooloracle.io, so an assistant connects to it rather than running anything locally. The registry entry does not list individual tool names or parameters, so the exact operations each tool performs are not documented here.
When to use it
Worth considering when an assistant needs help with bank or financial regulatory reporting topics, such as preparing or interpreting FINREP, COREP, ICAAP or ILAAP material, or working with BaFin and ESMA reporting frameworks. It is a narrow, domain-specific server, so it adds little outside regulatory reporting.
Requirements
A remote MCP client that supports streamable HTTP, plus network access to the tooloracle.io endpoint. The manifest declares no authentication, no environment variables and no headers, and no local package or runtime is needed.
Before you install
The manifest declares no authentication, so consider whether the endpoint should be reachable without credentials and what data you send to it. No tool list is published, so verify what each tool actually does before relying on its output. Regulatory reporting output can be consequential; treat results as assistance, not as a compliance opinion.

Installation

In SourceWeft

  1. Open Reporting in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.tooloracle%2Freporting/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "reporting": {
      "type": "http",
      "url": "https://tooloracle.io/reporting/mcp/"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Tooloracle integrations