Skip to main content
Glama
mcp-server-vippsmobilepay

mcp-server-vippsmobilepay

Related Servers

Alternatives to mcp-server-vippsmobilepay

No user-submitted related servers found.

    Related Servers

    TDQS

    A4/5.0

    Scored across 14 tools

    Disambiguation5/5

    Tools split cleanly along three domains (funds ledger reporting, ePayment, Recurring agreements) and each action targets a distinct resource+verb: get_payment vs capture/refund/cancel_payment, and the *_charge variants are unambiguously scoped to Recurring charges. Even the closely related reads (list_ledgers vs get_funds_summary vs list_transactions) are differentiated by their descriptions (accounts, sums, entries). No two tools appear to do the same thing.

    Naming Consistency5/5

    Every tool uses the same vipps_ prefix followed by a verb_noun pattern (list_ledgers, get_payment, capture_payment, refund_charge, cancel_charge, check_connection). Resource suffixes (payment vs charge vs agreement vs ledger) are used consistently to distinguish domains.

    Tool Count5/5

    14 tools is well within a comfortable range and each one maps to a real operation: 4 ledger/reporting, 4 ePayment, and 6 Recurring agreement/charge tools. Nothing looks redundant or like filler.

    Completeness3/5

    Read and money-moving coverage is solid for existing payments, agreements and charges, but there is no way to initiate a payment, create an agreement or create a charge, and payments can only be fetched by reference with no list/search operation. These gaps are workable (creation often happens via the frontend/SDK) but will cause dead ends for agents asked to start a payment flow or reconcile an unknown payment.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues