Skip to main content
Glama
massimiliano-dev

fse-mcp

by massimiliano-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to fse-mcp

No user-submitted related servers found.

    Related Servers

    • beliq-mcp by beliq-eu

      beliq-mcpofficial

      beliq-eu
      A
      license
      A
      quality
      C
      maintenance
      Validates electronic invoices (XRechnung, ZUGFeRD, Factur-X, Peppol BIS, etc.) against authority-pinned rules and explains failures.
      2
      137 npm
      MIT

    • ddex-ern-382-mcp

      devochkaskustikom
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP-capable clients to look up DDEX ERN 3.8.2 structure, element and attribute semantics, documented child sequences, AVS values, and step-by-step composition guides. It also performs offline XSD validation of ERN XML and package checks for delivery conventions such as BatchComplete, relative URLs, DeliveryType, and message MD5.
      10
      12 npm
      MIT

    • rnds-mcp

      Voa-Health
      A
      license
      Not graded
      quality
      A
      maintenance
      A local stdio MCP server that lets agents validate Brazilian health identifiers (CPF, CNS, CNES), look up RNDS CodeSystems and ValueSets, and check FHIR Bundles against packaged codes and references. Everything runs offline with no network calls or authentication against the RNDS.
      Apache 2.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: validation of a document, explanation of an error string, generation of a sample document, and terminology lookup. The possible overlap between validation and error explanation is resolved because explain_schematron_error takes an error message or rule id rather than a document.

    Naming Consistency5/5

    All tool names use consistent snake_case verb_noun phrasing: validate_cda, explain_schematron_error, generate_sample_cda, and lookup_code. The pattern is predictable and readable.

    Tool Count5/5

    The set is narrowly scoped to FSE 2.0 CDA2 validation and assistance, so four tools is reasonable. Each tool covers a distinct and useful part of the workflow without redundant operations.

    Completeness4/5

    The core local workflow is covered: validate a CDA, explain validation errors, generate a synthetic starting document, and look up terminology codes. Minor gaps remain, such as listing supported document types or catalog metadata and batch validation, but agents can generally work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources