# works.relux/agent-gateway (remote · api.relux.works)

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

- Trust score: 59/100 (low)
- Change this week: −5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.relux.works`: 59/100 (this document), [markdown](https://verifymcp.io/servers/works-relux-agent-gateway/api.md), [page](https://verifymcp.io/servers/works-relux-agent-gateway/api)

## Channel facts

- Endpoint: `https://api.relux.works/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (request_project_quote).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 48/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 766 tokens (~383/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 2/100
  - Stability check failed: schema churn in the 8 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http works-relux-agent-gateway https://api.relux.works/mcp
```

### Codex

```toml
[mcp_servers.works-relux-agent-gateway]
url = "https://api.relux.works/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "works-relux-agent-gateway": {
      "type": "remote",
      "url": "https://api.relux.works/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add works-relux-agent-gateway --url https://api.relux.works/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  works-relux-agent-gateway:
    url: "https://api.relux.works/mcp"
```

### Other

```json
{
  "mcpServers": {
    "works-relux-agent-gateway": {
      "type": "http",
      "url": "https://api.relux.works/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-07-31 (score 59, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 59, −5)

- [security regression] Stability: 0.03 → fail
- [functional regression] Schema quality: 232 → 383
- [functional] Schema quality: excellent → good

### 2026-07-27 (score 64, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 63)

First indexed and scored.

## MCP tools (2)

### `get_services_pricing` (~123 tokens)

Get services and pricing

Returns Relux Works services, fixed-price packages, company facts, selected work, supported languages, and market-specific planning prices. Tool and service identifiers remain in English.

Input parameters:

- `market` (string): Preferred market or ISO country code, for example us, gb, de, ae, sa, sg, il, ca, or au.
- `preferred_language` (string): Preferred BCP 47 language for regional filtering and the agent presentation, for example de, fr, ar, ar-AE, fa, or he. Canonical catalog prose remains in English.

### `request_project_quote` (~385 tokens)

Request a project quote

Creates and immediately sends an external project inquiry to a private Relux Works Telegram chat for human review. Do not call it to test the connector or demonstrate MCP. Build the summary from known conversation context, ask only for missing details, obtain a real user-provided or user-confirmed reply route to the decision maker or an accountable relay agent, and show the complete draft including that route. Before calling, provide https://relux.works/en/privacy-policy/ and obtain explicit user consent. Never invent or infer contact details. The current MCP chat is not a reply route. A human replies within one business day with a recommended package and a fixed-price quote.

Input parameters:

- `budget_usd` (number): Approximate budget in USD, if known
- `client_name` (string): Name of the person or company
- `consent_confirmed` (boolean, required): Set to true only after the user has reviewed the complete inquiry and reply route, received the privacy notice URL, and explicitly approved submission to Relux Works.
- `contact_email` (string): Real, reachable decision-maker email provided or explicitly confirmed by the user. Never invent or infer it. Legacy shorthand for reply_contact with channel=email and recipient=decision_maker. Reserv…
- `market` (string): Client market or country code
- `preferred_language` (string): Language preferred for the human reply
- `project_type` (string): Closest project category
- `reply_contact` (object): External route provided or explicitly confirmed by the user that a Relux Works human can use to reach the decision maker or a relay agent. Never invent or infer it. The current MCP session, chat, or…
- `summary` (string, required): What the user wants to build or fix, current state, goals (required)
- `timeline` (string): Desired timeline or deadline

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/works-relux-agent-gateway/api#diagnostics

## Score history

- 2026-08-03: 59
- 2026-08-02: 59
- 2026-08-01: 59
- 2026-07-31: 59
- 2026-07-30: 59
- 2026-07-29: 59
- 2026-07-28: 59
- 2026-07-27: 64
- 2026-07-26: 63

## Links

- Remote endpoint: https://api.relux.works/mcp
- Website: https://relux.works/
- Changelog RSS feed: https://verifymcp.io/servers/works-relux-agent-gateway/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/works-relux-agent-gateway/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/works-relux-agent-gateway/api