Remote MCP · Endpoint
ai.byteask/embedded-docs MCP server
No. ai.byteask/embedded-docs answered an MCP handshake 10 hours ago.
UpLast checked 10 hours ago
Server URL
https://mcp.byteask.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.byteask/embedded-docs
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 473 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Page-cited retrieval for embedded docs, datasheets, MISRA, CMSIS, and RTOS references.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 10 hours ago | Handshake completed | 473 ms |
| 2 days ago | Handshake completed | 477 ms |
| 4 days ago | Handshake completed | 461 ms |
| 5 days ago | Handshake completed | 478 ms |
| 7 days ago | Handshake completed | 475 ms |
| 8 days ago | Handshake completed | 461 ms |
| 9 days ago | Handshake completed | 446 ms |
| 12 days ago | Handshake completed | 480 ms |
| 13 days ago | Handshake completed | 478 ms |
| 15 days ago | Handshake completed | 456 ms |
| 16 days ago | Handshake completed | 460 ms |
| 17 days ago | Handshake completed | 445 ms |
| 18 days ago | Handshake completed | 451 ms |
| 19 days ago | Handshake completed | 448 ms |
| 20 days ago | Handshake completed | 479 ms |
| 21 days ago | Handshake completed | 447 ms |
| 23 days ago | Handshake completed | 303 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 ai.byteask/embedded-docs and makes no claim about it beyond what these checks measured.