All servers · Documents & retrieval
ai.byteask/embedded-docs
ai.byteask/embedded-docs · v1.0.1
No registry update 90+ days
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Not declared (tools carry no read/destructive hints) |
| Capabilities declared | experimental, prompts, resources, tools |
| Tool definitions | 3 tools · with description 100% · input schema is an object 100% · read/destructive hints 0% |
Description written by the publisher, not verified
Page-cited retrieval for embedded docs, datasheets, MISRA, CMSIS, and RTOS references.
Connect
streamable-http · https://mcp.byteask.ai/mcp
claude mcp add --transport http embedded-docs https://mcp.byteask.ai/mcp{
"mcpServers": {
"embedded-docs": {
"url": "https://mcp.byteask.ai/mcp"
}
}
}Tools as reported by the server
search_docsSearch 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,get_contextExpand a previous search hit to its full verbatim section (markdown). Args: result_id: The id from a search_docs hit's `_ref:` line - the token inside the backticks, e.g. E1_Nasdaq_ITCH-5.0:1.2:1:0. Pass it exactly. effort: Internal diagnostics tag; clients should leave this unset.request_documentRequest that a document be ADDED to the corpus - use this when search_docs returns 'no confident match' for material it should cover (a standard, protocol spec, SCPI or instrument manual, MCU / hardware datasheet, or library reference). This does NOT search; use search_docs for that. Pass ONE string
Repository · Website · JSON · Text for agents · Registry updated 2026-06-19