obper-mcp
Related Servers
Alternatives to obper-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to run deterministic Persian writing checks, search and retrieve rules and profiles, and validate proposed edits before applying them. It supports mechanical proofreading for orthography, spacing, punctuation, variant spellings, calques, and machine-like sentence patterns.MIT
- AlicenseNot gradedqualityBmaintenanceEnables users to get sourced Arabic grammar, spelling, punctuation, quotation, and formatting guidance, audit mechanical text issues, disambiguate selected unvowelled words with selective diacritics, and prepare proofreading checklists for host AI models.MIT
- FlicenseAqualityBmaintenanceLints English and Persian marketing copy for AI tells, puffery, facts missing from the brief, and channel limits, and loads copywriting playbooks and brand voice profiles. Runs locally with the Python standard library and makes no network calls. Made by Whalya, a product-led venture studio.26-
- AlicenseNot gradedqualityCmaintenanceEnables AI hosts to check text for grammar, spelling, and style errors, measure readability, and generate tone-adjusted rewrites through structured tool calls. Every tool returns predictable, typed output for reliable routing and results.MIT
- AlicenseAqualityCmaintenanceEnables deterministic, LLM-free checking of text against a prose editorial standard, returning violations with rule IDs, locations, severity, confidence, and suggested fixes, while also supporting safe fixes and writing measurements.514 npmMIT
- AlicenseBqualityBmaintenanceEnables AI agents to work with Iran-specific data and Persian/RTL frontends fully offline, covering Jalali date conversion, national ID, card, Sheba and mobile validation, Persian text and number formatting, bank and operator lookup, VAT and price handling, plus RTL auditing and CSS/Tailwind conversion. All tools run locally with no API keys.5654 npm5MIT
TDQS
Scored across 11 tools
The three rule-building tools (rule_pack, deep_rules, smart_rules) overlap heavily — all produce editing checklists for Persian text, and the distinctions (compact vs full vs diagnostic-driven) are subtle enough that an agent could easily misselect. Similarly, search, ruling, and rule_pack all query the same vault, with boundaries explained only in prose. The mechanical_pass/verify_regression/diff_report trio is more clearly separated by their distinct gate/ledger roles.
All names are lowercase snake_case with no camelCase mixing, which is a solid baseline. However, the pattern shifts between verb_noun (read_note, map_vault, verify_regression, diff_report) and bare noun/verb forms (search, reindex, ruling), so the convention is mostly but not fully predictable.
Eleven tools is a reasonable scope for a Persian editing pipeline plus vault access. It is slightly heavy given that three of them (rule_pack, deep_rules, smart_rules) occupy nearly the same slot, suggesting some consolidation is possible, but nothing is wildly out of range.
The editing pipeline is well-covered end to end: diagnose (smart_rules), fix (mechanical_pass), verify (verify_regression), and audit (diff_report), plus vault access via search/read_note/map_vault/reindex. The vault side is read-only with no note creation or update, but that may be intentional if notes are authored elsewhere, so the gap is minor.