獬豸(Xiezhi)小说投稿评审 MCP Server
Related Servers
Alternatives to 獬豸(Xiezhi)小说投稿评审 MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI-assisted long-form novel writing through 24 novel_* tools with code-enforced guardrails: outline-approval gates before drafting, fact-ledger conflict rejection, repetition and AI-tone/consistency audits at zero token cost, platform-specific review checks, and batch drafting with checkpoint resume. Also supports full-book health checks, chapter text-to-speech, and proposal-based revision so older drafts are never overwritten.2,070 npm48MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to draft long-form web novels with persistent, disk-backed memory, assembling a pre-writing task brief from structured settings, outlines, foreshadowing ledgers, and timelines, then committing post-chapter fact increments. It also audits pacing, checks per-chapter six-dimension consistency, gates commits on unresolved review findings, and can replay the commit chain to rebuild state when records and manuscripts disagree.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables writers and AI assistants to take a one-sentence idea through fourteen staged production steps for series, short-form drama, film, or novels, with per-stage criteria checks that flag missing or contradictory material. It also provides project scaffolding, continuity ledgers, outline and screenplay drafting, storyboards, version rollback, and Word/portfolio export through 54 local-only tools.MIT
- AlicenseAqualityCmaintenanceEnables AI tools to collaboratively write novels by managing chapters, characters, and story state through commands like validate, context, draft, review, and approve.8MIT
- AlicenseAqualityBmaintenanceEnables AI hosts to plan, draft, and check long-form novel chapters while honoring canon settings, character state, arcs, and check ordering, with approval-gated atomic commits. It keeps world, character, and chapter files as the human-editable source of truth, with snapshots and rollback for recovery.2717 npmApache 2.0
- AlicenseAqualityCmaintenanceEnables AI coding agents to submit work for external review before declaring a task done, receiving evidence-backed fix lists and verdicts based on git-measured changes and calibrated quality scoring.3MIT
TDQS
Scored across 25 tools
The set has many clearly dimension-specific probes, but several tools overlap: review_chapter already embeds check_redline, red_team, benchmark, and platform_fit, so an agent must decide between the aggregate pipeline and component calls. cache_stats also advertises a clear capability that duplicates cache_clear. Descriptions help but do not fully eliminate these boundary questions.
All names are snake_case and largely follow grouped verb_noun or prefixed conventions (check_*, review_*, foreshadow_*, cache_*, blind_*). A few standalone names are noun phrases (red_team, benchmark, platform_fit, impact_plan) rather than verb-led, and verb choice varies, but the pattern remains readable and casing is consistent.
25 tools is at the heavy end; the domain is genuinely complex, covering redlines, single/batch review, consistency, pacing, foreshadowing, blind review, and caching, so most tools earn a place. Still, the aggregate-vs-component duplication and granular probes make the surface larger than an agent can comfortably navigate, fitting the borderline-heavy range.
Coverage is unusually thorough for novel submission review: compliance, quality, pacing, consistency, foreshadowing lifecycle, platform fit, blind review, and next-chapter brief all have tools. Minor gaps remain: there is no explicit fact-contract review/approve/update operation after extract_facts, and no history/retrieval tool for prior review outputs beyond cache statistics. These are workable gaps.