Seller Funded Verification Bond

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

Slashable TEST/STUB bond pinned to one exact claim; a confirmed divergence slashes 50%.

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

VerifiedStreamable HTTPWeb executableFinance Security & Monitoring

Server details

Identifier: com.textforagents/seller-funded-verification-bond
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Oct 23, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to textforagents.com, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.textforagents%2Fseller-funded-verification-bond.svg)](https://sourceweft.com/mcp/com.textforagents%2Fseller-funded-verification-bond?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Remote MCP endpoint for a TEST/STUB seller-funded verification bond: read the tariff, verify signed receipts, and see which bond actions are refused over MCP.

What you can do: Read the published, versioned probe-cost tariff for a bond
Verify a signed receipt envelope
Attempt bond actions that are refused over MCP: posting a fee-bearing bond, re-pinning a suspended bond, filing a probe result or drawdown, and querying per-operator slash status
Attempt the paid bonded-status query, which is also refused over MCP and must go through the HTTP x402 payment surface
When to use it: Only worth adding if you are evaluating or testing this stub bond service and want an assistant to read its tariff and check receipt envelopes; the state-changing and paid operations are not available through MCP, so it cannot be used to actually post, re-pin, file or query bonds.
Requirements: A remote streamable HTTP endpoint at textforagents.com; no package, environment variables or headers are declared. The refused operations are documented as requiring a bearer token or x402 payment on the HTTP API instead.

Before you install

The bond is explicitly a TEST/STUB, not a production instrument. Posting a bond is fee-bearing and the paid status query costs $0.005 per call, but both are refused over MCP and must be done on the HTTP surface with x402 payment. Mutating actions (re-pin, probe result, slash status) need a bearer token and are also refused over MCP. A confirmed divergence slashes 50% of the bond.

Installation

In SourceWeft

Open Seller Funded Verification Bond in the dashboard and add it to a workspace.
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%2Fseller-funded-verification-bond/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": {
    "seller-funded-verification-bond": {
      "type": "http",
      "url": "https://textforagents.com/products/seller-funded-verification-bond/mcp"
    }
  }
}

Tools

post_bond

Post a TEST/STUB bond against a pinned claim — mutating + fee-bearing; refused over MCP, use POST /bonds with x402 payment

Takes no parameters.

repin

Re-pin a suspended bond to a new claim — mutating; refused over MCP, use POST /bonds/<id>/repin with your bearer token

Takes no parameters.

file_probe_result

File a probe result / drawdown against a bond — mutating; refused over MCP, use POST /bonds/<id>/probe-result with your bearer token

Takes no parameters.

slash_status

Slash status of a bond — per-operator scoped; refused over MCP (no auth), use POST /bonds/<id>/slash-status with your bearer token

Takes no parameters.

bonded_status_query

Bonded-status query $0.005/call — paid work refused over MCP; payments collect on the HTTP x402 surface (POST /status)

Parametersbond_idrequired

tariff

Published probe-cost tariff (pinned, versioned)

Takes no parameters.

verify_receipt

Verify a signed receipt envelope

Parametersreceiptrequired

Version history

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.