fish-curator
Related Servers
Alternatives to fish-curator
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP clients to classify, score, and evaluate content with structured typed decisions via a single generic tool.12MIT
- AlicenseNot gradedqualityBmaintenanceEnables a mechanical gating workflow for task intake, dispatch, independent review, verdict recording, auditing, and snapshot-based restoration through twelve stdio MCP tools.794 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to operate a user's own Bilibili account through MCP tools: scan-code login, browsing recommendations and rankings, watching videos with AI summaries, subtitles and frame overviews, plus commenting, @-mentioning, direct messaging, posting dynamics, and uploading videos. All operations return structured JSON with built-in rate limiting, audit logging, and safety guardrails.1,154 PyPI389MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to batch repetitive web admin work by harvesting queue items read-only, collecting verdicts, and applying them only after human approval, with dry runs, staged rollout, rate limits, a circuit breaker and an audit log. Also provides general browser control — navigating, reading, filling forms and clicking on allowed sites through an already logged-in local browser, pausing for confirmation before irreversible actions.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to analyze short-form videos into scenes with transcripts, beats, levers, and holds, and to quickly screen videos for production, voice, and custom questions.113 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to search videos, fetch video details and comments, and manage multiple isolated Douyin accounts (login, bind, alias, unbind) through standard MCP tools. Also supports explicitly authorized write actions such as posting image or text comments, liking videos, deleting comments, and sending direct messages, with read and write operations routed to a specified account.MIT
TDQS
Scored across 17 tools
Most tools map to one distinct step (feed, detail, blacklist, audit, QR login, notification queue), but the high-level submit_verdict overlaps heavily with block_author, like_video, collect_video and notify_master, which perform the same side effects individually. The descriptions try to disambiguate by calling submit_verdict the 'recommended entry' and naming it in each action tool, but an agent still has to decide between the orchestrator and the granular actions, and notify_master vs flush_notifications/check_notification needs careful reading.
Nearly all names are snake_case verb_noun (get_criteria, block_author, like_video, reset_seen) with platform prefixes kept consistent (bili_qr_login / bili_qr_poll). Minor deviations: login_status is a noun phrase with no verb, and notifications is plural in flush_notifications but singular in check_notification.
17 tools is on the heavy side, but each corresponds to a real step in the curation loop (auth, fetch, inspect, judge, act, notify, audit). The QR pair and the notification queue tools could be consolidated, but nothing looks redundant enough to be cut outright.
The lifecycle is well covered: login/health, feed retrieval, frame-level detail, verdict, block/unblock, like, collect, notify, notification delivery verification, blacklist, audit and seen-reset. The main gap is no rollback for positive actions — there is unblock_author but no unlike/uncollect — so a mistaken B verdict cannot be undone, and config can only be read (get_criteria) not updated.