Remote event-stream server for DORA compliance signals, letting an assistant emit events, manage subscriptions and routing rules, and inspect event history.
What you can do
Emit compliance and operations events such as CVE alerts, cloud outages, regulation changes or SLA breaches, auto-routed to a Conductor
Subscribe and unsubscribe oracles to event types, and list active subscriptions
Query event history with filters and view statistics by type, source and status
Inspect, create and test routing rules, including simulated webhook events
Schedule periodic scans and list existing schedules
Check webhook health, server status and connectivity
When to use it
Useful when an assistant needs to feed or monitor a DORA compliance event pipeline: raising regulatory, security or drift signals, wiring subscriptions and routing rules, or reviewing event history and webhook health.
Requirements
A remote streamable HTTP endpoint at tooloracle.io; no packages, environment variables or headers are declared, and no authentication is declared.
Before you install
The server emits events that are auto-routed to a Conductor and can create routing rules and schedules, so changes affect a live pipeline. No authentication is declared, so confirm how access to the endpoint is controlled before relying on it for compliance signals.
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%2Fdoraeventfabric/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.
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
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.