Stage Completeness Receipts

com.textforagentsPublished by textforagents.comOfficial publisherv1.0.1Updated Oct 29, 2026

Signed stage-completeness receipts: proof that a pipeline zero is a real zero, not a failed scan.

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

VerifiedStreamable HTTPWeb executableSecurity & MonitoringData & Analytics

Overview

AI-generated overview

Issues, verifies and fetches signed stage-completeness receipts, so an assistant can show a pipeline's zero result came from a real scan rather than a failed…

What you can do
  • Issue a signed stage-completeness receipt for a pipeline stage, with the first receipt free per operator.
  • Verify a receipt's signature, freshness and hash or parameter match, and get the downstream conclusion.
  • Run an independent sampled re-scan of a claimed source, capped at 5% of the sample, as a coarse-fault tripwire.
  • Fetch your own receipt by id.
When to use it
Useful when a pipeline reports zero findings and you need evidence that the scan actually ran, or when you must check someone else's completeness claim before trusting a downstream decision.
Requirements
Remote streamable HTTP endpoint at textforagents.com; no packages, environment variables or headers declared. Paid calls use x402, so a payment-capable client is needed beyond the free first receipt.
Before you install
Most tools cost money via x402: $0.02 per issued receipt after the free one, $0.005 per verification and $0.25 per coverage probe. Receipts are signed attestations, so treat them as evidence about a claimed source, not a guarantee of full coverage.

Installation

In SourceWeft

  1. Open Stage Completeness Receipts 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%2Fstage-completeness-receipts/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": {
    "stage-completeness-receipts": {
      "type": "http",
      "url": "https://textforagents.com/products/stage-completeness-receipts/mcp"
    }
  }
}

Tools

4

issue_receipt

Issue a signed stage-completeness receipt. First receipt free once per operator; then x402 $0.02.

Parametersttlquerystagerequiredsourcerequiredlistingrequiredmatchedexpectedscan_status

verify_receipt

Verify a receipt (signature, freshness, hash/parameter match) and get the downstream conclusion. x402 $0.005/check.

Parametersreceiptrequiredexpected_queryexpected_sourcepresented_listing

coverage_probe

Independent sampled re-scan of a claimed source, sample hard-capped at 5%. Coarse-fault tripwire. x402 $0.25/probe.

Parametersreceipt_idsource_listingrequiredsample_fraction

get_receipt

Fetch your own receipt by id.

Parametersreceipt_idrequired

Version history

2
  1. v1.0.1LatestOct 29, 2026
  2. v1.0.0Oct 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