overwing-mcp
Related Servers
Alternatives to overwing-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceProvides a single-purpose content-moderation gate that evaluates text and returns structured verdicts (spam/toxic probabilities, severity, confidence) with suggested actions (allow/review/block) for automated decision-making.11MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to score their outgoing responses against groundedness and prompt-injection risks mid-turn, returning allow, warn, or block verdicts before the response reaches the user.22 npm-
- AlicenseAqualityAmaintenanceEnables agents to verify claims against cited evidence, screen content for prompt injection and relevance before reading it, and rank candidates by meaning, all with calibrated probability verdicts.118,716 npm415MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to run fast, local, non-autoregressive System-1 decisions on text, including classification, triage, routing, and safety gating, via six typed tools with probabilistic outputs.208Apache 2.0
- AlicenseAqualityCmaintenanceEnables agents to perform typed judgments—classify, score, check, match, and screen—over closed answer sets with confidence scores, without text generation.722MIT

chakoshi MCP Serverofficial
AlicenseBqualityDmaintenanceEnables MCP clients to check text content using chakoshi's guardrail API for safety and moderation, returning assessment results.13MIT
TDQS
Scored across 10 tools
Each tool targets a distinct operation: single vs batch evaluation, rule set management, evaluation retrieval, and account/plan information. Even the plan-related tools (whoami, get_usage, list_plans) are cleanly separated by identity, usage, and catalog purposes.
Most tools follow a clear verb_noun pattern: list_rule_sets, get_rule_set, create_rule_set, get_evaluation, list_evaluations. evaluate, evaluate_batch, and whoami are minor deviations but still verb-first and predictable.
Ten tools is well-scoped for an LLM evaluation service: two evaluation paths, three rule set operations, two evaluation lookup operations, and three account/plan tools. Each tool earns its place without redundancy.
The evaluation lifecycle is well covered: evaluate, retrieve, and list evaluations, plus list/get/create rule sets. Update and delete for rule sets are missing, which is a minor gap, but agents can work around it by creating new rule sets.