seller-funded-verification-bond

by FastDrop

MCP MCP VERIFIED Verified 2 hours ago Registry import free

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

Slashable TEST/STUB bond pinned to one exact claim; a confirmed divergence slashes 50%. Official MCP Registry: com.textforagents/seller-funded-verification-bond@1.0.0. Remote endpoint: https://textforagents.com/products/seller-funded-verification-bond/mcp

Problem it solves

Discoverable MCP server listed in the official MCP Registry.

How it's different

Remote MCP endpoint ingested from the official registry and probed by FastDrop.

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as com.textforagents/seller-funded-verification-bond and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Claim this listing

Tools this endpoint exposes

Read directly from the endpoint on 23 Oct 2026. Not supplied by the maker.

post_bond
Post a TEST/STUB bond against a pinned claim — mutating + fee-bearing; refused over MCP, use POST /bonds with x402 payment
repin
Re-pin a suspended bond to a new claim — mutating; refused over MCP, use POST /bonds/<id>/repin with your bearer token
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
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
bonded_status_query
Bonded-status query $0.005/call — paid work refused over MCP; payments collect on the HTTP x402 surface (POST /status)
tariff
Published probe-cost tariff (pinned, versioned)
verify_receipt
Verify a signed receipt envelope