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.

Clipwright

REMOTE · CLIPWRIGHT.ELITEAIEMPIRE.COM

Automated long-form-to-shorts clipping with a rights gate that refuses unlicensed footage. Own conte

+3 this week 75 Trust /100

Last scanned (15 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Design and Media

Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security83
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 850 tokens (~65/item across 13 items; 13 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage76
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 29% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 −2
    • HSTS header: pass → fail ▼ security
    • Tool “get_checkout_link” rewrote its description, which is the text the model reads security
    • Tool “list_pricing” rewrote its description, which is the text the model reads security
    • Schema quality: 53 → 65 ▼ functional
    • Tool coverage: 14% → 29% ▲ functional
    • “get_checkout_link” added an optional parameter “accept_terms” cosmetic
    • “get_checkout_link” added an optional parameter “buyer_email” cosmetic
    • “get_checkout_link” added an optional parameter “interval” cosmetic
    • “get_checkout_link” added an optional parameter “store_handle” cosmetic
    • “get_checkout_link” reworded the description of “plan” cosmetic
    • “get_checkout_link” dropped the optional parameter “period” cosmetic
    • Tool “get_checkout_link” changed its title: Checkout link cosmetic
    • Tool “list_pricing” changed its title: Pricing cosmetic
  • 16 Nov 26 +3
    • HSTS header: fail → pass ▲ security
    • Tool “get_checkout_link” rewrote its description, which is the text the model reads security
    • Tool “get_company_info” rewrote its description, which is the text the model reads security
    • Tool “list_pricing” rewrote its description, which is the text the model reads security
    • Tool “search_site” rewrote its description, which is the text the model reads security
    • Tool coverage: 23% → 14% ▼ functional
    • “get_checkout_link” added an optional parameter “period” cosmetic
    • “get_checkout_link” reworded the description of “plan” cosmetic
    • “search_site” reworded the description of “query” cosmetic
    • “get_checkout_link” dropped the optional parameter “interval” cosmetic
    • “search_site” dropped the optional parameter “limit” cosmetic
    • “search_site” made “query” optional cosmetic
    • Tool “get_checkout_link” changed its title: Checkout link cosmetic
    • Tool “get_company_info” changed its title: Company info cosmetic
    • Tool “list_pricing” changed its title: Pricing cosmetic
    • Tool “search_site” changed its title: Search this site cosmetic
  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 −2
    • HSTS header: pass → fail ▼ security
    • Tool coverage: 17% → 23% ▲ functional
    • Schema quality: 61 → 54 ▲ functional
    • New tool “get_checkout_link” functional
    • New tool “get_company_info” functional
    • New tool “list_pricing” functional
    • New tool “search_site” functional
  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
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 21 Nov 2026 · Probed https://clipwright.eliteaiempire.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=eliteaiempire.com CN=YE1,O=Let's Encrypt,C=US 6 Oct 2026 4 Jan 2027 ECDSA 256 ECDSA-SHA384 517249ed134f0bde704a0af855a2b2bb62e
SANs: *.eliteaiempire.com, eliteaiempire.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of clipwright.eliteaiempire.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
eliteaiempire.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

Protected resource metadata

Retrieved No
Problem No resource metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://clipwright.eliteaiempire.com/mcp Verified 200
http (plaintext) http://clipwright.eliteaiempire.com/mcp HTTPS enforced 302 https://clipwright.eliteaiempire.com/mcp
MCP tools · 13 exposed · ~850 tokens

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 →

Tool Tokens
clipwright_check_rights ~52

Ask the rights gate whether a source may be clipped. Returns ALLOW or REFUSE with the reason. Deny-by-default.

NameTypeReqDescription
grant_idstring––
sourcestringyes–

No output schema declared.

No examples provided.

clipwright_create_clips ~92

Create vertical 9:16 captioned clips from a source. Refuses with 403 unless a rights grant covers the source. Requires confirm=true.

NameTypeReqDescription
confirmbooleanyesMust be true. This tool writes records and consumes monthly source-video quota; the call is refused without it.
grant_idstring––
sourcestringyes–
top_ninteger––

No output schema declared.

No examples provided.

clipwright_export_data ~31

Export everything stored for this key (jobs with clip metadata, rights grants, schedule intents) as JSON.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

clipwright_get_usage ~30

Read this key's plan, monthly source-video usage against the limit, and metered call counts.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

clipwright_job_status ~28

Fetch a clip job's status and rendered clips.

NameTypeReqDescription
job_idstringyes–

No output schema declared.

No examples provided.

clipwright_list_programs ~36

List the opt-in clipper programmes Clipwright can legally clip for (the rights holder grants the licence in the campaign brief).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

clipwright_register_grant ~95

Register a rights grant: kind is one of owned | program_brief | licence_file | open_licence. Verified by execution at registration. Requires confirm=true.

NameTypeReqDescription
confirmbooleanyesMust be true. This tool writes records; the call is refused without it.
expires_tsstring––
kindstringyes–
payloadobjectyes–
scopeobjectyes–

No output schema declared.

No examples provided.

clipwright_schedule ~82

Record a publish intent for the Empire Distributor. Publishes nothing (no platform token exists); returns publish_state NOT_PUBLISHED. Requires confirm=true.

NameTypeReqDescription
confirmbooleanyesMust be true. This tool writes records; the call is refused without it.
job_idstringyes–
platformsarray––
whenstring––

No output schema declared.

No examples provided.

clipwright_tiktok_post_draft ~103

F6015/S3: DRAFT ONLY. Returns the same creator_info (nickname, privacy options, interaction/duration limits) a human sees on the compliant per-post TikTok screen. NEVER posts -- there is no tool that does; posting requires an explicit human click on the dashboard, one post at a time, even once the app passes TikTok's audit.

NameTypeReqDescription
clip_idxinteger––
job_idstring––

No output schema declared.

No examples provided.

get_checkout_link ~206

Checkout URL for a plan. With no arguments: the main paid plan. Where the site supports it the URL is a Stripe-hosted Checkout session (created unpaid; a human pays, nothing is charged by this tool). A free plan is only returned when the plan is requested or the company sells nothing else.

NameTypeReqDescription
accept_termsboolean–ONLY where the site requires the buyer to accept its Terms/refund policy before checkout: set true only after the human buyer has read and accepted the policy links the tool lists. Never set it on yo…
buyer_emailstring–only for sites that need the buyer's email or store handle before checkout: the human buyer's own receipt email
intervalstring––
planstring–plan name from list_pricing
store_handlestring–only where the site asks for it (StoreForge): the store handle the buyer chose, 3+ chars a-z 0-9 -

No output schema declared.

No examples provided.

get_company_info ~31

Who runs Clipwright, what it sells, contact details and policy links. Read-only, no key needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_pricing ~34

Current plans and prices in USD: plan, interval, amount_usd, currency, what_you_get. No account needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_site ~30

Search Clipwright pages by keyword; returns title, URL and a snippet.

NameTypeReqDescription
querystring––

No output schema declared.

No examples provided.

Install

How do I install the Clipwright MCP server?

Clipwright is a hosted endpoint at https://clipwright.eliteaiempire.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 · clipwright.eliteaiempire.com

# add to Claude Code
claude mcp add --transport http com-eliteaiempire-clipwright 'https://clipwright.eliteaiempire.com/mcp'
Common questions

What is the Clipwright MCP server?

Clipwright is an MCP server listed in the public MCP registry as com.eliteaiempire/clipwright. Automated long-form-to-shorts clipping with a rights gate that refuses unlicensed footage. Own conte. This page covers its hosted endpoint (https://clipwright.eliteaiempire.com/mcp).

Is the Clipwright MCP server safe to use?

Clipwright scores 75 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 Clipwright MCP server expose?

Clipwright exposes 13 tools: clipwright_list_programs, clipwright_check_rights, clipwright_register_grant, clipwright_create_clips, clipwright_job_status, and 8 more. Their descriptions and schemas cost roughly 850 tokens of context every time the server is loaded.

Does the Clipwright MCP server require authentication?

Yes. Clipwright 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 Clipwright MCP server still maintained?

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

What did VerifyMCP test on the Clipwright MCP server?

VerifyMCP ran 13 checks on Clipwright, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.