English Français العربية

Lockout-Tagout for agent infrastructure

Official registry Cloud and DevOps

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

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http lockout-tagout-for-agent-infrastructure 'https://textforagents.com/products/lockout-tagout-for-agent-infrastructure/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "lockout-tagout-for-agent-infrastructure": {
            "type": "http",
            "url": "https://textforagents.com/products/lockout-tagout-for-agent-infrastructure/mcp"
        }
    }
}

Frequently asked questions

What is Lockout-Tagout for agent infrastructure?

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

How do I install Lockout-Tagout for agent infrastructure?

It runs as a remote server. In Claude Code: claude mcp add --transport http lockout-tagout-for-agent-infrastructure 'https://textforagents.com/products/lockout-tagout-for-agent-infrastructure/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Lockout-Tagout for agent infrastructure need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Who maintains Lockout-Tagout for agent infrastructure?

It is published by com.textforagents. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.