aethis-mcp
OfficialRelated Servers
Alternatives to aethis-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables users to trace regulatory rule changes to affected parties and required actions through deterministic safety gates, returning dated action plans and hash-linked evidence records. Supports 12 MCP tools over stdio or streamable HTTP for source comparison, obligation decomposition, scope assessment, planning, and evidence validation across multiple domain packs.MIT
- AlicenseAqualityAmaintenanceEnables agents to evaluate context against custom criteria and receive typed decisions (classifications, scores, probabilities) from JEV or local LAYA, with validation policies and durable decision records.41Apache 2.0
- AlicenseNot gradedqualityAmaintenanceDeterministic MCP notary suite for subscription policies: refund, cancellation, return, and trial terms. Stateless, read-only rules engine with auditable verdicts and hosted remote endpoints.14 npm1MIT

Cruxible Coreofficial
AlicenseNot gradedqualityAmaintenanceDeterministic decision engine with DAG-based receipts. Build entity graphs, query with MCP, get auditable proof.17Apache 2.0- AlicenseNot gradedqualityCmaintenanceEnables agents to evaluate single records or batches with dynamically authored typed questions, returning structured decisions and probabilities.MIT

Jev MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceEnables AI clients to run read-only yes/no checks, classifications, and ordered scores with probabilities, supporting triage, routing, sentiment, and lead-fit decisions through hosted or self-hosted MCP tools.41 npmAGPL 3.0
TDQS
Scored across 35 tools
Most tools target distinct actions within the authoring/decision lifecycle, and descriptions often explicitly disambiguate similar-sounding pairs (e.g. discover_rulesets vs list_rulesets, schema vs rulebook_schema). However, with 35 tools there are several easily confused clusters: discover/refine/validate for sections and fields, add_guidance vs add_domain_guidance, and explain vs graph vs explain_failure.
All tools use the same aethis_ snake_case prefix and are mostly verb_noun (e.g. create_ruleset, list_projects, archive_project). Minor deviations include noun-only or verb-only names like aethis_schema, aethis_graph, aethis_decide, and aethis_refine, but the overall convention is predictable.
35 tools is heavy for the apparent domain, well above the 3–15 sweet spot. Many operations are split into discover/refine/validate triples, suggesting consolidation could reduce surface area without losing capability.
The surface covers a full authoring lifecycle: discovery, field/section validation, generation, testing, refinement, publishing, archiving, guidance, usage, and review. Minor gaps remain, such as no rulebook archival/deletion, no direct ruleset update tool, and no get_project or list_tests operation.