Home / MCP registry index / org.ripclip/ripclip

RipClip

org.ripclip/ripclip in the official MCP registry. Endpoint https://ripclip.org/mcp/.

The registry describes it as: Clip long videos, open clips in the editor, draft posts and track views in your RipClip account.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http ripclip https://ripclip.org/mcp/

{
  "mcpServers": {
    "ripclip": {
      "url": "https://ripclip.org/mcp/"
    }
  }
}

code --add-mcp '{"name":"ripclip","type":"http","url":"https://ripclip.org/mcp/"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

list_projects list_clips list_library import_video estimate_hu find_clips job_status get_download_link list_social_accounts draft_post get_post_stats best_time_to_post edit_clip plan_posts weekly_report search fetch edit_catalog style_clip add_to_clip translate_captions preview_frame adjust_look frame_clip retime_clip mix_audio undo_edit import_photo save_template explain_clips find_moments get_moments clip_range list_clipping_presets write_captions update_draft delete_draft compare_platforms whats_taking_off why_it_worked get_account_stats show_clips show_drafts show_report

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-10): 24e4c64d4a43db7c. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/org-ripclip-ripclip/badge.svg)](https://lazaretto.dev/mcp-registry/org-ripclip-ripclip)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

YouTube and video MCP servers