Skip to main content
Glama
Valta-hq

valta-mcp

by Valta-hq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to valta-mcp

No user-submitted related servers found.

    Related Servers

    • imprest

      Theoddalex
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that provides programmable spend limits and audit trails for AI agents to make payments from a dedicated wallet, preventing overspend and unauthorized transactions.
      8
      MIT
    • expenselm-mcp-server by expenselm

      expenselm-mcp-serverofficial

      expenselm
      F
      license
      A
      quality
      D
      maintenance
      MCP server for ExpenseLM, a GenAI powered expense management application. Enables AI agents to access expense data for recording, insights, and advice.
      10
      1
      -

    • gov-mcp

      liuhaotian2024-prog
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enforces runtime governance on AI agent actions — file access, command execution, delegation chains, and permission escalation.
      MIT

    • 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

    • clawvault

      andrewszk
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for ClawVault - an AI agent payment security layer that enables Claude to request payments, check limits, and manage transactions with configurable rules.
      74 npm
      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

    A3.7/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct operation: wallet management, agent control, spend authorization, proxy requests, audit, etc. There is no noticeable overlap; even seemingly similar tools like check_balance and list_wallets serve different purposes.

    Naming Consistency4/5

    Tools consistently use snake_case and start with 'valta_'. Most follow a verb_noun pattern (e.g., create_wallet, freeze_agent), though 'proxy_request' is noun_verb, which is a minor deviation. Overall, naming is clear and predictable.

    Tool Count4/5

    With 16 tools, the server is slightly above the ideal 3-15 range, but the number is still reasonable given the domain's complexity. No tool feels superfluous, and the set covers essential operations without being bloated.

    Completeness4/5

    The tool surface covers core workflows: wallet lifecycle (create, list, balance, transfer), agent management (list, get, run, freeze/unfreeze), spending policies (list, set), spend authorization, proxy requests, and audit. Minor gaps exist (no update/delete for wallets or agents), but these are not critical for the primary purpose of spend governance.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources