Remote MCP · Endpoint
Datoka API MCP server
No. Datoka API answered an MCP handshake 6 days ago.
UpLast checked 6 days ago
Server URL
https://datoka-api.bhazarstudio.workers.dev/mcp
The last check completed an MCP handshake.
- Registry name
- dev.workers.bhazarstudio.datoka-api/api
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 107 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 15 checks
- Described by its publisher as
- Signed API declarations for agent handoffs. Free demo and verification; receipts cost 0.002 USDC.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 6 days ago | Handshake completed | 107 ms |
| 7 days ago | Handshake completed | 1.40 s |
| 7 days ago | Handshake completed | 387 ms |
| 9 days ago | Handshake completed | 345 ms |
| 10 days ago | Handshake completed | 325 ms |
| 11 days ago | Handshake completed | 634 ms |
| 12 days ago | Handshake completed | 440 ms |
| 13 days ago | Handshake completed | 355 ms |
| 15 days ago | Handshake completed | 606 ms |
| 17 days ago | Handshake completed | 599 ms |
| 20 days ago | Handshake completed | 307 ms |
| 22 days ago | Handshake completed | 323 ms |
| 25 days ago | Handshake completed | 575 ms |
| 26 days ago | Handshake completed | 314 ms |
| 29 days ago | Handshake completed | 340 ms |
| 31 days ago | Handshake completed | 314 ms |
| 32 days ago | Handshake completed | 345 ms |
| 34 days ago | Handshake completed | 413 ms |
| 35 days ago | Handshake completed | 344 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 24 responding of 24.
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 Datoka API and makes no claim about it beyond what these checks measured.