All servers · Cloud & networking · Payments & accounting · Agent payments (x402)
Lockout-Tagout for agent infrastructure
com.textforagents/lockout-tagout-for-agent-infrastructure · v1.0.0
New (7 days)
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-03-26 |
| Rank score | — |
| Declared risk | Not declared (tools carry no read/destructive hints) |
| Capabilities declared | tools |
| Tool definitions | 2 tools · with description 100% · input schema is an object 100% · read/destructive hints 0% |
Description written by the publisher, not verified
Personal-lock maintenance isolation for agent infrastructure: hasp-quorum refusal + try-start proof.
Connect
streamable-http · https://textforagents.com/products/lockout-tagout-for-agent-infrastructure/mcp
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"
}
}
}Tools as reported by the server
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)
JSON · Text for agents · Registry updated 2026-10-22