CLIPCLIPER
REMOTE · CLIPCLIPER.COM
Timestamped transcripts, chapters and clip suggestions from YouTube, Twitch, Kick or TikTok links.
Available components
Last scanned (25 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 30 Sep 2026.
Category Entertainment and Games
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.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, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 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.
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.
- 10 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 7 Oct 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 6 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 4 Oct 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 3 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 1 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.40 → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 29 Sept 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.
- 28 Sept 26 +7
- 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 10 Oct 2026 · Probed https://clipcliper.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=clipcliper.com | CN=WE1,O=Google Trust Services,C=US | 30 Aug 2026 | 28 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 7c413ccedd55a54513c0cf9bd4bcbd1a |
| SANs: clipcliper.com, *.clipcliper.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 clipcliper.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| clipcliper.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://clipcliper.com/mcp | Unreachable | ||
| http (plaintext) | http://clipcliper.com/mcp | HTTPS enforced |
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_chapters Get chapters ~199
Split a public video into topic chapters (start/end seconds, title, one-line summary) from its transcript. Transcribes the video first if needed (same cost and async behaviour as get_transcript); the chapters themselves are free and cached.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Spoken language of the video as ISO-639-1 (e.g. 'en', 'es'). Omit to auto-detect. |
| max_chapters | integer | – | Upper bound of chapters (default 12). |
| output_language | string | – | Language for titles and summaries (ISO-639-1). Default: the language of the video. |
| url | string | yes | Public video URL: YouTube video/short/live replay, Twitch VOD, Kick VOD or TikTok video. |
| wait_seconds | integer | – | Seconds to wait for processing before returning status 'processing' (default 90). Long videos can take several minutes: just call again. |
No output schema declared.
No examples provided.
get_transcript Get transcript ~303
Download a public video (YouTube, Twitch VOD, Kick VOD, TikTok) and return its full transcript with timestamps (Whisper large-v3). Asynchronous: if it returns status 'processing', call again with the same url. Results are cached 24 h per url. With a license key it costs one pack minute per started minute of video (minute packs at https://clipcliper.com/mcp; desktop hour packs cost one hour per started hour); without a key, videos up to 15 min (daily limit per IP).
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | 'timestamped' (default, one line per segment: [m:ss] text), 'text' (plain), 'srt' (subtitles) or 'segments' (JSON array of {start,end,text}). |
| language | string | – | Spoken language of the video as ISO-639-1 (e.g. 'en', 'es'). Omit to auto-detect. |
| max_chars | integer | – | Truncate the transcript to this many characters (default 150000). A 1 h talk is ~50000 chars. |
| url | string | yes | Public video URL: YouTube video/short/live replay, Twitch VOD, Kick VOD or TikTok video. |
| wait_seconds | integer | – | Seconds to wait for processing before returning status 'processing' (default 90). Long videos can take several minutes: just call again. |
No output schema declared.
No examples provided.
suggest_clips Suggest clips ~287
Find the most shareable moments of a public video for short-form clips: start/end seconds aligned to speech, a hook-style title in the video's language and why it works. Transcribes the video first if needed (same cost and async behaviour as get_transcript). Suggestions are free per call.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many clips (default 5; hard cap is one clip per 30 s of video, minimum 20). |
| instruction | string | – | Editorial guidance, e.g. 'moments about pricing' or 'funny moments only'. |
| language | string | – | Spoken language of the video as ISO-639-1 (e.g. 'en', 'es'). Omit to auto-detect. |
| max_seconds | integer | – | Longest clip in seconds (default 90). |
| min_seconds | integer | – | Shortest clip in seconds (default 20). |
| reason_language | string | – | Language for the 'reason' field (ISO-639-1, default 'en'). Titles always follow the video's language. |
| url | string | yes | Public video URL: YouTube video/short/live replay, Twitch VOD, Kick VOD or TikTok video. |
| wait_seconds | integer | – | Seconds to wait for processing before returning status 'processing' (default 90). Long videos can take several minutes: just call again. |
No output schema declared.
No examples provided.
How do I install the CLIPCLIPER MCP server?
CLIPCLIPER is a hosted endpoint at https://clipcliper.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 · clipcliper.com
claude mcp add --transport http com-clipcliper-clipcliper 'https://clipcliper.com/mcp'
What is the CLIPCLIPER MCP server?
CLIPCLIPER is an MCP server listed in the public MCP registry as com.clipcliper/clipcliper. Timestamped transcripts, chapters and clip suggestions from YouTube, Twitch, Kick or TikTok links. This page covers its hosted endpoint (https://clipcliper.com/mcp).
Is the CLIPCLIPER MCP server safe to use?
CLIPCLIPER scores 0 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 CLIPCLIPER MCP server expose?
CLIPCLIPER exposes 3 tools: get_transcript, get_chapters, suggest_clips. Their descriptions and schemas cost roughly 789 tokens of context every time the server is loaded.
Does the CLIPCLIPER MCP server require authentication?
Its publisher declares no required credentials for CLIPCLIPER. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the CLIPCLIPER MCP server still maintained?
CLIPCLIPER has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 30 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.