Remote MCP · Endpoint

ai.byteask/embedded-docs MCP server

No. ai.byteask/embedded-docs answered an MCP handshake 2 hours ago.

UpLast checked 2 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
416 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Page-cited retrieval for embedded docs, datasheets, MISRA, CMSIS, and RTOS references.
Website
https://docs.byteask.ai/embedded
Repository
https://github.com/ByteAsk/ByteAsk-Embedded-MCP
Listing
From the official MCP registry (active).
Recent checks of ai.byteask/embedded-docs
CheckedResultHandshake
2 hours agoHandshake completed416 ms
1 day agoHandshake completed1.21 s
3 days agoHandshake completed1.24 s
3 days agoHandshake completed1.17 s
4 days agoHandshake completed349 ms
5 days agoHandshake completed1.24 s
7 days agoHandshake completed417 ms
10 days agoHandshake completed1.13 s
12 days agoHandshake completed339 ms
14 days agoHandshake completed366 ms
17 days agoHandshake completed374 ms
19 days agoHandshake completed464 ms
21 days agoHandshake completed473 ms
23 days agoHandshake completed477 ms
25 days agoHandshake completed461 ms
26 days agoHandshake completed478 ms
28 days agoHandshake completed475 ms
29 days agoHandshake completed461 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.