com.textforagents/seller-funded-verification-bond
com.textforagents/seller-funded-verification-bondtextforagents.comstreamable-httpv1.0.0Scanned
Slashable TEST/STUB bond pinned to one exact claim; a confirmed divergence slashes 50%.
7 tools: 5 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 1
- No findings
Anlyon alternative
5 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Changes things 5Claude Code: ask
file_probe_resultFile a probe result / drawdown against a bond — mutating; refused over MCP, use POST /bonds/<id>/probe-result with your bearer tokenNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it File a probe result / drawdown against a bond — mutating; refused over MCP, use POST /bonds/<id>/probe-result with your bearer token
post_bondPost a TEST/STUB bond against a pinned claim — mutating + fee-bearing; refused over MCP, use POST /bonds with x402 paymentCan send data outNo findings
Why it is in this group
- The name "post_bond" says "post": a word for a change.
What it can reach
- outboundThe name "post_bond" says "post": it sends or publishes something to other people.
Description, as the server wrote it Post a TEST/STUB bond against a pinned claim — mutating + fee-bearing; refused over MCP, use POST /bonds with x402 payment
repinRe-pin a suspended bond to a new claim — mutating; refused over MCP, use POST /bonds/<id>/repin with your bearer tokenNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Re-pin a suspended bond to a new claim — mutating; refused over MCP, use POST /bonds/<id>/repin with your bearer token
tariffPublished probe-cost tariff (pinned, versioned)No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Published probe-cost tariff (pinned, versioned)
verify_receiptVerify a signed receipt envelopeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Verify a signed receipt envelope
Only reads 2Show 2 read-only tools
bonded_status_queryBonded-status query $0.005/call — paid work refused over MCP; payments collect on the HTTP x402 surface (POST /status)Reads text others writeNo findings
Why it is in this group
- The name "bonded_status_query" says "status": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "http": it reads web pages, which anyone can write.
Description, as the server wrote it Bonded-status query $0.005/call — paid work refused over MCP; payments collect on the HTTP x402 surface (POST /status)
slash_statusSlash status of a bond — per-operator scoped; refused over MCP (no auth), use POST /bonds/<id>/slash-status with your bearer tokenReads text others writeNo findings
Why it is in this group
- The name "slash_status" says "status": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "post": it reads posts, which other people can write.
Description, as the server wrote it Slash status of a bond — per-operator scoped; refused over MCP (no auth), use POST /bonds/<id>/slash-status with your bearer token
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http seller-funded-verification-bond https://textforagents.com/products/seller-funded-verification-bond/mcpclaude mcp add --transport http seller-funded-verification-bond https://textforagents.com/products/seller-funded-verification-bond/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__seller-funded-verification-bond__slash_status",
"mcp__seller-funded-verification-bond__bonded_status_query"
],
"ask": [
"mcp__seller-funded-verification-bond__post_bond",
"mcp__seller-funded-verification-bond__repin",
"mcp__seller-funded-verification-bond__file_probe_result",
"mcp__seller-funded-verification-bond__tariff",
"mcp__seller-funded-verification-bond__verify_receipt"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as seller-funded-verification-bond. Review it before you use it.
Capability tags behind 3 rules
- mcp__seller-funded-verification-bond__post_bond outbound
- mcp__seller-funded-verification-bond__slash_status untrusted-input
- mcp__seller-funded-verification-bond__bonded_status_query untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://anlyon.dev/api/v1/servers/com.textforagents/seller-funded-verification-bond/verify?hash=f609262d4c5834a0d45d1e734ae276426bb456ab0170b893f7405da4892108ff" | jq -e '.changed == false'Pinned hash f609262d4c58, from Oct 23, 2026, 03:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/com.textforagents/seller-funded-verification-bond/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/com.textforagents/seller-funded-verification-bond)Source: MCP Registry. Synced Oct 23, 2026, 03:17 UTC.