Lockout-Tagout for agent infrastructure

com.textforagentsPublished by textforagents.comOfficial publisherv1.0.0Updated Oct 26, 2026

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

The publisher's own server: Agent NOTAMs: hazard bulletins for agents

VerifiedStreamable HTTPWeb executableCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server for personal-lock maintenance isolation on agent infrastructure: check locks on a component and place a lock with a try-start proof.

What you can do
  • Check locks on a component, including hasp-quorum refusal status, for a per-query fee.
  • Place a personal lock on a component and obtain a try-start proof; the first placement per operator is free.
  • Both tools are paid per call through an x402 payment sent in the X-PAYMENT header on the JSON-RPC POST.
When to use it
Use it when an assistant or operator needs to coordinate maintenance isolation on agent infrastructure, verifying whether a component is locked before acting, or recording a personal lock with proof that a start attempt was refused.
Requirements
A remote endpoint at textforagents.com over streamable HTTP; no packages, environment variables or headers are declared for authentication. Each call requires an x402 payment supplied in the X-PAYMENT header, so a payment-capable client or wallet is needed.
Before you install
Calls cost money: $0.01 per lock check and $0.05 per lock placement, paid via the X-PAYMENT header, so automated loops can spend funds. Placing a lock changes shared state on the component and may block other operators until released. Payment credentials travel in a request header.

Installation

In SourceWeft

  1. Open Lockout-Tagout for agent infrastructure in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.textforagents%2Flockout-tagout-for-agent-infrastructure/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "lockout-tagout-for-agent-infrastructure": {
      "type": "http",
      "url": "https://textforagents.com/products/lockout-tagout-for-agent-infrastructure/mcp"
    }
  }
}

Tools

2

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)

Parameterscomponentrequired

place_lock

Place a personal lock + try-start proof ($0.05 x402 via the X-PAYMENT header, first placement free once per operator)

Parametersscoperequiredsharedcomponentrequiredadapter_classadapter_targetenergy_sourcesrequiredexpected_duration_s

Version history

1
  1. v1.0.0LatestOct 23, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Textforagents integrations