Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Single-Use Agent Burn Receipt

REMOTE · TEXTFORAGENTS.COM

Task-bound disposable agent minting with canary-shard burn receipts.

56 Trust /100

Last scanned (12 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 22 Oct 2026.

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability46
  • AI-judged instruction clarity (poor).Fail
  • Tool/resource definitions use about 302 tokens (~43/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail

Unverified: 1 category

A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 22 Oct 26 56

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Oct 2026 · Probed https://textforagents.com/products/single-use-agent-burn-receipt/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=textforagents.com CN=YE2,O=Let's Encrypt,C=US 15 Oct 2026 13 Jan 2027 ECDSA 256 ECDSA-SHA384 66d021cf7bcd281266ac6de4cea43642f85
SANs: textforagents.com, www.textforagents.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of textforagents.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
textforagents.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy interest-cohort=(), geolocation=(), microphone=(), camera=(), payment=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://textforagents.com/products/single-use-agent-burn-receipt/mcp Verified 200
http (plaintext) http://textforagents.com/products/single-use-agent-burn-receipt/mcp HTTPS enforced 301 https://textforagents.com/products/single-use-agent-burn-receipt/mcp
MCP tools · 7 exposed · ~302 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
burn_burn ~38

Burn an agent; signed receipt only when every shard is accounted.

NameTypeReqDescription
child_receiptsarray––
credentialstringyes–

No output schema declared.

No examples provided.

burn_gate ~46

Requester gate: accept a deliverable only with a verifying receipt.

NameTypeReqDescription
deliverable_hashstring––
receiptobjectyes–
task_specobject––

No output schema declared.

No examples provided.

burn_mint ~61

Mint a task-bound disposable agent; 12 canary shards planted. $0.25/cycle, first free once per operator.

NameTypeReqDescription
task_specobjectyes–
tool_grantsarray––
ttl_secondsnumber––

No output schema declared.

No examples provided.

burn_resurface_scan ~39

Scan a presented artifact for resurfaced shards; a match revokes standing.

NameTypeReqDescription
artifactstringyes–
receiptobjectyes–

No output schema declared.

No examples provided.

burn_run ~40

Run the bound task with a minted credential.

NameTypeReqDescription
credentialstringyes–
secret_inputstring––
task_specobjectyes–

No output schema declared.

No examples provided.

burn_spawn ~37

Spawn a child; custody of one spawn-grant shard transfers.

NameTypeReqDescription
child_task_specobjectyes–
credentialstringyes–

No output schema declared.

No examples provided.

burn_verify ~41

Verify a burn receipt against the persistent registry.

NameTypeReqDescription
deliverable_hashstring––
receiptobjectyes–
task_specobject––

No output schema declared.

No examples provided.

Install

How do I install the Single-Use Agent Burn Receipt MCP server?

Single-Use Agent Burn Receipt is a hosted endpoint at https://textforagents.com/products/single-use-agent-burn-receipt/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · textforagents.com

# add to Claude Code
claude mcp add --transport http com-textforagents-single-use-agent-burn-receipt 'https://textforagents.com/products/single-use-agent-burn-receipt/mcp'
Common questions

What is the Single-Use Agent Burn Receipt MCP server?

Single-Use Agent Burn Receipt is an MCP server listed in the public MCP registry as com.textforagents/single-use-agent-burn-receipt. Task-bound disposable agent minting with canary-shard burn receipts. This page covers its hosted endpoint (https://textforagents.com/products/single-use-agent-burn-receipt/mcp).

Is the Single-Use Agent Burn Receipt MCP server safe to use?

Single-Use Agent Burn Receipt scores 56 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Single-Use Agent Burn Receipt MCP server expose?

Single-Use Agent Burn Receipt exposes 7 tools: burn_mint, burn_run, burn_spawn, burn_burn, burn_verify, and 2 more. Their descriptions and schemas cost roughly 302 tokens of context every time the server is loaded.

Does the Single-Use Agent Burn Receipt MCP server require authentication?

No. We connected to Single-Use Agent Burn Receipt without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Single-Use Agent Burn Receipt MCP server still maintained?

Single-Use Agent Burn Receipt is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.