Remote MCP · Endpoint

TokenOS dApp Builder MCP server

No. TokenOS dApp Builder answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://tokenos.ai/api/mcp/apps/dapp-builder

The last check completed an MCP handshake.

Registry name
ai.tokenos/dapp-builder
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
7.31 s
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Idea to buildable dApp spec
Listing
From the official MCP registry (active).
Recent checks of TokenOS dApp Builder
CheckedResultHandshake
1 hour agoHandshake completed7.31 s
2 days agoHandshake completed437 ms
5 days agoHandshake completed163 ms
7 days agoHandshake completed255 ms
9 days agoHandshake completed164 ms
11 days agoHandshake completed254 ms
13 days agoHandshake completed271 ms
16 days agoHandshake completed152 ms
18 days agoHandshake completed141 ms
19 days agoHandshake completed503 ms
21 days agoHandshake completed451 ms
22 days agoHandshake completed420 ms
23 days agoHandshake completed815 ms
26 days agoHandshake completed390 ms

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

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 TokenOS dApp Builder and makes no claim about it beyond what these checks measured.