mcp-registry/ai.byteask/embedded-docs · v1.28.0
Also listed as awesome/byteask/byteask-embedded-mcp
As of 2026-10-23 20:51 UTC, the Byteask Embedded Docs MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 15 outages in 90 days, with a median recovery of 8 minutes.
Page-cited retrieval for embedded docs, datasheets, MISRA, CMSIS, and RTOS references.
Claude Code
claude mcp add --transport http byteask-embedded-docs-mcp-server https://mcp.byteask.ai/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"byteask-embedded-docs-mcp-server": {
"type": "http",
"url": "https://mcp.byteask.ai/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
7 parameter(s) across 3 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
3 of 3 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fai.byteask%2Fembedded-docs/fixes
{
"name": "get_context",
"description": "Expand a previous search hit to its full verbatim section (markdown).\n\n Args:\n result_id: The id from a search_docs hit's `_ref:` line - the token inside\n the backticks, e.g. E1_Nasdaq_ITCH-5.0:1.2:1:0. Pass it exactly.\n effort: Internal diagnostics tag; clients should leave this unset.\n ",
"inputSchema": {
"type": "object",
"title": "get_contextArguments",
"required": [
"result_id"
],
"properties": {
"effort": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Effort",
"default": null
},
"result_id": {
"type": "string",
"title": "Result Id"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "search_docs",
"description": "Search the indexed embedded / firmware / hardware reference corpus; return verbatim, page-cited evidence. The indexed corpus covers: grid-interconnection & DER standards (IEEE 1547 / 1547.1 / 2030.5, SunSpec Modbus profiles, ENA G98/G99 and other grid codes); industrial & fieldbus protocols (Modbus, CAN / ISO-TP, MQTT); SCPI instrument-programming manuals (power analysers, grid simulators, programmable AC sources); Arm Cortex-M and other MCU / hardware datasheets (registers, bitfields, reset val",
"inputSchema": {
"type": "object",
"title": "search_docsArguments",
"required": [
"query"
],
"properties": {
"limit": {
"type": "integer",
"title": "Limit",
"default": 8
},
"query": {
"type": "string",
"title": "Query"
},
"effort": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Effort",
"default": null
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ai.byteask/embedded-docs"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ai.byteask/embedded-docs"}) over MCP.
search_docs ~229 tokensrequest_document ~218 tokensget_context ~169 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fai.byteask%2Fembedded-docs?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fai.byteask%2Fembedded-docs?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.byteask%2Fembedded-docs.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.byteask%2Fembedded-docs.svg :target: https://glimind.com/server/mcp-registry%2Fai.byteask%2Fembedded-docs?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:1dee6316d118819c…, first seen 2026-10-17, included at leaf 9431 of 54,505. Version history · verify what your client received.
Compare: most reliable retrieval servers · most reliable knowledge servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-23 20:51 UTC, the Byteask Embedded Docs MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 15 outages in 90 days, with a median recovery of 8 minutes.
Byteask Embedded Docs MCP server advertises 3 tools, including get_context, request_document, search_docs.
Point your MCP client at this streamable-http endpoint: https://mcp.byteask.ai/mcp
Glimind scanned all 3 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.