Skip to main content
Glama
miracleweasel

katto-mcp

by miracleweasel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to katto-mcp

Related Servers

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.1/5.0

Scored across 16 tools

Disambiguation3/5

Several tools have overlapping purposes: katto_get_account and katto_get_usage both return quota/plan details, and katto_get_job already includes clips while katto_get_clips exists as a separate convenience. This could cause an agent to select the wrong tool when a single resource is exposed through multiple endpoints.

Naming Consistency4/5

Names mostly follow a consistent katto_verb_noun pattern, but there is a minor inconsistency: collection-returning tools use both 'list' (katto_list_jobs, katto_list_sources) and 'get' (katto_get_clips), and katto_get_account vs katto_get_usage are semantically close despite different names.

Tool Count4/5

16 tools is slightly above the typical 3-15 range, but each tool maps to a clear API operation and the set does not feel bloated. The count is reasonable for a video-clipping service with listing, job management, rendering, and account endpoints.

Completeness4/5

The toolset covers the main lifecycle: create/list/get/cancel jobs, retrieve clips and transcripts, rerender/dub clips, poll rerenders, and check account/usage. There are minor redundancies rather than major gaps, though a dedicated single-clip fetch or rerender listing could be considered missing.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources