Skip to main content
Glama
tstockham96

rail-mcp

by tstockham96
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to rail-mcp

No user-submitted related servers found.

    Related Servers

    • sellable-mcp

      HarshDubey23
      A
      license
      A
      quality
      A
      maintenance
      Lets any MCP-compatible agent shop for catalog items by SKU and quantity under a user-set budget, category and expiry limit. Purchases flow through deterministic server-side pricing, policy checks, single-use approval binding and a recoverable execution state machine, so a compromised or manipulated model cannot move money.
      10
      1
      MIT

    • clearance-mcp

      Nauti-Labs
      A
      license
      A
      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.
      9
      4 npm
      MIT

    • agent-budget

      nyx-builds
      A
      license
      Not graded
      quality
      C
      maintenance
      Budget management and cost tracking MCP server for autonomous agents, enabling budget creation, cost recording, spending projections, and alert rules.
      MIT

    • cicash

      Cee62
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for CIcash, a budget system that lets AI agents spend within bounded, expiring, revocable budgets. Provides tools for budget checks, quotes, payments, delegation, and receipts, with the private key kept server-side.
      Apache 2.0
    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.3/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool maps to a distinct resource+action: budgets (set/get), proposals (propose/list/decide), and receipts (get/refund). Descriptions explicitly clarify boundaries, e.g. set_budget vs propose_purchase vs decide_proposal, leaving no real overlap.

    Naming Consistency5/5

    Every tool follows a clean verb_noun snake_case pattern (set_budget, get_budget, propose_purchase, list_proposals, decide_proposal, get_receipts, refund_receipt). No mixing of conventions.

    Tool Count5/5

    Seven tools is well-scoped for a spend-governance ledger, each covering a necessary stage of the budget/proposal/receipt lifecycle with no filler.

    Completeness4/5

    Covers the full lifecycle: budget set/read, proposal create/list/decide, receipt read/refund. Minor gaps like filtering or clearing stale proposals exist but core workflows have no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources