embedded-docs
Page-cited retrieval for embedded docs, datasheets, MISRA, CMSIS, and RTOS references.
ai.byteask/embedded-docs
Publication
Published
Publisher
ByteAsk
Publisher identity: Not verified
Primary source
Official MCP Registry record
https://github.com/ByteAsk/ByteAsk-Embedded-MCPStatic analysis · human review · publication
Security evidence
Scanner signals, coverage and review decisions describe different parts of this report.
- Scan status
- completed
- Coverage
- Sufficient source coverage
- Static risk signals
- 8/100 · low
- Finding count
- 2
- Highest finding severity
- medium
- Human review
- Approved review
- Review freshness
- Stale review
- Publication
- Published
Scan coverage and reliability
The scan completed with enough source coverage for ToolRepute's current review workflow. This does not verify runtime behavior.
Reliability: Meets current requirements
- Scanner version
- V5
- Scan run
- 191
- Last scan date
- 2026-09-06
- Files scanned
- 17
- Bytes scanned
- 48,827
- Manifest
- Found
- Source commit
- Pinned
- Truncation
- No
Analyzed source
https://github.com/ByteAsk/ByteAsk-Embedded-MCP
Analyzed commit: e7103adab7579df88313e763f66b4533519c651d
This assessment covers the available repository source. It does not inspect the hosted remote service or its runtime behavior.
Human review and publication
This historical decision does not establish current approval for the current review workflow. It may concern an older run, changed evidence or an older scanner.
- Review decision
- Approved review
- Review date
- 2026-09-08
- Reviewed scan run
- 191
- Reviewed commit
- e7103adab7579df88313e763f66b4533519c651d
Publication is a decision to display evidence under ToolRepute's current rules, not a security certification, endorsement or guarantee.
Internal reviewer identity, review notes and private metadata are not displayed.
Published findings
MediumShell command execution detectedINSTALL_SHELL_EXECassets/make_demo_gif.py:303Finding details and evidence
Shell command execution detected
Category: code execution
What was found
Static analysis detected an API or option capable of launching shell commands.
Why it matters
Shell execution can interact with the host system and expands the impact of unsafe input.
Evidence snippet
subprocess.run(["ffmpeg", "-y", "-v", "error", "-i", os.path.join(tmp, "f%04d.png"),
Scanner interpretation
A static rule match is a signal for contextual inspection, not a confirmed vulnerability or malicious behavior.
Recommended check
Inspect the command, its inputs and call path. Check input validation and whether execution is expected and explicitly authorized.
Limitations and legitimate-use context
The presence of an execution mechanism does not show that it is unsafe or that it runs without user intent.
MediumShell command execution detectedINSTALL_SHELL_EXECassets/make_demo_gif.py:305Finding details and evidence
Shell command execution detected
Category: code execution
What was found
Static analysis detected an API or option capable of launching shell commands.
Why it matters
Shell execution can interact with the host system and expands the impact of unsafe input.
Evidence snippet
subprocess.run(["ffmpeg", "-y", "-v", "error", "-framerate", str(FPS),
Scanner interpretation
A static rule match is a signal for contextual inspection, not a confirmed vulnerability or malicious behavior.
Recommended check
Inspect the command, its inputs and call path. Check input validation and whether execution is expected and explicitly authorized.
Limitations and legitimate-use context
The presence of an execution mechanism does not show that it is unsafe or that it runs without user intent.
Reputation evidence
Insufficient evidence · low confidence · model v1
Evidence support score: 5/100. This is separate from risk, review and publication.
Assessment as of 2026-10-23. Live repository HEAD is not checked when this page loads.
Security evidence · 0/25LIMITED · low confidence
Reliable mapped v6 scope is not established; evidence age: aging.
Static support is capped at 18/25 before a risk deduction of ceil(riskScore/4); zero findings does not establish safety.
Last observed: 2026-09-06
- scan record 191: Scanner v5; completed; manifest found; sufficient scope true; 17 files / 48827 bytes; 2 findings; not truncated; scanner risk score 8.Commit e7103adab7579df88313e763f66b4533519c651dSource evidence
Static analysis covers a bounded source scope, not runtime, dependencies in full, or hosted behavior.
Source transparency · 5/25STALE · low confidence
Completed matching public GitHub acquisition: not established (+0).
Unique primary mapping: observed (+5).
Completed matching pinned commit: not established (+0).
Completed matching source mapping: not established (+0).
Matching manifest and sufficient untruncated scope: not established (+0).
Last observed: 2026-10-04
- source record 185: Primary mapping is incomplete or changed. Live repository HEAD is not checked by page requests.Source evidence
- scan record 191: Scanner v5; completed; manifest found; sufficient scope true; 17 files / 48827 bytes; not truncated.Commit e7103adab7579df88313e763f66b4533519c651dSource evidence
A source mapping does not prove ownership. Repository availability and live HEAD are not rechecked here.
Review freshness · 0/25STALE · low confidence
Current artifact-bound approval earns 25; matching approval with unchecked live HEAD earns 8; stale, missing or rejected evidence earns 0.
Last observed: 2026-09-08
- review record 19: Decision: approved; reviewed run 191; NEXT-11 freshness: stale.
Page requests make no upstream probe. An old approval is not approval of changed evidence.
Registry consistency · 0/10UNKNOWN · low confidence
Unique primary, normalized active/latest official registry observation earns 10 within 30 days, 5 within 90, otherwise 0.
Last observed: 2026-10-04
- registry record 185: Normalized official record: false; active: true; latest: true; observation age: recent.
Registry consistency is a source-record observation, not identity verification or a security endorsement.
Publisher identity confidence · 0/15UNKNOWN · low confidence
No verified legal, domain or repository-ownership binding is available; free text and the registry verification flag earn no credit.
Last observed: Not available
Publisher name and registry namespace cannot establish legal identity or ownership.
Recorded assessment history (1)
History starts with explicit captures in model v1. Past source and review state cannot be fully reconstructed. Page reads do not save snapshots; changes in the live assessment appear in history only after an explicit capture.
- 2026-10-11 · model v1 · 5/100 · low confidence · scan 191e7103adab7579df88313e763f66b4533519c651d
Recorded signal breakdown
- Security evidence: 0/25 · LIMITED
- Source transparency: 5/25 · STALE
- Review freshness: 0/25 · STALE
- Registry consistency: 0/10 · UNKNOWN
- Publisher identity confidence: 0/15 · UNKNOWN
Reputation reflects ToolRepute-observed evidence only; it is not a guarantee of security.
Signals may be incomplete or stale. Runtime and hosted behavior may differ from scanned source.
Publisher identity has no verified binding. Repository ownership and legal identity are not established.
This score measures support in the available evidence, not the probability that a tool is safe.
Registry data
Version
1.0.1
Packages
0
Remote endpoints
1
Enrichment
complete
Last fetched
2026-10-04
Registry inclusion identifies the source record. It is not a ToolRepute security endorsement.
Normalized sources
Structured from the Official MCP Registry record.
Enriched 2026-10-04
Remote endpoints
streamable-http · mcp.byteask.ai
https://mcp.byteask.ai/mcpMore reviewed MCP servers
Continue exploring integrations with published ToolRepute reviews.