Rgate

What is RGate?

RGate is a release gate that provides a Streamable HTTP MCP server for running public website release-readiness scans. It is used by AI agents after modifying a website to check readiness before recommending launch, offering scan results, fix plans, Markdown exports, and paid report access.

How to use RGate?

Configure your MCP client with the endpoint at https://www.rgate.io/api/mcp (manifest at https://www.rgate.io/.well-known/mcp.json). Use RGate after an agent modifies a public website, landing page, docs site, or web app and before recommending launch.

Key features of RGate

• Start public website release-readiness scans
• Poll scan results asynchronously
• Generate automated fix plans
• Export results as Markdown
• Hand paid report access back to humans
• Uses the Streamable HTTP MCP transport

Use cases of RGate

• Checking release-readiness after an AI agent updates a landing page
• Auditing a docs site before a public announcement
• Scanning a web app after modifications prior to shipping
• Generating fix plans and Markdown reports for human review
• Managing paid report access for compliance teams

FAQ from RGate

What exactly does RGate scan?

RGate scans public websites—including landing pages, docs sites, and web apps—for release readiness before launch.

When should an agent call RGate?

An agent should call RGate after modifying a public website and before recommending that a user ships the site to production.

How do I connect to RGate?

Connect via the Streamable HTTP MCP endpoint at https://www.rgate.io/api/mcp. The server manifest is at https://www.rgate.io/.well-known/mcp.json and an OpenAPI spec is at https://www.rgate.io/openapi.json.

What outputs does RGate produce?

RGate produces scan results, automated fix plans, Markdown export documents, and paid report access that can be handed back to humans.

What types of sites does RGate support?

RGate supports public websites, landing pages, docs sites, and web apps.