Cue
Related Servers
Alternatives to Cue
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for AI compliance auditing. Scores agent outputs for hallucination liability under the EU AI Act, issues verifiable compliance stamps, and tracks audit history by agent.MIT
- AlicenseAqualityBmaintenanceMCP server for verifying AI agent claims vs reality — single-transcript inline grounding-check that flags when an agent's response states facts not in the input context, when its code silently swallows exceptions and substitutes mock data, or when its multi-turn transcript contains contradictions or unverified completion claims. Sub-second, local, free, no API calls.429 PyPI1MIT
- AlicenseAqualityDmaintenanceMCP server that analyzes your writing style to generate personal voice rules, scores drafts for AI slop, and verifies authorship, enabling LLMs to write in your specific voice.723 PyPIMIT
- AlicenseAqualityDmaintenanceA ruthless, read-only code review MCP server that analyzes code produced by AI coding assistants, catching missing requirements, security vulnerabilities, edge cases, and performance issues without ever modifying files.114 npmMIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that enables AI coding agents to pre-validate packages before installation, audit code changes for duplicated boilerplate and lazy placeholders, and detect when modified files drift from the original task intent.294 npmApache 2.0
- AlicenseAqualityDmaintenanceAn MCP server that inspects AI-generated code and returns a deterministic list of structural and safety violations, so an AI coding agent can fix its own output before the code lands.2MIT
TDQS
Scored across 3 tools
Each tool has a distinct role: analyze_message performs the core honesty check, cue_status confirms connectivity, and check_usage reports quota/plan. cue_status and check_usage are both lightweight informational tools that could be mildly confused at a glance, but their descriptions clearly separate connection status from usage quotas.
All three names use snake_case and read predictably, with analyze_message and check_usage following a verb_noun pattern. cue_status deviates slightly by prefixing the server name instead of using a verb, but the convention remains consistent and readable.
Three tools for a focused honesty-guardian server is reasonable: one core checking tool plus two zero-cost supporting tools. It is on the lean side, but every tool serves a purpose and none feels redundant.
The core lifecycle is covered: run a check, verify the service is active, and inspect remaining quota. The only minor gap is that check_usage references 'prompt rewrites' as a separate capability with no dedicated tool, though rewrites appear to be delivered through analyze_message output.