reporting
Server Details
ReportingOracle — 16 regulatory reporting tools: BaFin, ESMA, FINREP, COREP, ICAAP, ILAAP.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 2.9/5 across 16 of 16 tools scored. Lowest: 2/5.
Each tool targets a distinct reporting function (e.g., annual, incident, TLPT, ROI) or supporting task (deadlines, validation, approval), with no overlap in purpose.
Most tool names follow a descriptive noun_noun or verb_noun pattern with underscores, but 'ping' and mixed styles (e.g., 'sync_from_ampel' vs 'obligation_map') cause minor inconsistency.
16 tools cover a comprehensive reporting domain without being excessive; each tool has a clear justification, though slightly above the typical 3-15 range.
The surface covers core lifecycle stages: generation, retrieval, approval, deadlines, validation, and submission. Missing update/delete tools are acceptable given the regulatory context where reports are typically not modified after approval.
Available Tools
16 toolsannual_reportInspect
Annual ICT risk management report for board + NCA (Art. 6(5)). Auto-fills from AmpelOracle.
| Name | Required | Description | Default |
|---|---|---|---|
| year | No | ||
| entity_id | No |
approve_reportInspect
Approve a draft report (4-eyes). Status: draft → approved.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | Yes | ||
| report_id | Yes | ||
| approved_by | Yes |
deadline_trackerInspect
All DORA reporting deadlines per entity with days-until countdown.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No | Optional — empty for general deadlines |
get_reportInspect
Get full report content by report_id.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | Yes | ||
| report_id | Yes |
health_checkInspect
Server status.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
incident_reportInspect
Generate ITS 2024/1772 incident report for BaFin (initial/intermediate/final). Art. 19-20. Deadlines: 4h/72h/30d.
| Name | Required | Description | Default |
|---|---|---|---|
| title | No | ||
| severity | No | major|significant | |
| entity_id | No | ||
| root_cause | No | ||
| containment | No | ||
| description | No | ||
| incident_id | No | ||
| remediation | No | ||
| report_type | No | initial|intermediate|final | |
| detection_date | No | ||
| affected_clients | No | ||
| affected_services | No |
incident_statusInspect
Track all incident reports per entity with deadlines and overdue status.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No |
management_letterInspect
Generate management response letter to findings. 4-eyes principle.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No | ||
| finding_ids | No | Comma-separated finding IDs (empty=all open) |
nca_submission_statusInspect
Track all NCA submissions with deadlines, status, overdue alerts.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No |
obligation_mapInspect
Reporting obligations DORA-RPT-01 to RPT-08 with deadlines and cross-jurisdiction.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
pingInspect
Connectivity test.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
report_templatesInspect
Available ITS/RTS report templates with mandatory fields count.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
roi_exportInspect
Generate Register of Information ITS export (Art. 28(3)). Pulls providers from AmpelOracle, checks ITS mandatory fields.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No |
roi_validateInspect
Validate Register of Information against ITS mandatory fields per provider.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No |
sync_from_ampelInspect
Pull latest entity data from AmpelOracle for report population.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No |
tlpt_reportInspect
Generate TLPT results summary for NCA submission (Art. 26(8)). Pulls from TestOracle.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!