Skip to main content
Glama
Sign In
spendshield

spendshield

by felixpg13-glitch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to spendshield

No user-submitted related servers found.

    Related Servers

    • spendveto

      revanthrajeev
      A
      license
      Not graded
      quality
      B
      maintenance
      Governs AI agents' spending by enforcing budgets, approvals, and kill switches before any payment, providing an MCP interface for tool calls with policy checks.
      377 npm
      Apache 2.0

    • Boundra

      gobeyondfj-cmd
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to evaluate every payment intent against user-signed, on-chain-anchored policies before money moves, returning allow, deny, or human-approval verdicts. Provides policy versioning, revocation, spend reports, and audit trails through MCP tools that agents cannot alter without the owner's key.
      1
      Apache 2.0

    • Budget Governor

      mightbesaad
      A
      license
      Not graded
      quality
      C
      maintenance
      Budget & cost control for AI agents: hard per-agent spend caps, rate limits, idempotency, and human-in-the-loop approval — enforced before each LLM call, not after the invoice. One hosted MCP endpoint (no proxy or self-hosting), settled via x402 (USDC on Base).
      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.8/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a clearly distinct operation: status is a live snapshot, audit is historical records, reset is session state management, protect gates a spend, and secret_get retrieves a credential. No two tools plausibly serve the same purpose, and the descriptions make the boundaries obvious.

    Naming Consistency4/5

    The tools are all lowercase snake_case and mostly follow a domain-prefix pattern, with four sharing spend_ and one using secret_. The slight inconsistency is that the second segment mixes nouns and verbs, and secret_get breaks away from the spend_ namespace, so it is not as uniform as a strict verb_noun convention.

    Tool Count5/5

    Five tools is well-scoped for a spending-defense utility: status, audit, reset, protect, and secret retrieval each cover a necessary function without redundancy. There are no filler tools or obvious bloat.

    Completeness4/5

    The set covers the core lifecycle well: protect a spend, inspect status, review audit trails, reset session amounts, and safely retrieve secrets. The main gap is configuration management such as setting budgets, whitelists, or blacklists, but agents can still work within the existing guardrails.

    Maintenance

    ActivitySlowing
    ResponsivenessResponsive

    Resources