Skip to main content
Glama

KARTA — spend control for AI agents

Server Details

Task envelope, budget ledger, kill switch and signed receipts for agents that pay.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
mrpkk/onchain-ai-agent
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a distinct action-resource pair: check_spend evaluates a proposal, get_envelope reads state, envelope_evidence produces a verifiable bundle, kill_envelope stops, open_envelope creates, and policy_rules explains the rule set. The descriptions make the boundaries between check_spend, get_envelope, and envelope_evidence explicit (verdict vs. state vs. evidence pack).

Naming Consistency4/5

Four tools follow a clear verb_noun pattern (check_spend, get_envelope, kill_envelope, open_envelope), but envelope_evidence and policy_rules use noun-first naming. The deviation is minor and still readable, so it does not seriously hinder selection.

Tool Count5/5

Six tools is well-scoped for a spend-control lifecycle: open, check, inspect, evidence, kill, and policy explanation. Every tool earns its place without bloat or thinness.

Completeness3/5

The core lifecycle is covered, but there is no way to list or enumerate envelopes, no explicit record_spend tool despite evidence returning recorded spends, and no update/adjust operation for an envelope. These are notable gaps that could force agents into dead ends when managing multiple envelopes.

Available Tools

6 tools
check_spendCheck a spend against a task envelopeB
Read-onlyIdempotent
Inspect

Check whether a proposed agent spend is inside a task envelope. Returns verdict, rule, reason, counterfactual and next. No state is stored.

Inputs: payee (required), amount (required), envelope (required), calls_so_far, +2 more. Returns: result

envelope_evidenceEvidence pack for an envelopeB
Read-onlyIdempotent
Inspect

Return an evidence bundle for one envelope: state, every recorded spend, the stop record and a sha256 of the whole pack that anyone can recompute. Read-only.

Inputs: envelope_id (required). Returns: result

get_envelopeRead an envelopeA
Read-onlyIdempotent
Inspect

Return an envelope's state: budget, per-call cap, calls used, spent, remaining, allowlist and expiry. Read-only.

Inputs: envelope_id (required). Returns: result

kill_envelopeStop an envelopeA
DestructiveIdempotent
Inspect

Stop one task envelope immediately: no further spend is approved for it, the reason is recorded with a timestamp. Idempotent — the first reason wins.

Inputs: envelope_id (required), reason. Returns: result

open_envelopeOpen a task envelopeAInspect

Create a signed budget envelope for one task: total budget, per-call cap, call count, allowlisted payees, subscription rule, expiry. Stores it in this server's local ledger (no funds move, no keys). Returns the envelope id. Capped at 30 envelopes/hour per server.

Inputs: calls_max (required), budget_total (required), per_call_max (required), allowlist, +4 more. Returns: result

policy_rulesList policy rulesA
Read-onlyIdempotent
Inspect

List the deterministic rules a spend is checked against (E01-E08) with the order they are applied and the meaning of each. Read-only, no state.

Inputs: no named parameters. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.