Remote MCP · Endpoint

TapeAPI: signed BNB Chain reads MCP server

No. TapeAPI: signed BNB Chain reads answered an MCP handshake 59 minutes ago.

UpLast checked 59 minutes ago

Server URL

https://api.tapeapi.fun/mcp

The last check completed an MCP handshake.

Registry name
io.github.BruceLanLan/tapeapi
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
109 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Signed BNB Chain reads (balances, tokens, NFTs, prices, TapeOut names) with verifiable receipts
Listing
From the official MCP registry (active).
Recent checks of TapeAPI: signed BNB Chain reads
CheckedResultHandshake
59 minutes agoHandshake completed109 ms
9 days agoHandshake completed111 ms
10 days agoHandshake completed96 ms
11 days agoHandshake completed102 ms
12 days agoHandshake completed84 ms
14 days agoHandshake completed124 ms
14 days agoHandshake completed83 ms
15 days agoHandshake completed85 ms
17 days agoHandshake completed907 ms
19 days agoHandshake completed121 ms
21 days agoHandshake completed89 ms
24 days agoHandshake completed213 ms
26 days agoHandshake completed123 ms
28 days agoHandshake completed111 ms

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

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 TapeAPI: signed BNB Chain reads and makes no claim about it beyond what these checks measured.