Skip to content

MCP servers › org.ripclip › ripclip

MCP server · registry snapshot 2026-11-16 · last tested 2026-11-16

ripclip MCP server

Registry name org.ripclip/ripclip

by ripclip.org · domain (the registry's namespace rule)Website ↗

Turn Twitch and Kick streams and long videos into captioned shorts; edit, draft posts, track views. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-11-16version 1.0.1streamable HTTP44 tools

Summary

org.ripclip/ripclip is a remote MCP server listed in the official MCP registry at version 1.0.1, under the namespace of the domain ripclip.org. On 2026-11-16 ProtocolProbe connected to it in read-only mode and read its inventory: 44 tools, 6 resources and 11 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Tools
44
Last tested
2026-11-16

Tool list size

26,540 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (44 tools). Counted with Anthropic's token counter on 2026-11-16, from the tool list we read on 2026-11-16. Median across 28,560 counted servers: 2,657 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-16 (ripclip.org), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.1).

Add to your client

Observed fact

This server accepted a session without any credential and lists 9 tools whose name or declaration suggests they change data (draft_post, edit_clip, style_clip, add_to_clip, translate_captions and 4 more). That is our reading of the names; we did not call them. Source: our connection, 2026-11-16.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-16
Mode
read-only (no tool calls)
Latest version
1.0.1, published 2026-11-15 (registry, as of the 2026-11-16 snapshot)
First listed version
2026-11-09 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, 2026-11-09 to 2026-11-15; 2 in the 90 days before the 2026-11-16 snapshot.
Most recent 2 versions
  • 1.0.1 · 2026-11-15
  • 1.0.0 · 2026-11-09
(versions still listed in the registry only)
Registry data
snapshot 2026-11-16
Package and repository
checked 2026-11-16
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 1.0.0 (published 2026-11-09) → 1.0.1 (published 2026-11-15), between the registry lists of 2026-11-15 and 2026-11-16.

No release note: the registry entry links no GitHub repository.

Source: the official MCP Registry list on 2026-11-15 and on 2026-11-16; release notes from the GitHub Releases API, checked 2026-11-16.

What it is

What does this server offer?

Observed inventory
44tools
6resources
11prompts

None of its 44 tools are described as changing anything. For 44 the reading was uncertain, so no mark is shown.

  • “Use this when the user wants to see the long videos already in RipClip (Twitch or Kick stream VODs, podcast episodes, uploads) or needs a project_id: "what videos do I have", "which stream did I impo…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • cursorstring
    • limitinteger
  • “Use this when the user wants to see their finished clips or saved photos, or needs a clip_id: "show me my clips", "what shorts did you make", "find my latest highlight", "my photos".”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs
    • cursorstring
    • limitinteger
    • kindstring
  • “Use this when the user wants to browse the Library, the rendered video files saved in their RipClip account: "what's in my Library", "list my exports".”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • cursorstring
    • limitinteger
  • import_videoon 2 other servers

    “Use this when the user wants to bring a long video into RipClip so it can be clipped: "clip this Twitch VOD", "turn my Kick stream into shorts", "use this podcast episode", "clip my last stream", "cl…”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world yes

    6 inputs
    • request_keystring
    • urlstring
    • rightsboolean
    • channelstring
    • platformstring
    • fileobject
  • estimate_hu

    “Use this when the user wants to know what clipping a video will cost before anything runs: "how much will it take to clip this stream", "what will that use".”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    4 inputs, 1 required
    • project_idstringrequired
    • request_keystring
    • range_startnumber
    • range_endnumber
  • “Use this when the user wants clips cut from a long video: "find the highlights in my stream", "turn my VOD into TikToks", "clip the funny moments".”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    20 inputs, 2 required
    • project_idstringrequired
    • max_hunumberrequired
    • request_keystring
    • countinteger
    • range_startnumber
    • range_endnumber
    • topicstring
    • min_secondsnumber
    • max_secondsnumber
    • clipping_presetstring
    • remove_filler_wordsboolean
    • remove_pausesboolean
    • remove_bad_takesboolean
    • highlight_keywordsboolean
    • auto_emojisboolean
    • auto_zoomboolean
    • stock_brollboolean
    • auto_transitionsboolean
    • hook_first_versionboolean
    • ai_titlesboolean
  • “Use this when the user wants to know whether something RipClip is working on has finished: "is my import done", "are my clips ready", "did the edit render".”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • job_idstringrequired
  • get_download_linkon 3 other servers

    “Use this when the user wants the video file of a clip, or to open it in the full editor: "send me the clip", "download it", "I want to post it myself", "let me edit this one".”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    1 input, 1 required
    • clip_idstringrequired
  • list_social_accountson 4 other servers

    “Use this when the user wants to know which social accounts are connected to RipClip (TikTok, YouTube, Instagram, Facebook, Threads, Bluesky; X is coming soon) or needs an account_id: "where can I pos…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • “Use this when the user wants to put one clip on their posting calendar: "schedule this clip for Friday", "post this to TikTok tonight", "put it on Shorts and Reels".”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    5 inputs, 2 required
    • clip_idstringrequired
    • platformstringrequired
    • captionstring
    • scheduled_atstring
    • account_idstring
  • get_post_statson 2 other servers

    “Use this when the user wants the numbers for their posts: "how are my clips doing", "which TikTok took off", "how many views did my Short get", "show my scheduled posts".”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs
    • platformstring
    • statusstring
    • limitinteger
  • best_time_to_poston 2 other servers

    “Use this when the user wants to know when to post: "best time to post on TikTok", "when should I upload my Shorts", "which day gets me the most views".”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • platformstring
    • timezonestring
Show 32 more tools
  • “Use this when the user wants an everyday change to a clip they already have: "make the captions bigger and yellow", "cut the silences", "remove the ums", "add chill music", "put a title on it", "spli…”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    18 inputs, 1 required
    • clip_idstringrequired
    • caption_sizestring
    • caption_colorstring
    • highlight_colorstring
    • caption_positionstring
    • caption_animationstring
    • uppercaseboolean or null
    • remove_silencesboolean
    • min_pause_secondsnumber
    • remove_filler_wordsboolean
    • musicstring
    • music_volumestring
    • hook_titlestring
    • layoutstring
    • auto_zoomboolean or null
    • emojisboolean or null
    • trim_start_secondsnumber
    • trim_end_secondsnumber
  • plan_posts

    “Use this when the user wants a batch of posts planned in one go: "plan my week", "fill my content calendar", "draft my top 3 clips for TikTok and YouTube Shorts at my best times".”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    4 inputs, 1 required
    • platformsarrayrequired
    • countinteger
    • timezonestring
    • clip_idsarray or null
  • weekly_reporton 13 other servers

    “Use this when the user wants a recap of how their posts did and what to post next: "how did last week go", "give me my analytics", "what should I post next".”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • timezonestring
    • daysinteger
  • “Use this when the user wants to find a video or clip in their RipClip account by a word in its name: "find my tournament stream", "which clip is called the giveaway".”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • querystringrequired
  • “Use this when the user wants the details of one project or clip that search found, or what was said in a video: "write show notes for this episode", "give me chapters / timestamps", "what did I say a…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired
  • edit_catalog

    “Use this when the user wants to know what the editor offers before changing a clip: "which caption styles are there", "what effects can I add", "any glitch transitions", "a sound effect for a big mom…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs, 1 required
    • kindstringrequired
    • querystring
    • limitinteger
  • style_clip

    “Use this when the user wants to change how a clip looks, at editor depth: "make the captions look like a gaming channel's", "give it a cinematic color grade", "add a glitch at the drop", "make it squ…”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    28 inputs, 1 required
    • clip_idstringrequired
    • caption_templatestring
    • fontstring
    • caption_stroke_widthnumber or null
    • caption_stroke_colorstring
    • caption_shadowboolean or null
    • caption_boxstring
    • filter_lookstring
    • filter_strengthnumber or null
    • brightnessnumber or null
    • contrastnumber or null
    • saturationnumber or null
    • warmthnumber or null
    • effectstring
    • effect_start_secondsnumber
    • effect_end_secondsnumber
    • effect_strengthnumber or null
    • transitionstring
    • transition_msinteger
    • speednumber or null
    • output_shapestring
    • progress_barboolean or null
    • fade_in_secondsnumber or null
    • fade_out_secondsnumber or null
    • templatestring

    and 3 more not listed here.

  • add_to_clip

    “Use this when the user wants to put text, a sticker, a sound or B-roll on a clip: "add a title that says NO WAY", "a fire emoji on the punchline", "a whoosh at 4 seconds", "find me B-roll for this li…”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    23 inputs, 1 required
    • clip_idstringrequired
    • textstring
    • text_stylestring
    • text_effectstring
    • text_animationstring
    • text_loopstring
    • text_colorstring
    • text_sizenumber or null
    • text_positionstring
    • text_start_secondsnumber
    • text_end_secondsnumber
    • stickerstring
    • sticker_at_secondsnumber
    • sticker_secondsnumber or null
    • sticker_positionstring
    • sticker_sizenumber or null
    • sound_effectstring
    • sound_at_secondsnumber
    • broll_searchstring
    • broll_linestring
    • broll_at_secondsnumber
    • broll_secondsnumber
    • broll_layoutstring
  • translate_captions

    “Use this when the user wants subtitles in another language on a clip: "add Spanish subtitles", "translate it to Japanese", "put the captions in Portuguese only".”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    3 inputs, 2 required
    • clip_idstringrequired
    • languagestringrequired
    • modestring
  • preview_frameon 2 other servers

    “Use this when the user wants to see how a clip looks at one moment: "show me the captions", "how does the title look", "what did that effect do".”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • clip_idstringrequired
    • at_secondsnumber
  • adjust_look

    “Use this when the user wants the light or color of a clip or photo changed: "brighten this photo", "it's too dark", "make it warmer", "more punch", "black and white", "make the sky bluer".”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    26 inputs, 1 required
    • clip_idstringrequired
    • exposurenumber or null
    • brightnessnumber or null
    • contrastnumber or null
    • highlightsnumber or null
    • shadowsnumber or null
    • whitesnumber or null
    • blacksnumber or null
    • saturationnumber or null
    • vibrancenumber or null
    • warmthnumber or null
    • tintnumber or null
    • huenumber or null
    • claritynumber or null
    • dehazenumber or null
    • sharpennumber or null
    • vignettenumber or null
    • grainnumber or null
    • fadenumber or null
    • colorstring
    • color_huenumber or null
    • color_saturationnumber or null
    • color_lightnessnumber or null
    • start_secondsnumber
    • end_secondsnumber

    and 1 more not listed here.

  • frame_clip

    “Use this when the user wants the picture framed differently in a clip or photo: "zoom in a bit", "show more of the left", "mirror it", "show the whole picture", "a black background, not the blur", "m…”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    11 inputs, 1 required
    • clip_idstringrequired
    • zoomnumber or null
    • position_xnumber or null
    • position_ynumber or null
    • flip_horizontalboolean or null
    • flip_verticalboolean or null
    • fitstring
    • backgroundstring
    • blur_amountnumber or null
    • custom_widthinteger or null
    • custom_heightinteger or null
  • retime_clip

    “Use this when the user wants the timing of part of a clip changed: "slow down the part at 0:12", "speed up the boring middle", "freeze on the reaction for 2 seconds", "cut out 0:20 to 0:25".”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    6 inputs, 1 required
    • clip_idstringrequired
    • start_secondsnumber
    • end_secondsnumber
    • speednumber or null
    • freeze_secondsnumber or null
    • removeboolean
  • mix_audio

    “Use this when the user wants the sound of a clip changed: "mute the original audio", "turn my voice up", "remove the background noise", "even out the volume", "make me sound like a robot", "the music…”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    10 inputs, 1 required
    • clip_idstringrequired
    • original_volumenumber or null
    • mute_originalboolean or null
    • denoisenumber or null
    • voice_boostnumber or null
    • normalizeboolean or null
    • voice_effectstring
    • music_volumestring
    • music_duckingboolean or null
    • ducking_dbnumber or null
  • “Use this when the user wants the last change to a clip or photo taken back: "undo that", "put it back", "I liked it better before", "go back one step".”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    1 input, 1 required
    • clip_idstringrequired
  • import_photo

    “Use this when the user wants a photo or picture brought into RipClip to edit it: "brighten this photo", "edit my picture", "fix the colors on this image".”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    2 inputs
    • urlstring
    • fileobject
  • save_templateon 8 other servers

    “Use this when the user wants a clip's look kept to use again: "save this style", "remember this edit", "make this my template", "clip my next streams like this".”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    6 inputs, 1 required
    • namestringrequired
    • clip_idstring
    • categorystring
    • descriptionstring
    • for_new_clipsboolean
    • look_fromstring
  • explain_clips

    “Use this when the user wants to know which clip to post first, why a clip was picked, or whether a clip is ready to post: "which clip should I post first", "why did you pick this one", "review my cli…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    6 inputs
    • clip_idsarray or null
    • job_idstring
    • campaign_min_secondsnumber
    • campaign_max_secondsnumber
    • must_sayarray or null
    • hashtagsarray or null
  • find_momentson 2 other servers

    “Use this when the user wants to search a long video for a topic by meaning before clipping: "where do I talk about the new game", "find the funny bits", "when did chat go wild", "find the part about …”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    7 inputs, 3 required
    • project_idstringrequired
    • topicstringrequired
    • max_hunumberrequired
    • request_keystring
    • countinteger
    • min_secondsnumber
    • max_secondsnumber
  • “Use this when the user wants the results of a find_moments search: "what did it find", "show me the matches".”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • job_idstringrequired
  • clip_range

    “Use this when the user wants ONE clip of an exact stretch of a video: "clip 1:02:10 to 1:03:00" (3730 to 3780 seconds), "make a short from that moment", or a match from get_moments.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    6 inputs, 4 required
    • project_idstringrequired
    • start_secondsnumberrequired
    • end_secondsnumberrequired
    • max_hunumberrequired
    • request_keystring
    • clipping_presetstring
  • list_clipping_presets

    “Use this when the user wants to clip in their saved style: "use my usual style", "what presets do I have".”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • write_captions

    “Use this when the user wants the text for a post written: "write my captions", "caption this for TikTok and Shorts", "give me a YouTube title and hashtags".”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world no

    3 inputs, 2 required
    • clip_idstringrequired
    • platformsarrayrequired
    • tonestring
  • “Use this when the user wants to change a post that is still a draft, or schedule it: "make the caption shorter", "move it to Friday 6pm", "turn comments on", "switch it to YouTube", "post it", "sched…”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    16 inputs, 1 required
    • post_idstringrequired
    • captionstring or null
    • scheduled_atstring
    • clear_timeboolean
    • platformstring
    • account_idstring
    • privacystring
    • allow_commentboolean or null
    • allow_duetboolean or null
    • allow_stitchboolean or null
    • discloseboolean or null
    • brand_organicboolean or null
    • brand_contentboolean or null
    • modestring
    • aigcboolean or null
    • scheduleboolean
  • delete_drafton 8 other servers

    “Use this when the user wants to remove a draft post: "scrap that draft", "delete the TikTok draft".”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • post_idstringrequired
  • compare_platformson 9 other servers

    “Use this when the user wants platforms side by side: "which platform got the most views for this clip", "TikTok vs Shorts vs Reels this month", "where do my clips perform".”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • clip_idstring
    • daysinteger
  • whats_taking_off

    “Use this when the user wants to know if a post is blowing up: "is anything taking off", "did my last clip pop", "is my TikTok going viral".”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • why_it_worked

    “Use this when the user wants to know what their better posts have in common: "why did that one do well", "what should I do more of", "what makes my clips work".”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • daysinteger
    • timezonestring
  • get_account_statson 1 other server

    “Use this when the user wants follower numbers: "how many followers did I gain this week", "how is my TikTok account growing".”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • show_clips

    “Use this when the user wants to watch their clips right in the chat: "show me my clips", "let me watch them", or after find_clips finishes (pass its job_id).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs
    • clip_idsarray or null
    • job_idstring
    • limitinteger
  • show_drafts

    “Use this when the user wants to see their posting calendar: "what's on my calendar", "show my drafts", "what's scheduled this week", or after plan_posts.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • daysinteger
    • timezonestring
  • show_report

    “Use this when the user wants to see how their week went as a chart in the chat: "show me my analytics", "chart my views".”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • daysinteger
    • timezonestring

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-16.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
0% of 247
Tools with a description
100% of 44
Typical description length
850 characters

The tool set

Counted from the listing

Tools
44
Size of the list
about 27,251 tokens for an agent to load (characters ÷ 4)
Naming
42 of 44 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 44 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-16 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://ripclip.org/mcp/
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "ripclip": {
      "url": "https://ripclip.org/mcp/"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "ripclip": {
      "type": "http",
      "url": "https://ripclip.org/mcp/"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"ripclip","type":"http","url":"https://ripclip.org/mcp/"}'
Claude Code
claude mcp add --transport http ripclip https://ripclip.org/mcp/
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "ripclip": {
      "type": "streamableHttp",
      "url": "https://ripclip.org/mcp/",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "ripclip": {
      "httpUrl": "https://ripclip.org/mcp/"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.ripclip]
url = "https://ripclip.org/mcp/"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "ripclip": {
      "url": "https://ripclip.org/mcp/"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://ripclip.org/mcp/ --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-16. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-16. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-16. Source: read 2026-11-16.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-16. Source: read 2026-11-16.

Own host

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint ripclip.org/mcp/Session openedmatchesour test · 2026-11-16
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-16

Tool list changes

Our reads compared · no tool called

Hosted endpoint ripclip.org/mcp/

1 of 1 comparison between consecutive reads showed a change (2 reads, 2026-11-12 to 2026-11-16; versions 1.0.0 to 1.0.1).

Last change seen between our reads on 2026-11-12 (version 1.0.0) and 2026-11-16 (version 1.0.1).

Changed (7):

draft_post: descriptionexplain_clips: description, input schemafetch: descriptionimport_video: description, input schemalist_social_accounts: descriptionplan_posts: descriptionupdate_draft: description, input schema

Compared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-11-16 is not known yet. No tool was called. How it is compared

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-16. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about org.ripclip/ripclip

Answered from the data above

Who publishes org.ripclip/ripclip?

The registry ties the namespace org.ripclip to the domain ripclip.org; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does org.ripclip/ripclip need an API key or sign-in?

It opened a session without any credential on 2026-11-16. The registry entry declares no required credential; no declaration is not a guarantee.

Has org.ripclip/ripclip been security tested?

Partly. 5 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-16
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: exercised
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

5 exercised11 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 5 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 5
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.exercised
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 11
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 2
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-11-16, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 954 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 44 tools, 6 resources, 11 prompts.
  4. 7,856 msFinished: 5 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-16; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-11-16
MCP capability
prompts, resources, tools
our test · 2026-11-16
Transport
streamable HTTP
registry · 2026-11-16
Required credentials
none declared
registry · 2026-11-16 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-16
Lifecycle status
registry · 2026-11-16
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-16

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “org.ripclip/ripclip: MCP server record.” Data checked 2026-11-16. https://protocolprobe.com/mcp/servers/org.ripclip/ripclip

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/org.ripclip/ripclip)](https://protocolprobe.com/mcp/servers/org.ripclip/ripclip)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology