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.

gimmeclip

REMOTE · GIMMECLIP.COM

Video info, transcripts, trimmed share links and AI edits (captions, vertical) for public videos.

Available components

+4 this week 62 Trust /100

Last scanned (23 hours ago)

Scores higher than 45% 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 Security46
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1524 tokens (~254/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (11)

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

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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.

  • 21 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • “edit_video” added an optional parameter “allow_ai_edit” cosmetic
  • 20 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “edit_video” rewrote its description, which is the text the model reads security
    • “edit_video” reworded the description of “frame” cosmetic
  • 19 Nov 26 +1

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

  • 18 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_video_info” rewrote its description, which is the text the model reads security
    • “download_video” reworded the description of “url” cosmetic
    • “edit_video” reworded the description of “url” cosmetic
    • “get_transcript” reworded the description of “url” cosmetic
    • “get_video_info” reworded the description of “url” cosmetic
    • “share_video” reworded the description of “url” cosmetic
  • 17 Nov 26 +1

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

  • 16 Nov 26 0
    • Tool “share_video” rewrote its description, which is the text the model reads security
  • 15 Nov 26 +1
    • Tool “edit_video” rewrote its description, which is the text the model reads security
  • 14 Nov 26 0
    • 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://gimmeclip.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=gimmeclip.com CN=WE1,O=Google Trust Services,C=US 10 Nov 2026 8 Feb 2027 ECDSA 256 ECDSA-SHA256 f2c6726bfb79c0d90e588264e15b9d91
SANs: gimmeclip.com, www.gimmeclip.com, *.www.gimmeclip.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 gimmeclip.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
gimmeclip.com. No DS 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://gimmeclip.com/mcp Verified 200
http (plaintext) http://gimmeclip.com/mcp Inconclusive 405
MCP tools · 6 exposed · ~1,314 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
check_download ~36

Wait for a download started by download_video and return its link when ready.

NameTypeReqDescription
job_idstringyesjob_id from download_video.

No output schema declared.

No examples provided.

download_video ~239

Prepare a video as MP4 (H.264 + AAC, plays everywhere), MP3, or a looping GIF of up to 10 s, and return a download link. The link works for 15 minutes after the last request. Long videos may still be preparing when this returns: then call check_download with the job_id. Counts against the caller's daily limit (40 per IP).

NameTypeReqDescription
endnumber–Optional: end of the part to keep, in seconds (after start).
iteminteger–Which video of a multi-video post (1-based); see get_video_info.
qualitystring–Resolution cap (the smaller side, so vertical videos count the same). "audio" gives an MP3; "gif" a looping GIF of a selection up to 10 s (set start and end).
startnumber–Optional: start of the part to keep, in seconds.
urlstringyesLink to a public post or video (YouTube, Instagram, X / Twitter, TikTok, Bluesky, Facebook, VK, LinkedIn, Weibo, Twitch, Kick).

No output schema declared.

No examples provided.

edit_video ~462

Make an edited copy of part of a public video (up to 15 s between start and end): vertical 9:16 or square crop, burned-in captions of the speech and of other sounds such as "[dog barking]" (in the language spoken, or translated to English, Portuguese, Spanish), even loudness; with a prompt also AI-written text over the picture (thought bubbles, meme captions, a title), a dramatic zoom, and slow motion or speed-up. Describe the edit in prompt, or set frame and captions_language (these override the prompt). Returns a gimmeclip.com/w/… watch link kept for 30 days; if it returns an edit_id, call edit_video again with only that edit_id to keep waiting. Each new edit counts against the caller's 30 edits a day, and preparing the source against the daily download limit; repeating the same edit is free.

NameTypeReqDescription
allow_ai_editboolean–Set true to allow a paid AI video change interpreted from the prompt. Default false: the rest of the edit is still made.
captions_languagestring–Burn in captions: "source" in the language spoken, or translated. Omit for no captions (unless the prompt asks for them).
edit_idstring–Only to resume: edit_id from an earlier edit_video call that was still working.
endnumber–Optional: end of the part to keep, in seconds (after start).
framestring–"9:16" vertical (default), "1:1" square, "original", or any width:height from 2:5 to 5:2 ("4:5", "16:9").
iteminteger–Which video of a multi-video post (1-based); see get_video_info.
promptstring–Optional: the edit in plain words, e.g. "15-second vertical with Portuguese captions".
startnumber–Optional: start of the part to keep, in seconds.
urlstring–Link to a public post or video (YouTube, Instagram, X / Twitter, TikTok, Bluesky, Facebook, VK, LinkedIn, Weibo, Twitch, Kick).

No output schema declared.

No examples provided.

get_transcript ~230

Transcribe speech from a public video, optionally between start and end. Returns a transcript_id while processing in the background: call this tool again with transcript_id to check. When done, fetch text_url for timestamped plain text with source attribution; Markdown and JSON links are also provided. Parts without speech are listed as machine-labelled sounds with times, closed-caption style (e.g. "[cat meowing]", "[music]"). Visual content is not described. New transcription uses the normal daily quota; results last 30 days.

NameTypeReqDescription
endnumber–Optional: end of the part to keep, in seconds (after start).
iteminteger–Which video of a multi-video post (1-based); see get_video_info.
startnumber–Optional: start of the part to keep, in seconds.
transcript_idstring–Resume/check an existing transcription.
urlstring–Link to a public post or video (YouTube, Instagram, X / Twitter, TikTok, Bluesky, Facebook, VK, LinkedIn, Weibo, Twitch, Kick).

No output schema declared.

No examples provided.

get_video_info ~108

Title, uploader, duration, thumbnail and available qualities of a public video link (YouTube, Instagram, X / Twitter, TikTok, Bluesky, Facebook, VK, LinkedIn, Weibo, Twitch, Kick). Posts with several videos list each one as an item.

NameTypeReqDescription
urlstringyesLink to a public post or video (YouTube, Instagram, X / Twitter, TikTok, Bluesky, Facebook, VK, LinkedIn, Weibo, Twitch, Kick).

No output schema declared.

No examples provided.

share_video ~239

Prepare the video (or just the part between start and end) and return a short gimmeclip.com/w/… link anyone can open and play, kept for 30 days. Counts against the caller's daily limit (40 per IP, 200 with an API key) unless the same clip was shared before. If it returns a job_id, call share_video again with that job_id to keep waiting.

NameTypeReqDescription
endnumber–Optional: end of the part to keep, in seconds (after start).
iteminteger–Which video of a multi-video post (1-based); see get_video_info.
job_idstring–Only to resume: job_id from an earlier share_video call that was still preparing.
qualitystring–Resolution cap (the smaller side, so vertical videos count the same).
startnumber–Optional: start of the part to keep, in seconds.
urlstring–Link to a public post or video (YouTube, Instagram, X / Twitter, TikTok, Bluesky, Facebook, VK, LinkedIn, Weibo, Twitch, Kick).

No output schema declared.

No examples provided.

Install

How do I install the gimmeclip MCP server?

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

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

What is the gimmeclip MCP server?

gimmeclip is an MCP server listed in the public MCP registry as com.gimmeclip/gimmeclip. Video info, transcripts, trimmed share links and AI edits (captions, vertical) for public videos. This page covers its hosted endpoint (https://gimmeclip.com/mcp).

Is the gimmeclip MCP server safe to use?

gimmeclip scores 62 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 gimmeclip MCP server expose?

gimmeclip exposes 6 tools: get_transcript, get_video_info, download_video, check_download, share_video, edit_video. Their descriptions and schemas cost roughly 1,314 tokens of context every time the server is loaded.

Does the gimmeclip MCP server require authentication?

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

Is the gimmeclip MCP server still maintained?

gimmeclip 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 gimmeclip MCP server?

VerifyMCP ran 11 checks on gimmeclip, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about gimmeclip: Authorization and HTTPS. 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.