Skip to main content
Glama

Related Servers

Alternatives to finops-studio

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      MCP server for German e-invoice compliance (XRechnung 3.0 & ZUGFeRD 2.x) enabling AI agents to validate, generate, parse, and check compliance of electronic invoices per EN 16931.
      6
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A fully local, closed-world MCP server that manages, validates, and serves bank-specific ISO 20022 clearing profiles and rule packs, enabling AI agents to discover profiles, fetch them, lint payloads against them, and validate rule-pack definitions.
      4
      165 PyPI
      1
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      MCP server that enables AI agents to parse, validate, and reverse ISO 20022 bank statements, with tools for discovering message types and return reasons.
      24
      190 PyPI
      2
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that provides AI agents with tools to validate SWIFT MT and ISO 20022 MX payment messages, check BIC/IBAN correctness, and convert between MT and MX formats.
      7
      4 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server providing deterministic accounting tools for AI agents, including bank statement parsing, document classification, money math, and webhook verification.
      2
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      A Model Context Protocol server that exposes the pain001 ISO 20022 Customer Credit Transfer Initiation library as agent tools, enabling AI assistants to generate and validate standardized payment XML messages.
      30
      1,471 PyPI
      1
      Apache 2.0

    TDQS

    A3.9/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a distinct resource-and-action identity: parsers (pain.002, BAI2), validators (routing, file audit), and format-specific generators (SEPA, EU e-invoice, NACHA, DATEV, ABA, BACS, CPA-005). The only plausible overlap — validate_bank_routing vs audit_bank_file_format — is explicitly disambiguated in both descriptions by scope (single identifier vs full file). Country/format generators are separated by unambiguous format names.

    Naming Consistency5/5

    All names follow a strict snake_case verb_noun pattern: parse_*, validate_*, audit_*, generate_*. Naming is fully predictable, so an agent can infer the verb class and target format from the name alone.

    Tool Count5/5

    Eleven tools is well within the ideal 3-15 range for a payments/accounting file toolkit. Each tool maps to a distinct, non-redundant format or validation concern, so no tool feels like filler.

    Completeness4/5

    Generation and validation coverage is broad (SEPA, NACHA, BACS, ABA, CPA-005, DATEV, EN 16931) with inbound parsing for pain.002 and BAI2. Notable gaps remain: no CAMT.053/MT940 bank statement parsing and no structured parsing of inbound NACHA/BACS/ABA return files, though audit_bank_file_format partially covers file inspection.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues