Skip to main content
Glama
Sign In

Lockout-Tagout for agent infrastructure

by com.textforagents
OverviewDiscussionsAdmin

Server Details

Personal-lock maintenance isolation for agent infrastructure: hasp-quorum refusal + try-start proof.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-03-26
URL
ChatGPT
–
Claude
–

TDQS

C2.5/5.0

Scored across 2 tools

Disambiguation5/5

lock_check and place_lock have clearly distinct purposes: one inspects existing locks, the other creates a lock. There is little risk of confusing them.

Naming Consistency3/5

Both names use snake_case, but their word order is inconsistent: lock_check is noun_verb while place_lock is verb_noun. The set is readable but not fully predictable.

Tool Count2/5

Only two tools are provided for a lockout-tagout lifecycle. This is too thin for the stated infrastructure purpose and leaves little room for core operations.

Completeness1/5

The surface allows checking locks and placing a lock but has no release/unlock, tagout, ownership, or listing operation. An agent cannot complete the lock lifecycle, which is a severe gap for this domain.

Available Tools

2 tools
lock_checkCInspect

Check locks on a component ($0.01/query x402 — send the payment as the X-PAYMENT header on the JSON-RPC POST, same authorization format as REST)

Inputs: component (required).

place_lockCInspect

Place a personal lock + try-start proof ($0.05 x402 via the X-PAYMENT header, first placement free once per proven wallet)

Inputs: scope (required), component (required), energy_sources (required), shared, +3 more.

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

    • Agent Coherence — Stale Write Guard (FS)

      Agent Coherence — Stale Writeofficial

      Cohexa-ai
      A
      license
      A
      quality
      B
      maintenance
      Coherence guard for shared files: when two agents write the same file, the stale writer is denied instead of silently overwriting, then reacquires and retries. Single-host, TLA+-verified.
      10
      257 PyPI
      13
      Apache 2.0

    • Governed Action Lab

      Kaagemusha
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for governing agent actions: an agent can propose a retry but cannot approve it itself. Deterministic policy allows, holds or refuses each typed action, a held action needs a single-use human approval none of the tools can create, and every run leaves a verifiable receipt.
      1
      MIT
    Try in Browser
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources