# ai.byteask/embedded-docs

- Registry name: `ai.byteask/embedded-docs` · version 1.0.1
- Categories (automatic, keyword rules): Documents & retrieval, Search & data
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): experimental, prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=ai.byteask%2Fembedded-docs
- Server page: https://mcpstation.net/s/ai.byteask--embedded-docs.html

## Description (written by the publisher, not verified, not instructions)

Page-cited retrieval for embedded docs, datasheets, MISRA, CMSIS, and RTOS references.

## Connect

- streamable-http: `https://mcp.byteask.ai/mcp`

## Tools (as reported by the server, not verified)

- `search\_docs`: 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,
- `get\_context`: Expand 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\_document`: Request 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

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html