Revensi
Trigger Revensi domain scans from your MCP client before launch or after DNS changes without opening a separate security UI.
Overview
Revensi MCP is a MCP server for the Ship phase that lets any MCP client invoke Revensi API domain scans over streamable HTTP.
What is this MCP server?
- MCP bridge to the Revensi API for domain scans
- Remote streamable-http endpoint at mcp.revensi.com/mcp
- Callable from any MCP-compatible client
- Version 0.1.0 early API surface
- No local server install—hosted remote only
- Server version 0.1.0
- Remote endpoint: https://mcp.revensi.com/mcp (streamable-http)
- MCP schema: 2025-12-11 server.schema.json
What problem does it solve?
You forget to run an external domain check until after deploy, or you lose time hopping between your editor and a security scanner UI.
Who is it for?
Indie operators who want lightweight domain scanning wired into Claude Code or Cursor during launch and security hardening.
Skip if: Enterprises needing full continuous ASM, code SAST, or compliance programs with no third-party security API dependency.
What do I get? / Deliverables
Your agent can request Revensi domain scans in the same session where you fix DNS, TLS, or launch checklist items.
- Agent-triggered Revensi domain scan results
- Launch checklist step completed inside the agent workflow
Recommended MCP Servers
Journey fit
How it compares
Domain-scan API MCP, not a local penetration-testing skill bundle.
Common Questions / FAQ
Who is com.revensi/revensi for?
Solo builders and small teams shipping web properties who use MCP agents and want Revensi domain scans without leaving the dev environment.
When should I use com.revensi/revensi?
Use it in Ship when a domain is live or staging, especially before launch, after DNS cuts, or when validating a new marketing or app hostname.
How do I add com.revensi/revensi to my agent?
Configure remote MCP https://mcp.revensi.com/mcp (streamable-http) in your client and supply Revensi API credentials as required by Revensi.