Relay
REMOTE · MCP.RELAYGPU.COM · 2 COMPONENTS
Run any Relay model (image, video, audio, LLM), poll tasks, upload files and search Relay's docs.
Available components
Last scanned (10 hours ago)
Scores higher than 26% of remote servers
Reachable. Last reached 5 Nov 2026.
Category AI and Machine Learning
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 Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 15 Oct 26 −30
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- Transport: pass → unverified ▼ security
- HSTS header: pass → fail ▼ security
- Authorization: fail → pass ▲ security
- First check of Authorization: pass security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 66
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 5 Nov 2026 · Probed https://mcp.relaygpu.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=relaygpu.com | CN=WE1,O=Google Trust Services,C=US | 23 Sept 2026 | 22 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 9f041b0de3623d3713cdc5e0269c772a |
| SANs: relaygpu.com, *.relaygpu.com | ||||||
| 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 insecure
Validation of mcp.relaygpu.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| relaygpu.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.relaygpu.com/.well-known/oauth-protected-resource", scope="relay"
Bearer resource_metadata="https://mcp.relaygpu.com/.well-known/oauth-protected-resource", scope="relay"| Header | Value |
|---|---|
| www-authenticate | Bearer resource_metadata="https://mcp.relaygpu.com/.well-known/oauth-protected-resource", scope="relay" |
Protected resource metadata
| Document | https://mcp.relaygpu.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.relaygpu.com/mcp |
| Authorisation server | https://relaygpu.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.relaygpu.com/mcp | Auth required | 401 | |
| http (plaintext) | http://mcp.relaygpu.com/mcp | HTTPS enforced | 301 | https://mcp.relaygpu.com/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 →
cancel_workflow_run Cancel a workflow run ~71
Cancel a workflow run. Cancels between steps only: a step already running completes and bills. A run that has already ended answers WORKFLOW_RUN_NOT_CANCELLABLE. Needs a Relay credential.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | The run id returned by run_workflow (`wf:…`). |
No output schema declared.
No examples provided.
check_task Check a Relay task ~148
Checks a task run_model returned (no key needed: the task_id is the capability). Waits up to 30 s for it to finish; returns the result when completed, else its status: then call check_task again, never resubmit. Task results are kept 1 h after they finish.
| Name | Type | Req | Description |
|---|---|---|---|
| inline_images | boolean | – | Also return images ≤ 1 MB as image content blocks (default false: links only). |
| task_id | string | yes | The task_id from run_model, e.g. direct:2f9c… |
| wait_seconds | integer | – | Seconds to wait for it to finish (0–30, default 30); 0 just reads the status. |
No output schema declared.
No examples provided.
check_workflow_run Check a workflow run ~126
Poll a workflow run by run_id, waiting up to wait_seconds (≤ 30) for it to end. Completed → the final output; failed / cancelled → the error; still running → its steps so far: call check_workflow_run again. No key needed: the run_id is the access token.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | The run id returned by run_workflow (`wf:…`). |
| wait_seconds | integer | – | Seconds to wait for it to finish (0–30, default 30); 0 answers the current state at once. |
No output schema declared.
No examples provided.
estimate_cost Estimate a Relay cost ~179
Estimates the USD cost of a call from the public price list: an estimate, not an invoice (the bill uses provider-reported usage and any custom pricing on your account). Pass only the usage fields the model's billing_type (see get_model or get_pricing) reads: per_token: input_tokens, output_tokens, cached_input_tokens; per_image: image_count, resolution_tier; per_second_video: duration_seconds, quality_mode, sound; per_second_audio: duration_seconds; per_character: character_count; per_media_token: media_input_tokens, media_output_tokens. Add store_output / retention / file_count for storage fees.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | yes | Exact model name, e.g. KlingTeam/v3-T2V. |
| usage | object | yes | What the call uses; only the fields of the model's billing type matter. |
No output schema declared.
No examples provided.
get_credits Get credit balance ~50
Read the account's credit balance, active promo credits and consumption. Needs a dashboard JWT or a custom-tier superkey; a plain inference key gets PERMISSION_DENIED (403). Needs a Relay credential.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_model Get a Relay model ~66
Returns one model's route, request_schema (what run_model's input must follow), request_example, pricing and availability. Then call run_model with an input shaped like request_example.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | yes | Exact model name from search_models, e.g. Qwen/qwen-image. |
No output schema declared.
No examples provided.
get_pricing Get Relay pricing ~88
Returns Relay's public list prices (USD), optionally for one model, plus media_storage: the per-file fees of the store_output / upload retention SKUs (relay1d, relay7d, …). Then estimate_cost for a number.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | – | Model name (e.g. Qwen/qwen-image) to keep only its rows. Omit for every model. |
No output schema declared.
No examples provided.
get_usage Get usage ~140
Read the account's usage and spend per API key. Pass period (e.g. 7d) for a by-date breakdown, or from + to. Needs a dashboard JWT or a custom-tier superkey; a plain inference key gets PERMISSION_DENIED (403). Needs a Relay credential.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Start date `YYYY-MM-DD`; use together with `to`. |
| period | string | – | Time period shorthand, e.g. `7d` or `30d` (max 30 days); adds a by-date breakdown. |
| to | string | – | End date `YYYY-MM-DD`; use together with `from`. |
No output schema declared.
No examples provided.
list_workflows List workflows ~61
List Relay's workflow templates: multi-step pipelines (e.g. script → voiceover) run as one call. Each entry has workflow_id, input_schema and its steps (step_id + model). Run one with run_workflow; inputs follow input_schema.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_model Run a Relay model ~296
Runs any Relay model by name (billed to your key). input follows get_model's request_schema (request_example runs as is). Waits up to 45 s; past that it returns a task_id — do not resubmit, call check_task. Result links expire 1 h after completion unless store_output names a media_storage SKU from get_pricing. Pass an idempotency_key if you may retry the same submit. Needs a Relay credential.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | Your key for this submit: a retry with the same key replays the first task instead of starting (and billing) a new one. |
| inline_images | boolean | – | Also return images ≤ 1 MB as image content blocks (default false: links only). |
| input | object | yes | Request body per get_model's request_schema, without model (added for you). Pass media as *_url links (upload_file makes one). |
| model | string | yes | Exact model name from search_models / get_model, e.g. Qwen/qwen-image. |
| store_output | string | – | Keep result media longer: a media_storage SKU from get_pricing (e.g. relay7d, adds its per-file fee), or provider (default, 1 h). |
| wait_seconds | integer | – | Seconds to wait for it to finish (0–45, default 45); 0 returns the task_id at once. |
No output schema declared.
No examples provided.
run_workflow Run a workflow ~298
Start a workflow run (one submit) and wait up to wait_seconds (≤ 45) for it to finish. Completed → the final output; still running → run_id: call check_workflow_run with it, never resubmit (a new run bills again). Each step is billed as an ordinary request. webhook_url gets ONE signed workflow.completed / workflow.failed delivery when the run ends. Get workflow_id and the inputs shape from list_workflows. Needs a Relay credential.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | Idempotency-Key for the submit: the same key and inputs within 24 h return the same run_id instead of a new run. Generated when omitted. |
| inputs | object | yes | Template inputs, an object matching the workflow's input_schema. |
| store_output | string | – | Run-level storage for every media step: `provider` (default, 1 h link) or `relay1d` / `relay7d` / `relay30d` (billed per file, see get_pricing). |
| wait_seconds | integer | – | Seconds to wait for it to finish (0–45, default 45); 0 returns the run_id at once. |
| webhook_url | string | – | HTTPS URL for one signed workflow.completed / workflow.failed delivery when the run ends. |
| workflow_id | string | yes | Workflow template id from list_workflows, e.g. `script-voiceover`. |
No output schema declared.
No examples provided.
search_docs Search the Relay docs ~126
Search Relay's public docs (bundled, offline) for how-to, auth, errors, limits, retries, webhooks, files and pricing rules. Returns the best-matching sections: page, heading, docs path with anchor and an excerpt. For a model's input fields use get_model instead; to find a model use search_models.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many sections to return (1–10, default 5). |
| query | string | yes | What to look for, in plain words, e.g. `idempotency key` or `file retention`. |
No output schema declared.
No examples provided.
search_models Search Relay models ~147
Lists Relay models by tag and/or text. Common tags: text-to-image, image-to-image, text-to-video, image-to-video, video-to-video, text-to-speech, speech-to-text, text-to-text, text-to-embedding. Returns name, tag and route per model (at most 50). Then call get_model with a name for its input schema.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Words to match, case-insensitive; every word must appear in the name, display name or tag (e.g. 'kling v3'). |
| tag | string | – | Model type tag, e.g. text-to-image or image-to-video. Omit for every tag. |
No output schema declared.
No examples provided.
upload_file Upload a file to Relay ~233
Hosts an image, video or audio file on Relay and returns its url: pass that url to any *_url input of run_model. Give exactly one of path (local server only, ≤ 100 MB), base64 (≤ 4 MB) or url (a public link Relay copies). retention: relay1h (default, free within a daily quota) or a media_storage SKU from get_pricing. Needs a Relay credential.
| Name | Type | Req | Description |
|---|---|---|---|
| base64 | string | – | File content as base64 or a data: URI, at most 4 MB decoded. Larger files: pass url. |
| filename | string | – | File name to record (defaults to the path's base name). |
| path | string | – | Local file path (stdio server only; the hosted server cannot read your disk). Max 100 MB. |
| retention | string | – | How long the link lives: relay1h (default, free within a daily quota) or a media_storage SKU from get_pricing (relay1d, relay7d, …). |
| url | string | – | Public http(s) link to copy onto Relay. |
No output schema declared.
No examples provided.
How do I install the Relay MCP server?
Relay is a hosted endpoint at https://mcp.relaygpu.com/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 · mcp.relaygpu.com
claude mcp add --transport http com-relaygpu-mcp 'https://mcp.relaygpu.com/mcp'
What is the Relay MCP server?
Relay is an MCP server listed in the public MCP registry as com.relaygpu/mcp. Run any Relay model (image, video, audio, LLM), poll tasks, upload files and search Relay's docs. This page covers its hosted endpoint (https://mcp.relaygpu.com/mcp).
Is the Relay MCP server safe to use?
Relay scores 37 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 Relay MCP server expose?
Relay exposes 14 tools: search_models, get_model, get_pricing, estimate_cost, run_model, and 9 more. Their descriptions and schemas cost roughly 2,029 tokens of context every time the server is loaded.
Does the Relay MCP server require authentication?
Yes. Relay asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Relay MCP server still maintained?
Relay is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.