Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

UnrealUGC

REMOTE · UNREALUGC.COM · 2 COMPONENTS · SCANNED AUG 22

Generate and manage AI UGC video ads through eleven typed MCP tools

25 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security63
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 4 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.

Install

How do I install the UnrealUGC MCP server?

UnrealUGC is a hosted endpoint at https://unrealugc.com/api/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 · unrealugc.com

# add to Claude Code
claude mcp add --transport http com-unrealugc-mcp 'https://unrealugc.com/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-unrealugc-mcp": {
      "url": "https://unrealugc.com/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-unrealugc-mcp": {
      "type": "http",
      "url": "https://unrealugc.com/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-unrealugc-mcp]
url = "https://unrealugc.com/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-unrealugc-mcp": {
      "type": "remote",
      "url": "https://unrealugc.com/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-unrealugc-mcp --url 'https://unrealugc.com/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-unrealugc-mcp:
    url: "https://unrealugc.com/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-unrealugc-mcp": {
      "Transport": "http",
      "Url": "https://unrealugc.com/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-unrealugc-mcp -t streamable-http -u 'https://unrealugc.com/api/mcp'
// mcp.json
{
  "mcpServers": {
    "com-unrealugc-mcp": {
      "type": "http",
      "url": "https://unrealugc.com/api/mcp"
    }
  }
}

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

Changelog

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.

  • 18 Aug 26 25

    First indexed and scored.

Diagnostics

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 22 Aug 2026 · Probed https://unrealugc.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=unrealugc.com CN=YR2,O=Let's Encrypt,C=US 2 Jul 2026 30 Sept 2026 RSA 2048 SHA256-RSA 536610596568b4b93999aa4e1464ebdd3da
SANs: unrealugc.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f
DNSSEC insecure

Validation of unrealugc.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
unrealugc.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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=63072000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(self), microphone=(self), geolocation=()
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://unrealugc.com/api/mcp Not MCP 200
http (plaintext) http://unrealugc.com/api/mcp HTTPS enforced 308 https://unrealugc.com/api/mcp
MCP tools

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.

No tool schema has been captured from this endpoint yet.

Common questions

What is the UnrealUGC MCP server?

UnrealUGC is an MCP server listed in the public MCP registry as com.unrealugc/mcp. Generate and manage AI UGC video ads through eleven typed MCP tools. This page covers its hosted endpoint (https://unrealugc.com/api/mcp).

Is the UnrealUGC MCP server safe to use?

UnrealUGC scores 25 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.

Does the UnrealUGC MCP server require authentication?

No. We connected to UnrealUGC without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the UnrealUGC MCP server still maintained?

UnrealUGC is still listed as active in the MCP registry. We last reached this channel on 22 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.