Lockout-Tagout for agent infrastructure
com.textforagents/lockout-tagout-for-agent-infrastructure · v1.0.0
Personal-lock maintenance isolation for agent infrastructure: hasp-quorum refusal + try-start proof.
Connect Remote server
claude mcp add --transport http lockout-tagout-for-agent-infrastructure https://textforagents.com/products/lockout-tagout-for-agent-infrastructure/mcp
{
"mcpServers": {
"lockout-tagout-for-agent-infrastructure": {
"url": "https://textforagents.com/products/lockout-tagout-for-agent-infrastructure/mcp"
}
}
}
{
"servers": {
"lockout-tagout-for-agent-infrastructure": {
"type": "http",
"url": "https://textforagents.com/products/lockout-tagout-for-agent-infrastructure/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://textforagents.com/products/lockout-tagout-for-agent-infrastructure/mcp
Tools 2 found in our last check
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 proven wallet)
Details
| Endpoint | https://textforagents.com/products/lockout-tagout-for-agent-infrastructure/mcp (Streamable HTTP) |
| First published | 22 Oct 2026 |
| Last updated | 22 Oct 2026 |
| Registry name | com.textforagents/lockout-tagout-for-agent-infrastructure |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
