79trust / 100

KARTA — spend control for AI agents

by karta.rta.lat in Productivity & SaaS

MCP serverPassing, checked 2 h ago

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

https://karta.rta.lat/mcp
Tools
6
open to any client
Uptime
94.7%
last 30 days
Response time
553 ms
1.9 s slowest 5%
Last check
Passed
2 h ago, next in 5 h

Scan it nowHow to connect

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to connect

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "karta-spend-control-for-ai-agents": {
      "type": "http",
      "url": "https://karta.rta.lat/mcp"
    }
  }
}

6 tools

  • check_spend

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

  • open_envelope

    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.

  • get_envelope

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

  • kill_envelope

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

  • envelope_evidence

    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.

  • policy_rules

    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.

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTime
2 h agoPassed200537 ms
16 h agoPassed2001.9 s
31 h agoPassed200601 ms
46 h agoinitialize returned HTTP 5025021.7 s
3 days agoPassed200526 ms
Show 10 older checks
3 days agoPassed200997 ms
4 days agoPassed200326 ms
4 days agoPassed200729 ms
5 days agoPassed200553 ms
5 days agoPassed200481 ms
6 days agoPassed2001.7 s
6 days agoPassed200386 ms
7 days agoPassed200890 ms
7 days agoPassed200836 ms
8 days agoPassed200528 ms