Skip to main content
Glama
Theoddalex

imprest

by Theoddalex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to imprest

No user-submitted related servers found.

    Related Servers

    • clearance-mcp

      Nauti-Labs
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables AI agents to request human approval before spending money, check approval status, verify signed tokens, and manage API keys.
      13 npm
      MIT

    • valta-mcp

      Valta-hq
      A
      license
      A
      quality
      B
      maintenance
      An MCP server for Valta that exposes financial governance tools for AI agents, including spend authorization and audit trail via MCP-compatible clients.
      16
      51 npm
      1
      MIT

    • peage-mcp

      javimosch
      F
      license
      Not graded
      quality
      A
      maintenance
      MCP server that provides AI agents a prepaid fiat wallet, enabling them to pay metered APIs per call on the peage rail with adjustable spending caps.
      -
    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

    A4.2/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool has a distinct purpose: direct payment, token allowance, paid HTTP fetch, operator pending-action management, and read-only balance/gas. However, 'request_approval' can be misread as requesting human approval, which overlaps conceptually with list_pending_approvals/resolve_approval, though the descriptions make the distinction clear.

    Naming Consistency4/5

    The tool names mostly follow a consistent verb_noun pattern: request_*, list_*, resolve_*, get_*. 'pay_x402' is a slight outlier as a verb plus protocol identifier, and 'request_approval' is semantically a bit misleading, but there is no mixed casing or chaotic verb usage.

    Tool Count5/5

    Seven tools is well-scoped for a crypto spend-control server: three spend paths (payment, allowance, x402), two operator approval tools, and two read-only helpers. The set is neither bloated nor too thin.

    Completeness4/5

    The core lifecycle is covered: requesting payments, granting/revoking allowances, paying for HTTP resources, and operator approval of pending actions. Minor gaps include no audit/history listing, no way to query current allowances or policy limits, and agents cannot list their own pending requests, but these are workable around.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources