Lockout-Tagout for agent infrastructure

Name: Lockout-Tagout for agent infrastructure
Author: com.textforagents

MCP serverMCP

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

by com.textforagentsv1.0.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"lockout-tagout-for-agent-infrastructure","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability11/11 checks ok

30 days ago

when	check	result	http	latency	detail
2 h ago	mcp initialize	ok	200	255 ms	server lockout-tagout 1.1.0 · protocol 2025-03-26 · 2 tools
9 h ago	mcp initialize	ok	200	80 ms	server lockout-tagout 1.1.0 · protocol 2025-03-26 · 2 tools
17 h ago	mcp initialize	ok	200	258 ms	server lockout-tagout 1.1.0 · protocol 2025-03-26 · 2 tools
25 h ago	mcp initialize	ok	200	237 ms	server lockout-tagout 1.1.0 · protocol 2025-03-26 · 2 tools
32 h ago	mcp initialize	ok	200	78 ms	server lockout-tagout 1.1.0 · protocol 2025-03-26 · 2 tools
2 d ago	mcp initialize	ok	200	236 ms	server lockout-tagout 1.1.0 · protocol 2025-03-26 · 2 tools
2 d ago	mcp initialize	ok	200	273 ms	server lockout-tagout 1.1.0 · protocol 2025-03-26 · 2 tools
2 d ago	mcp initialize	ok	200	76 ms	server lockout-tagout 1.1.0 · protocol 2025-03-26 · 2 tools
3 d ago	mcp initialize	ok	200	84 ms	server lockout-tagout 1.1.0 · protocol 2025-03-26 · 2 tools
3 d ago	mcp initialize	ok	200	258 ms	server lockout-tagout 1.1.0 · protocol 2025-03-26 · 2 tools

Tools observed via MCP handshake

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

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrycom.textforagents/lockout-tagout-for-agent-infrastructure

first seen 3 d ago · fetched 3 d agoopen ↗

Field history (5 recent events)

3 d ago · declared · summary → "Personal-lock maintenance isolation for agent infrastructure: hasp-quorum refusal + try-start proof."
3 d ago · declared · description → "Personal-lock maintenance isolation for agent infrastructure: hasp-quorum refusal + try-start proof."
3 d ago · declared · publisherName → "com.textforagents"
3 d ago · declared · version → "1.0.0"
3 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from