Worth Sending
OfficialRelated Servers
Alternatives to Worth Sending
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables coding agents to submit their original request, proposed plan items, and observed repository conventions for per-item necessity scoring before making edits. It returns advisory keep, simplify, or review recommendations with reasons and evidence, without blocking or modifying the plan.13 npmMIT
- AlicenseNot gradedqualityBmaintenanceLets agents submit a traveler profile, trip context, and candidate listings to receive a deterministic, evidence-backed recommendation with score breakdowns, tradeoffs, risk flags, missing information, and confidence. It handles non-sensitive decision categories only and does not search inventory, book, transact, or persist data.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Codex and Claude Code agents to submit drafts for local rubric-based review through TypeSafe Jev, returning keep, rewrite, or uncertain decisions so agents can fix flagged issues and re-check once.MIT
- FlicenseNot gradedqualityBmaintenanceEnables users to evaluate cold email copy for spam heuristics, formatting ratios, unsubscribe compliance, and readability, returning a composite spam score, deliverability tier, flags, and recommendations to improve primary inbox placement.7-
- AlicenseNot gradedqualityCmaintenanceEnables an agent that reads a person's inbox to check a raw or .eml message and receive a 0-100 cold-outreach score with the reasons behind it. The agent can then avoid replying on the person's behalf to a cold message, or surface a likely cold one with its signals for the person to judge.410 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables an agent to check its own drafted messages for the wording, leaked placeholders, and chat wrappers that make readers think a bot wrote them, returning a verdict, 0-100 score, and per-finding suggestions. It also applies the safe fixes that need no judgement and reports what still requires a human or model rewrite before anything is sent.35 npmMIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one retrieves the rubric, the other performs the evaluation. The descriptions explicitly state that the rubric should be read first, eliminating any confusion about which tool to use when.
Both tool names follow a consistent snake_case verb_noun pattern: get_message_rubric and evaluate_message. The slight variation in noun phrase length does not break the predictable convention.
With only 2 tools, the set is slightly below the typical 3-15 range, but each tool is essential for the server's narrow purpose. The minimal count is justified by the focused workflow of fetching a rubric and then evaluating a message.
The two tools cover the full lifecycle for evaluating a message: obtaining the rubric and performing the assessment. No obvious operations are missing for the stated domain, and the server explicitly does not dispatch messages, so no send tool is needed.