Not reviewed
No score, grade or rank. This listing is facts from the official MCP registry and our own checks, and it stays out of the rankings until the panel reviews it.
Page-cited retrieval for embedded docs, datasheets, MISRA, CMSIS, and RTOS references.
Facts
- MCP registry
ai.byteask/embedded-docs· 1.0.1- Endpoint
https://mcp.byteask.ai/mcp- Website
- docs.byteask.ai/embedded
- GitHub stars
- 24
- Registry entry
- updated 19 Jun 2026
From the official MCP registry, the package registries and our own checks. JSON · Markdown
Why it's listed
- It's published in the registry under byteask.ai, a namespace the registry only gives to whoever proves they control that domain.
Being indexed says nothing about quality, and nobody can pay for it. Is this yours? Ask for a review.
Tools it lists 3 · about 1,167 tokens of context · checked 1 hour ago
| Tool | What it does | Hint |
|---|---|---|
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… | |
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.… | |
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… |
What https://mcp.byteask.ai/mcp answered to tools/list, asked without credentials over MCP 2025-11-25. The token figure is the size of the list as sent, divided by four; a model sees about that much before it calls anything. Full definitions, input schemas included, are in the listing's JSON under mcpTools.
How its tools read to an agent 0 errors · 6 warnings · 2 notes
- warnTC07search_docsthe description is about 627 tokens
- warnTC11request_documentnone of its 2 parameters has a description
- warnTC11search_docsnone of its 3 parameters has a description
- warnTC16get_contextno readOnlyHint or destructiveHint
- warnTC16request_documentno readOnlyHint or destructiveHint
- warnTC16search_docsno readOnlyHint or destructiveHint
- noteTC11get_contextparameters are documented in the description but not in the schema: effort, result_id
- noteTC29serverabout 94 tokens (7% of the definitions) are titles that repeat property or function names
The checks from /check and anchor check, run each day on the list above: about 1,167 tokens of definitions. Not part of the score yet. Check your own server.