RGate MCP
RGate MCP server scans public websites for release-readiness across five quality layers: security, SEO, accessibility, legal compliance, and sustainability. Here's what you can do:
Start a scan (
start_scan): Kick off an asynchronous scan for any public URL.Poll scan status & retrieve results (
get_scan): Monitor scan progress and fetch structured findings, check results, tech detections, and an agent summary once complete. Supports report tokens for full, non-redacted access.Unlock a free report (
unlock_report): During active campaigns, submit an email to receive a 24-hour token granting full access to findings and fix plans at no cost.Create a checkout handoff (
create_checkout_handoff): Generate a URL to send a human to purchase a full report or subscription when a report is paywalled.Browse the check catalog (
list_checks): Explore all checks RGate performs, optionally filtered by layer.Get pricing info (
get_pricing): Retrieve machine-readable plan details including names, prices, billing periods, scan limits, and use cases.Generate a fix plan (
generate_fix_plan): Build a prioritized, implementation-ready fix plan from scan findings — release blockers first, then high-impact items, then backlog — in JSON or Markdown, optionally filtered by layer.Export scan as Markdown (
export_scan_markdown): Export results using templates suited for Cursor agent prompts, GitHub issues, or executive summaries.Compare two scans (
compare_scan_history): Diff two completed scans of the same domain to identify added, resolved, improved, or worsened findings — useful for tracking progress or catching regressions after a deploy.
Allows exporting scan results as a GitHub issue body for tracking website quality improvements.
RGate MCP Server
RGate is the release gate agents call before they tell users a public website is ready to ship.
This repository documents the public RGate MCP server for agentic IDEs, coding agents, and MCP clients. The RGate product source code is not published here; this repo is the public integration and directory listing home for the operated MCP endpoint.
Server
MCP endpoint:
https://www.rgate.io/api/mcpTransport: Streamable HTTP
Manifest:
https://www.rgate.io/.well-known/mcp.jsonOpenAPI:
https://www.rgate.io/openapi.jsonAgent guide:
https://www.rgate.io/agents.mdDeveloper docs:
https://www.rgate.io/en/developersAgent recipes:
https://www.rgate.io/en/agent-recipes
Related MCP server: blop
What RGate Does
RGate scans public websites across five release-readiness layers:
Security
SEO
Accessibility
Legal compliance
Sustainability
Agents can start a scan, poll structured results, inspect the check catalog, generate fix plans, export Markdown, compare scan history, and hand paid report access back to a human.
MCP Client Configuration
{
"mcpServers": {
"rgate": {
"url": "https://www.rgate.io/api/mcp",
"transport": "streamable-http"
}
}
}Tools
Tool | Purpose |
| Start an RGate website quality scan for a public URL. |
| Fetch scan status and, once complete, structured findings and results. |
| Describe RGate scan layers and the check catalog. |
| Return machine-readable plan names, prices, limits, and use cases. |
| Create a human handoff URL for purchasing report access or a subscription. |
| Generate a prioritized release-readiness fix plan from findings. |
| Export scan results as Markdown for Cursor, GitHub issues, or summaries. |
| Compare two scans and return added, resolved, improved, and worsened findings. |
Example Agent Flow
Confirm the user is allowed to scan the public website.
Call
start_scanwith the public URL.Poll
get_scanwith the returnedscanIduntil status isdoneorfailed.If the target passed green, report that the website passed the release gate.
If access is locked, send the human to the report URL for checkout and poll the same
scanIdagain after payment.Generate a fix plan or Markdown export for the coding agent working on that project.
Related Integrations
CLI:
npm install -g @rgate_io/rgateSkill:
npx skills add marcoldenburg/rgate-release-readiness-skillSkill repository:
https://github.com/marcoldenburg/rgate-release-readiness-skill
Directory Metadata
Glama:
glama.jsonat repo root (maintainer claim for listing)Name:
rgateTitle:
RGateDescription:
Release gate agents call before they tell users a public website is ready to ship. Scans public websites across security, SEO, accessibility, legal compliance, and sustainability.Tags:
developer-tools,release-readiness,mcp,agent-tools,website-audit,security,seo,accessibility,compliance,sustainability
Running as a local stdio server (build checks / directory harnesses)
RGate is a remote MCP server hosted at https://www.rgate.io/api/mcp
(transport: Streamable HTTP). Some runners — including Glama's automated
build/quality check — start a local stdio process and speak MCP to it. This
repo doubles as a thin stdio↔remote bridge for exactly that:
npm install
npm start # = mcp-remote https://www.rgate.io/api/mcpGlama admin configuration
Build steps:
["npm install"]Start command:
npm start(ormcp-remote https://www.rgate.io/api/mcp)Node.js ≥ 18; Python/base-image defaults are fine.
For direct clients (Cursor, Claude, VS Code) just use the remote URL from
mcp.json — no bridge needed.
Maintenance
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/marcoldenburg/rgate-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server