Live-Payload Conformance Probes

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

Live-payload conformance probes with signed receipts: ABSENT/EMPTY/PARTIAL/COMPLETE/BROKEN.

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsData & Analytics

Overview

AI-generated overview

Remote MCP server that runs a live-payload conformance check against a registered declared schema and returns a signed receipt.

What you can do
  • Run a conformance check of a live payload against a registered declared schema
  • Get back a signed receipt with a status of ABSENT, EMPTY, PARTIAL, COMPLETE or BROKEN
When to use it
Useful when you need an auditable, receipt-backed verdict on whether a live payload matches its declared schema, for example in data-contract or integration checks.
Requirements
Remote streamable HTTP endpoint at textforagents.com; no authentication, environment variables or headers are declared. Each check is paid: $0.01 per check via x402, so a payment-capable client is needed.
Before you install
Each check costs $0.01 through x402, so calls spend money. The payload being checked is sent to a third-party service. No authentication is declared, so anyone with the endpoint can invoke it.

Installation

In SourceWeft

  1. Open Live-Payload Conformance Probes 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%2Flive-payload-conformance-probes/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": {
    "live-payload-conformance-probes": {
      "type": "http",
      "url": "https://textforagents.com/products/live-payload-conformance-probes/mcp"
    }
  }
}

Tools

1

conformance_check

Run one live-payload conformance check against a registered declared schema; returns a signed receipt. $0.01/check via x402.

Parameterstoolrequiredserver_idrequired

Version history

1
  1. v1.0.0LatestOct 20, 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