Remote MCP · Endpoint

Single-Use Agent Burn Receipt MCP server

No. Single-Use Agent Burn Receipt answered an MCP handshake 30 minutes ago.

UpLast checked 30 minutes ago

Server URL

https://textforagents.com/products/single-use-agent-burn-receipt/mcp

The last check completed an MCP handshake.

Registry name
com.textforagents/single-use-agent-burn-receipt
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
70 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Task-bound disposable agent minting with canary-shard burn receipts.
Listing
From the official MCP registry (active).
Recent checks of Single-Use Agent Burn Receipt
CheckedResultHandshake
30 minutes agoHandshake completed70 ms
3 days agoHandshake completed17 ms
13 days agoHandshake completed16 ms
14 days agoHandshake completed21 ms
15 days agoHandshake completed16 ms
16 days agoHandshake completed15 ms
17 days agoHandshake completed15 ms
18 days agoHandshake completed17 ms
19 days agoHandshake completed19 ms
21 days agoHandshake completed16 ms
23 days agoHandshake completed18 ms
25 days agoHandshake completed15 ms
28 days agoHandshake completed25 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Single-Use Agent Burn Receipt and makes no claim about it beyond what these checks measured.