MCP servers observed by Lowdown
io.github.Mvp2o-ai/cuttingfloor MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-11 to 2026-11-17) (Lowdown checks this server every 3 days); 73 tools listed. On 2026-11-17 a tool description with a URL appeared (new domain: cuttingfloor.ai). MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; tool definitions last changed on 2026-11-17 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.Mvp2o-ai/cuttingfloor
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.Mvp2o-ai/cuttingfloor?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 2 of 2 compared days.
- 2026-11-17: input or output schemas changed, descriptions changed, tool names changed, server version changed; tool count 72 → 73; a tool description with a URL appeared (cuttingfloor.ai)
- 2026-11-14: input or output schemas changed, descriptions changed, server version changed
What tools does it list?
73 tools on 2026-11-17:
adjustment.addaudio.fadeaudio.set_gainaudio.set_masteraudio.set_pancaption.addclip.addclip.freezeclip.linkclip.moveclip.removeclip.replaceclip.rollclip.set_animationclip.set_blendclip.set_enabledclip.set_maskclip.set_speedclip.set_transformclip.slideclip.slipclip.splitclip.trimclip.unlinkcreate.cutoutcreate.lipsynccreate.mattecreate.motioncreate.stabilizedcreate.stemscreate.stillcreate.upscaledcreate.voiceoveredit.batchexport.timelineexport.videofilter.addfilter.removefilter.setjob.canceljob.getjob.listjudge.askmedia.analyzemedia.correlatemedia.deletemedia.getmedia.importmedia.listmedia.listenmedia.searchmedia.seekmedia.uploadqa.checkrange.extractrange.liftrender.framesskills.getskills.searchtext.settimeline.createtimeline.difftimeline.gettimeline.historytimeline.loadtimeline.set_sequencetitle.addtrack.addtrack.removetrack.settransition.addtransition.removetransition.set
MCP Registry declaration
- Registry name:
io.github.Mvp2o-ai/cuttingfloor - Declared version: 0.55.9
- Status: active
- Declared hosts:
api.cuttingfloor.ai
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.Mvp2o-ai/cuttingfloor", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.Mvp2o-ai/cuttingfloor?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).