Skip to main content
Glama
devochkaskustikom

ddex-ern-382-mcp

by devochkaskustikom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to ddex-ern-382-mcp

No user-submitted related servers found.

    Related Servers

    • ai-fighter

      jeonghwanko
      A
      license
      A
      quality
      B
      maintenance
      Enables Dot/Codex hosts to read the game's authoring specifications and validate fighter manifests and asset packages with real WebP, hash, frame, and profile checks. It provides local MCP tools for creating and checking JSON-based fighter packages without uploading or registering them.
      2
      MIT

    • AgentProof

      tianhaoyu1001-prog
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP hosts and agents to run structural and format checks on delivered artifacts and generate consolidated QC reports in JSON and Markdown, so issues can be surfaced and fixed before delivery.
      MIT

    • acmt001-mcp

      sebastienrousseau
      A
      license
      A
      quality
      A
      maintenance
      MCP server for ISO 20022 acmt.001 Account Opening (and companion acmt.* messages): message-type discovery, required-field lookup, JSON Schema introspection, IBAN/BIC/LEI validation, flat-record validation, and validated acmt XML generation.
      7
      91 PyPI
      1
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 10 tools

    Disambiguation4/5

    Tools pair up cleanly as list_X/get_X patterns (list_sequences vs element_sequence, list_enums vs avs_values, list_elements vs explain_element), and the two validators target distinct inputs (XML string vs package directory). Minor overlap exists between list_enums and avs_values since both concern enumerated values, but descriptions clarify the boundary.

    Naming Consistency4/5

    Most tools follow a verb_noun convention (validate_ern_xml, list_sequences, explain_element, howto_compose). A few deviate to bare noun phrases (element_sequence, avs_values), which is mildly inconsistent but still readable and predictable within each tool family.

    Tool Count5/5

    Ten tools is well-scoped for a validation-plus-reference server, with each tool earning a distinct role across validation, structural reference, and composition guidance. No redundant or filler tools.

    Completeness4/5

    Covers validation (XML and package), schema ordering, enums, and composition howtos/element explanations, forming a coherent lifecycle for authoring and checking ERN 3.8.2. There is no tool to retrieve the raw XSD or synthesize example/valid ERN content, which would round out the surface but isn't a blocking gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources