Whalory
Related Servers
Alternatives to Whalory
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables agents to load anti-slop copywriting rules and deterministically audit markdown, HTML, JSX/TSX, and i18n copy for AI clichés, readability issues, and SEO/microcopy length budgets in English and Bahasa Indonesia.55 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables agents to analyze text strings or files for formulaic AI writing patterns, returning a 0–100 score, band label, specific violations with context, and concrete advice. It performs this rule-based linting locally without LLM judges or API calls.-
- AlicenseNot gradedqualityBmaintenanceEnables checking drafts against trained or preset voice styles, measuring rhythm and self-repetition, and running a fully local deterministic AI-tell audit with tiers, scores, and located findings. Also manages banned/custom word dictionaries and style instructions, with no network or model calls required.302 npmMIT
- FlicenseNot gradedqualityAmaintenanceScores prose from 0 to 100 for formulaic AI writing patterns using purely programmatic rules, with no LLM judge or API calls. Enables agents to lint text or files and receive a score, band label, specific violations with surrounding context, and concrete advice for each hit.-
- AlicenseNot gradedqualityCmaintenanceProvides writing guidance and mechanical lint checks to help AI clients draft or rewrite content in a specific natural voice.MIT
- FlicenseNot gradedqualityAmaintenanceEnables agents to analyze inline prose or files on disk for formulaic AI writing patterns, returning a 0-100 score, band label, specific violations with context, and concrete advice. Uses purely programmatic, configurable rules with no LLM judge or API calls.-
TDQS
Scored across 6 tools
The three lint-related tools overlap: check_final is explicitly described as returning findings 'in the same form as lint_text', and lint_file vs lint_text differ only in input source, so an agent may struggle to pick the right one. get_playbook and get_reference_section both read from Whalory's knowledge base with different anchors, which descriptions partially clarify but not decisively.
Five of six names follow a verb_noun pattern (lint_file, lint_text, get_playbook, get_reference_section, check_final), giving a predictable shape. profile_lookup breaks the convention with noun_verb ordering, a minor but visible deviation.
Six tools is well-scoped for a copy-linting and brand-voice guidance server: two lint entry points, one final gate, one profile resolver, and two knowledge retrieval tools. No tool appears redundant enough to drop, and none is filler.
Core lint-and-check workflows are covered, but there is no way to create, edit, or save a brand profile (profile_lookup only reads and suggests starters) and no tool to enumerate available playbooks or reference files upfront. An agent must discover anchors by trial or by calling get_reference_section without an anchor, which is a notable gap.