io.github.runcomfy-com/runcomfy-mcp
REMOTE · MCP.RUNCOMFY.COM · SCANNED OCT 4
Remote MCP for RunComfy: ComfyUI deployments, hosted models, LoRA training. 31 tools.
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 Security89
- 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 offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
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.
How do I install the io.github.runcomfy-com/runcomfy-mcp server?
io.github.runcomfy-com/runcomfy-mcp is a hosted endpoint at https://mcp.runcomfy.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.runcomfy.com
claude mcp add --transport http runcomfy-com-runcomfy-mcp 'https://mcp.runcomfy.com/mcp'
{
"mcpServers": {
"runcomfy-com-runcomfy-mcp": {
"url": "https://mcp.runcomfy.com/mcp"
}
}
} {
"servers": {
"runcomfy-com-runcomfy-mcp": {
"type": "http",
"url": "https://mcp.runcomfy.com/mcp"
}
}
} [mcp_servers.runcomfy-com-runcomfy-mcp] url = "https://mcp.runcomfy.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"runcomfy-com-runcomfy-mcp": {
"type": "remote",
"url": "https://mcp.runcomfy.com/mcp",
"enabled": true
}
}
} openclaw mcp add runcomfy-com-runcomfy-mcp --url 'https://mcp.runcomfy.com/mcp' --transport streamable-http
mcp_servers:
runcomfy-com-runcomfy-mcp:
url: "https://mcp.runcomfy.com/mcp" {
"McpServers": {
"runcomfy-com-runcomfy-mcp": {
"Transport": "http",
"Url": "https://mcp.runcomfy.com/mcp"
}
}
} assistant mcp add runcomfy-com-runcomfy-mcp -t streamable-http -u 'https://mcp.runcomfy.com/mcp'
{
"mcpServers": {
"runcomfy-com-runcomfy-mcp": {
"type": "http",
"url": "https://mcp.runcomfy.com/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.
- 28 Sept 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
- 25 Sept 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 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
- 24 Aug 26 0
- Endpoint reachability: unreachable → behind authorisation ▼ security
- HSTS header: unverified → fail ▼ security
- Transport: fail → unverified ▼ security
- Authorization: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
- 23 Aug 26 0
- Endpoint reachability: behind authorisation → unreachable ▼ security
- Transport: unverified → fail ▼ security
- HSTS header: fail → unverified ▼ security
- Authorization: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. functional
- Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
- 13 Aug 26 0
- Endpoint reachability: not serving MCP → behind authorisation ▼ security
- Transport: fail → unverified ▼ security
- Authorization: unverified → pass ▲ security
- First check of Authorization: partial security
- Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
- 12 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.53 → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified 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
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 6 Oct 2026 · Probed https://mcp.runcomfy.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=runcomfy.com | CN=WE1,O=Google Trust Services,C=US | 12 Aug 2026 | 10 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | c4d603d4e7ff7ca113c1fc3ddac64ab0 |
| SANs: runcomfy.com, mcp.runcomfy.com, *.mcp.runcomfy.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.runcomfy.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| runcomfy.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 realm="OAuth", resource_metadata="https://mcp.runcomfy.com/.well-known/oauth-protected-resource/mcp", scope="mcp:tools"
Bearer realm="OAuth", resource_metadata="https://mcp.runcomfy.com/.well-known/oauth-protected-resource/mcp", scope="mcp:tools"| Header | Value |
|---|---|
| www-authenticate | Bearer realm="OAuth", resource_metadata="https://mcp.runcomfy.com/.well-known/oauth-protected-resource/mcp", scope="mcp:tools" |
Protected resource metadata
| Document | https://mcp.runcomfy.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.runcomfy.com/mcp |
| Authorisation server | https://mcp.runcomfy.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.runcomfy.com/mcp | Auth required | 401 | |
| http (plaintext) | http://mcp.runcomfy.com/mcp | HTTPS enforced | 301 | https://mcp.runcomfy.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 →
call_instance_proxy ~125
Call a ComfyUI backend endpoint on a live instance. Backs ``POST /prod/v2/deployments/{deployment_id}/instances/{instance_id}/proxy/{path}``. Get the instance_id from ``get_request_status`` once the status is ``in_progress``. Common target: ``api/free`` with ``{"unload_models": true}`` to free GPU memory.
| Name | Type | Req | Description |
|---|---|---|---|
| comfy_backend_path | string | yes | – |
| deployment_id | string | yes | – |
| instance_id | string | yes | – |
| request_body | – | – | – |
No output schema declared.
No examples provided.
cancel_request ~74
Cancel a queued or running request. Backs ``POST /prod/v1/deployments/{deployment_id}/requests/{request_id}/cancel``. Returns ``cancelled`` if accepted, ``not_cancellable`` if already done.
| Name | Type | Req | Description |
|---|---|---|---|
| deployment_id | string | yes | – |
| request_id | string | yes | – |
No output schema declared.
No examples provided.
create_deployment ~259
Create a Serverless API (ComfyUI) deployment. Backs ``POST /prod/v2/deployments``. For LoRA deployments, create via the runcomfy.com UI instead. Args: name: Human-readable name. workflow_id: UUID of the ComfyUI workflow. workflow_version: Version label, e.g. "v1". hardware: One of TURING_16, AMPERE_24, AMPERE_48, ADA_48_PLUS, AMPERE_80, ADA_80_PLUS, HOPPER_141. min_instances: 0..30. Warm instance floor (billable if > 0). max_instances: 1..60. Concurrency ceiling. queue_size: >= 0. Pending requests before scaling up. keep_warm_duration_in_seconds: >= 0. Idle timeout.
| Name | Type | Req | Description |
|---|---|---|---|
| hardware | string | – | – |
| keep_warm_duration_in_seconds | integer | – | – |
| max_instances | integer | – | – |
| min_instances | integer | – | – |
| name | string | yes | – |
| queue_size | integer | – | – |
| workflow_id | string | yes | – |
| workflow_version | string | yes | – |
No output schema declared.
No examples provided.
delete_deployment ~64
Permanently delete a deployment. Backs ``DELETE /prod/v2/deployments/{deployment_id}``. This cannot be undone. Consider ``update_deployment(is_enabled=false)`` to pause instead.
| Name | Type | Req | Description |
|---|---|---|---|
| deployment_id | string | yes | – |
No output schema declared.
No examples provided.
get_deployment ~102
Get one deployment by ID. Backs ``GET /prod/v2/deployments/{deployment_id}``. Set include_payload=true to inspect the deployed workflow graph (workflow_api_json) and default overrides — use the node IDs and input names to build the ``overrides`` for ``submit_request``.
| Name | Type | Req | Description |
|---|---|---|---|
| deployment_id | string | yes | – |
| include_payload | boolean | – | – |
| include_readme | boolean | – | – |
No output schema declared.
No examples provided.
get_request_result ~67
Fetch a completed request's outputs. Backs ``GET /prod/v1/deployments/{deployment_id}/requests/{request_id}/result``. Output URLs are hosted for 7 days.
| Name | Type | Req | Description |
|---|---|---|---|
| deployment_id | string | yes | – |
| request_id | string | yes | – |
No output schema declared.
No examples provided.
get_request_status ~79
Poll a request's current status. Backs ``GET /prod/v1/deployments/{deployment_id}/requests/{request_id}/status``. Lifecycle: ``in_queue`` → ``in_progress`` → ``completed`` / ``cancelled``.
| Name | Type | Req | Description |
|---|---|---|---|
| deployment_id | string | yes | – |
| request_id | string | yes | – |
No output schema declared.
No examples provided.
list_deployments ~108
List Serverless API deployments in the caller's account. Backs ``GET /prod/v2/deployments``. Args: ids: Optional list of deployment IDs to filter to. include_payload: Include workflow_api_json, overrides, and object_info_url for each deployment. Larger response. include_readme: Include the deployment's README markdown.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | – | – | – |
| include_payload | boolean | – | – |
| include_readme | boolean | – | – |
No output schema declared.
No examples provided.
submit_request ~349
Submit an async inference request to a deployment. Backs ``POST /prod/v1/deployments/{deployment_id}/inference``. Args: deployment_id: Target deployment. overrides: Partial graph keyed by node_id, e.g. ``{"6": {"inputs": {"text": "a cat"}}}``. Use ``get_deployment(include_payload=true)`` to discover node IDs and input names. workflow_api_json: Advanced — run a different workflow without updating the deployment. Omit ``overrides`` in this mode. extra_data: E.g. ``{"api_key_comfy_org": "comfyui-..."}`` for ComfyUI Core API nodes. webhook_url: Push-based updates instead of polling. webhook_intermediate_status: Fire webhooks on every status change, not just terminal. wait_for_completion: If true, poll until done and return the result inline. timeout_seconds: Max wait when wait_for_completion=true. File inputs: pass a public HTTPS URL or Base64 data URI directly in the overrides value, e.g. ``{"189": {"inputs": {"image": "https://example.com/photo.jpg"}}}`` or ``{"189": {"inputs": {"image": "data:image/jpeg;base64,/9j..."}}}``.
| Name | Type | Req | Description |
|---|---|---|---|
| deployment_id | string | yes | – |
| extra_data | – | – | – |
| overrides | – | – | – |
| timeout_seconds | integer | – | – |
| wait_for_completion | boolean | – | – |
| webhook_intermediate_status | – | – | – |
| webhook_url | – | – | – |
| workflow_api_json | – | – | – |
No output schema declared.
No examples provided.
update_deployment ~115
Partially update a deployment. Backs ``PATCH /prod/v2/deployments/{deployment_id}``. Only pass the fields you want to change. Set is_enabled=false to pause; true to re-enable.
| Name | Type | Req | Description |
|---|---|---|---|
| deployment_id | string | yes | – |
| hardware | – | – | – |
| is_enabled | – | – | – |
| keep_warm_duration_in_seconds | – | – | – |
| max_instances | – | – | – |
| min_instances | – | – | – |
| name | – | – | – |
| queue_size | – | – | – |
| workflow_version | – | – | – |
No output schema declared.
No examples provided.
What is the io.github.runcomfy-com/runcomfy-mcp server?
io.github.runcomfy-com/runcomfy-mcp is listed in the public MCP registry as io.github.runcomfy-com/runcomfy-mcp. Remote MCP for RunComfy: ComfyUI deployments, hosted models, LoRA training. 31 tools. This page covers its hosted endpoint (https://mcp.runcomfy.com/mcp).
Is the io.github.runcomfy-com/runcomfy-mcp server safe to use?
io.github.runcomfy-com/runcomfy-mcp scores 36 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 io.github.runcomfy-com/runcomfy-mcp server expose?
io.github.runcomfy-com/runcomfy-mcp exposes 10 tools: list_deployments, get_deployment, create_deployment, update_deployment, delete_deployment, and 5 more. Their descriptions and schemas cost roughly 1,342 tokens of context every time the server is loaded.
Does the io.github.runcomfy-com/runcomfy-mcp server require authentication?
Yes. io.github.runcomfy-com/runcomfy-mcp 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 io.github.runcomfy-com/runcomfy-mcp server still maintained?
io.github.runcomfy-com/runcomfy-mcp is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.