Lockout-Tagout for agent infrastructure
Personal-lock maintenance isolation for agent infrastructure: hasp-quorum refusal + try-start proof.
Should I use this
Quality & Safety
A
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
~187Tokens (tool definitions)
~633 BTypical response size
Minimal attention impact (0.15% of 128k context)
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"lockout-tagout-for-agent-infrastructure": {
"url": "https://textforagents.com/products/lockout-tagout-for-agent-infrastructure/mcp"
}
}
}Remote endpoints
https://textforagents.com/products/lockout-tagout-for-agent-infrastructure/mcpstreamable-httpWhat it can do
Tool inventory
Tools (2)
🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟡lock_check(component)
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)
Input Schema
{
"type": "object",
"properties": {
"component": {
"type": "string"
}
},
"required": [
"component"
]
}⚪place_lock(component, scope, energy_sources, expected_duration_s, shared, ...)
Place a personal lock + try-start proof ($0.05 x402 via the X-PAYMENT header, first placement free once per operator)
Input Schema
{
"type": "object",
"properties": {
"component": {
"type": "string"
},
"scope": {
"type": "string"
},
"energy_sources": {
"type": "array",
"items": {
"type": "string"
}
},
"expected_duration_s": {
"type": "number"
},
"shared": {
"type": "boolean"
},
"adapter_class": {
"type": "string"
},
"adapter_target": {
"type": "string"
}
},
"required": [
"component",
"scope",
"energy_sources"
]
}Community
Evidence
Recent observations
verifiedversion not recorded2 tools