Other · Remote MCP server

Agent Gateway

Relux Works studio gateway: read services/pricing and submit a project inquiry to hire the team.

Visit Agent Gateway's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
works.relux/agent-gateway
Version
1.0.0
Status
Active
Category
other
Transport
Streamable HTTP
Published
2026-07-06
Updated
2026-07-06
Publisher
works.relux
Namespace
Namespace verified by the MCP Registry via the domain relux.works · how
Website
relux.works
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://api.relux.works/mcpNone

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 200)
Handshake
relux-works-agent-gateway 1.3.0 · protocol 2025-06-18
Tools discovered
2: get_services_pricing, request_project_quote
Checked on
2026-10-05

How the live check works

How to connect Agent Gateway

Agent Gateway is a remote MCP server: there is nothing to install. Its endpoint is https://api.relux.works/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More other servers

All 8,395 →
ServerRunsEndpoint or package
Agent Failure Archive186 real AI agent post-mortems, 107 of them measurement failures. Free tools, paid via x402.Remote · HTTPLive check: ✓ handshakedesktop-ai2ata5-1.tailfeb765.ts.net
Agent Firewall MCPInput/output safety for AI agents: known-pattern injection and obfuscation scan, URL/IP, secrets.Local · stdionpm: agent-firewall-mcp
Agent GateLocal mandate gate and proof trail for AI agents that take consequential actions.Local · stdionpm: forge-agent-gate
Agent GateFail-closed quality gate and hash-chained receipt ledger for AI agent workflows.Local · stdioPyPI: mcp-agent-gate
Agent Graph AuditorFinds transitive excessive agency across LangGraph/CrewAI/AutoGen orchestration graphs.Local · stdionpm: @guardbee/mcp-agent-graph-auditor
Agent GuardSafety checks an agent runs before it acts: package malware, destructive command, secret leak.Local · stdioPyPI: agent-tripwire
Agent Guard MCPVerify-before-act safety checks for AI agents: packages, lockfiles, manifests, CI workflows.Local · stdionpm: @liminallablibs/agent-guard-mcp
Agent GuardrailDeterministic policy firewall for AI agent tool calls - YAML rules, not a fuzzy risk score.Local · stdioPyPI: guardrail-mcp