Platform
Integrations
Revelion connects to the tools your team already uses, and exposes itself to the agents that increasingly do the asking.
Where the work already happens
Findings arrive where your team is looking
Security output that lives only in a portal is security output nobody reads. Revelion pushes into the surfaces you already watch.
- Slack
- Mission status and validated findings delivered to the channel that owns the estate, with severity attached.
- MCP server
- Revelion exposes a Model Context Protocol server, so your own agents and assistants can query missions and findings directly.
- API
- A documented HTTP API for triggering missions, pulling findings and wiring results into your own systems.
Agent-native
Built to be consumed by other agents, not just people
Most security tooling assumes a human will log into a dashboard. That assumption is ageing quickly. Increasingly the thing that wants to know whether an estate is exploitable is another piece of software.
Revelion ships an MCP server so an assistant can ask about mission state, retrieve validated findings and reason about remediation without a human relaying the answer. The same information is available through the API for anything that speaks HTTP.
It also means the site itself is machine-readable: the documentation is published in a form agents can consume, rather than locked inside rendered pages.
Wire it into what you already run.
Read the API docs