Skip to main content
Glama
Be-Infinitum

Pulse MCP Server

by Be-Infinitum
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Pulse MCP Server

No user-submitted related servers found.

    Related Servers

    • MyFatoorah MCP

      kuwaitdevs
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP hosts like Claude, VS Code, Cursor, and others to discover payment methods, create payment links, verify payments, inspect invoices, and manage refunds through focused tools, with a guided safe payment workflow and a restricted generic API escape hatch.
      7
      18 npm
      MIT

    • Usage And Billing MCP Server

      BACH-AI-Tools
      A
      license
      C
      quality
      D
      maintenance
      Enables access to Usage and Billing APIs for managing accounts, products, meters, plans, and usage reporting. Supports operations like creating products/plans, reporting usage, and retrieving billing information.
      18
      MIT

    • pai

      connortessaro
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to manage API keys and child keys with budgets and spending caps, set plans and model routing, handle wallet payments and top-ups, and verify signed receipts through MCP tools.
      MIT

    • agent-invoice

      nyx-builds
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to generate, track, and manage invoices via MCP tools, with CLI support for payment tracking and earnings summaries.
      MIT
    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

    B3.3/5.0

    Scored across 25 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes targeting specific resources and actions, such as create_customer vs. update_customer or track_event vs. track_events_batch. However, some potential ambiguity exists between list_payment_intents and list_received_payments, as both relate to payment tracking but with slightly different scopes that could confuse an agent about which to use for specific queries.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, such as create_customer, list_products, get_usage, and update_customer. All tools use snake_case with clear action verbs, making the set predictable and easy to navigate without any deviations in naming conventions.

    Tool Count3/5

    With 25 tools, the count is borderline high for a coherent set, as it may feel heavy and potentially overwhelming for an agent. While the tools cover a broad domain of billing, metering, and marketplace operations, the number approaches the upper limit where usability might degrade, placing it in the 16-25 range that feels borderline for typical agent interactions.

    Completeness4/5

    The tool set provides comprehensive coverage for billing, metering, and marketplace domains, including CRUD operations for customers, products, and webhooks, plus usage tracking and payment management. Minor gaps exist, such as no update or delete tools for products or meters, but agents can likely work around these with the available create and get operations without significant failures.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources