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.

Cutshed

REMOTE · CUTSHED.COM

Free browser tools, Studio prices, and the public clipper quote. Account tools need OAuth.

Available components

+3 this week 68 Trust /100

Last scanned (4 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 5 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 Security57
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 588 tokens (~65/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage73
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 20% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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
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.

  • 4 Nov 26 +1

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

  • 1 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.

  • 30 Oct 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.

  • 28 Oct 26 +1

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

  • 26 Oct 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.

  • 24 Oct 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.

  • 22 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 21 Oct 26 61

    First indexed and scored.

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 5 Nov 2026 · Probed https://cutshed.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=cutshed.com CN=WE1,O=Google Trust Services,C=US 9 Oct 2026 7 Jan 2027 ECDSA 256 ECDSA-SHA256 e396586426cdb2b413395af2dff14f36
SANs: cutshed.com, www.cutshed.com, *.www.cutshed.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 cutshed.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
cutshed.com. absent 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
Header Value
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://cutshed.com/mcp Verified 200
http (plaintext) http://cutshed.com/mcp HTTPS enforced 301 https://cutshed.com/mcp
MCP tools · 9 exposed · ~528 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
get_generation ~46

Read one Studio generation's status and results for the token's account. Requires OAuth scope studio:generate. Pass the id returned by start_generation.

NameTypeReqDescription
idstringyesGeneration id.

No output schema declared.

No examples provided.

get_my_account ~29

Read the signed-in person's email and display name. Requires an OAuth bearer token with profile:read.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_my_credits ~29

Read the credit balance and recent credit history. Requires an OAuth bearer token with credits:read.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_studio_pricing ~40

Return Studio credit packs and model prices from the live catalog. Prices are credits and provider cents. This does not start a purchase or a generation.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_tool ~49

Return one free Cutshed tool by slug, title, or path. Example slug: vocal-remover.

NameTypeReqDescription
namestringyesTool slug, title, or path, such as vocal-remover.

No output schema declared.

No examples provided.

list_tools ~36

List Cutshed's free browser tools with the public URL and a one-line description. Studio, checkout, and account actions are not included.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

quote_clipper ~86

Return the public clipper quote for an 8-window highlight pass: windows, apiCents, credits, frameApiCents, markup, and vision. Audio-only scoring on the site is free. credits is the vision price when vision is true.

NameTypeReqDescription
windowsinteger–Optional. The public quote is an 8-window pass, so omit this or pass 8.

No output schema declared.

No examples provided.

search_site ~60

Search the public Cutshed guide (llms.txt) and the free-tool list. Returns short matching excerpts. It does not search account data. Account tools are separate and need OAuth.

NameTypeReqDescription
querystringyesWords to find in the public site guide.

No output schema declared.

No examples provided.

start_generation ~153

Start a Studio generation with the same pricing, balance check, and per-account limits as the website. Requires OAuth scopes studio:generate and credits:spend.

NameTypeReqDescription
aspectRatiostring––
audioboolean––
consentboolean––
durationnumber––
genrestring––
imagestring––
instrumentalboolean––
lyricsstring––
modelstringyes–
outputsinteger––
promptstring––
referencesarray––
resolutionstring––
speednumber––
stabilitynumber––
voicestring––

No output schema declared.

No examples provided.

Install

How do I install the Cutshed MCP server?

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

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

What is the Cutshed MCP server?

Cutshed is an MCP server listed in the public MCP registry as com.cutshed/cutshed. Free browser tools, Studio prices, and the public clipper quote. Account tools need OAuth. This page covers its hosted endpoint (https://cutshed.com/mcp).

Is the Cutshed MCP server safe to use?

Cutshed scores 68 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 Cutshed MCP server expose?

Cutshed exposes 9 tools: list_tools, get_tool, get_studio_pricing, quote_clipper, search_site, and 4 more. Their descriptions and schemas cost roughly 528 tokens of context every time the server is loaded.

Does the Cutshed MCP server require authentication?

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

Is the Cutshed MCP server still maintained?

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