works.relux/agent-gateway
REMOTE · API.RELUX.WORKS · SCANNED SEP 24
Relux Works studio gateway: read services/pricing and submit a project inquiry to hire the team.
Available components
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. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (request_project_quote). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the works.relux/agent-gateway MCP server?
works.relux/agent-gateway is a hosted endpoint at https://api.relux.works/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.relux.works
claude mcp add --transport http works-relux-agent-gateway 'https://api.relux.works/mcp'
{
"mcpServers": {
"works-relux-agent-gateway": {
"url": "https://api.relux.works/mcp"
}
}
} {
"servers": {
"works-relux-agent-gateway": {
"type": "http",
"url": "https://api.relux.works/mcp"
}
}
} [mcp_servers.works-relux-agent-gateway] url = "https://api.relux.works/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"works-relux-agent-gateway": {
"type": "remote",
"url": "https://api.relux.works/mcp",
"enabled": true
}
}
} openclaw mcp add works-relux-agent-gateway --url 'https://api.relux.works/mcp' --transport streamable-http
mcp_servers:
works-relux-agent-gateway:
url: "https://api.relux.works/mcp" {
"McpServers": {
"works-relux-agent-gateway": {
"Transport": "http",
"Url": "https://api.relux.works/mcp"
}
}
} assistant mcp add works-relux-agent-gateway -t streamable-http -u 'https://api.relux.works/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 27 Aug 26 +3
- Stability: fail → pass ▲ security
- 26 Aug 26 75
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 0
- Stability: 0.03 → fail ▼ security
- Schema quality: 232 → 383 ▼ functional
- Schema quality: excellent → good functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://api.relux.works/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=relux.works | CN=WE1,O=Google Trust Services,C=US | 3 Sept 2026 | 2 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6bfa0707d690abdb0e919100247eff1a |
| SANs: relux.works, api.relux.works, *.api.relux.works | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.relux.works. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| works. | present | 46672 | 8 | Verified |
| relux.works. | present | 2371 | 13 | Verified |
| api.relux.works. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.relux.works/mcp | Verified | 200 | |
| http (plaintext) | http://api.relux.works/mcp | HTTPS enforced | 301 | https://api.relux.works/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_services_pricing Get services and pricing ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
request_project_quote Request a project quote ~385
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.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_usd | number | – | Approximate budget in USD, if known |
| client_name | string | – | Name of the person or company |
| consent_confirmed | boolean | yes | 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 | yes | What the user wants to build or fix, current state, goals (required) |
| timeline | string | – | Desired timeline or deadline |
No output schema declared.
No examples provided.
What is the works.relux/agent-gateway MCP server?
works.relux/agent-gateway is an MCP server listed in the public MCP registry as works.relux/agent-gateway. Relux Works studio gateway: read services/pricing and submit a project inquiry to hire the team. This page covers its hosted endpoint (https://api.relux.works/mcp).
Is the works.relux/agent-gateway MCP server safe to use?
works.relux/agent-gateway scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the works.relux/agent-gateway MCP server expose?
works.relux/agent-gateway exposes 2 tools: get_services_pricing, request_project_quote. Their descriptions and schemas cost roughly 508 tokens of context every time the server is loaded.
Does the works.relux/agent-gateway MCP server require authentication?
No. We connected to works.relux/agent-gateway without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the works.relux/agent-gateway MCP server still maintained?
works.relux/agent-gateway is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.