Lockout-Tagout for agent infrastructure

com.textforagents/lockout-tagout-for-agent-infrastructure · v1.0.0 · cloud-and-infra

Lockout-Tagout for agent infrastructure is healthy: it completed an MCP handshake in 455 ms and exposes 2 tools.

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

Endpoint: https://textforagents.com/products/lockout-tagout-for-agent-infrastructure/mcp (streamable-http)

No repository listed · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count2
Latency455 ms
Last checked (UTC)2026-10-23T05:00:17.287Z

Health history

Checked (UTC)StatusLatencyError
2026-10-23T05:00:17.287ZHealthy455

Tools (2)

lock_checkCheck 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)
place_lockPlace a personal lock + try-start proof ($0.05 x402 via the X-PAYMENT header, first placement free once per operator)