Skip to main content
Glama
Keesan12

MartinLoop — Stop Runaway Loops, Bad Code & Token Waste

Related Servers

Alternatives to MartinLoop — Stop Runaway Loops, Bad Code & Token Waste

Related Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Local Cost Guard and runtime guardrails for AI agents in Claude Code.
    99 npm
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables autonomous agents to enforce financial guardrails by tracking real-time token burn and cost velocity, automatically throttling or freezing execution when budgets are exceeded. It also blocks destructive shell commands, prompt injections, and runaway planning loops while sanitizing outputs before they are returned.
    7
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables agents to track real-time token spend and cost velocity, automatically throttle or freeze execution when budgets are exceeded, and enforce sandbox and safety guardrails.
    7
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Enforces policy controls for AI agents, including spend limits, action approvals, kill switch, scoped credentials, dry-run diffs, loop prevention, and auditable hash-chained logs.
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Stop runaway agents. One gateway in front of all your agent traffic — MCP tools and LLM models — one budget, one kill switch. Sits between AI clients (Cursor, Claude Desktop, Windsurf) and remote MCP servers / OpenAI-compatible model APIs; hard token budgets; a single static Go binary.
    1
    Apache 2.0

TDQS

A3.7/5.0

Scored across 24 tools

Disambiguation3/5

Several tools have overlapping purposes: martin_get_run, martin_status, martin_run_dossier, martin_dossier, and martin_inspect all read run data with subtle differences in format and depth. The descriptions try to disambiguate with 'do not use' guidance, but an agent could easily confuse martin_dossier vs martin_run_dossier vs martin_get_run.

Naming Consistency4/5

Most tools follow a consistent martin_<verb>_<noun> pattern (martin_get_run, martin_create_pr, martin_review_pr). Minor deviations exist: martin_doctor, martin_arcade, and martin_arcade_status use noun-only or different structures, and martin_status vs martin_get_status inconsistency appears in descriptions.

Tool Count3/5

24 tools is at the high end of acceptable for a complex run-management system, but the count feels inflated by near-duplicate read surfaces (dossier, run_dossier, get_run, inspect, status, logs, verification_results). A leaner set of 15-18 tools would cover the same functionality.

Completeness4/5

The lifecycle is well covered: estimate, plan, preflight, run, pause/cancel/continue, status, verification, eval, PR creation/review. Minor gaps include no explicit tool for listing attempts across runs or deleting/archiving runs, but agents can work around these.

Maintenance

ActivityActive
ResponsivenessSlow