Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/indecenti/NucleoOsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/indecenti/nucleoos/context7)<a href="https://agentmods.dev/mcp/indecenti/nucleoos/context7"><img src="https://agentmods.dev/badge/mcp/indecenti/nucleoos/context7/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/indecenti/nucleoos/context7"><img src="https://agentmods.dev/badge/mcp/indecenti/nucleoos/context7.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
context7 scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 11 lines scan A 28225054f563
context7 is an MCP server published in the GitHub repository indecenti/NucleoOs (63 stars, last pushed 4d ago), with no licence file. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
hardware-logging
MCP server "hardware-logging" as configured in gurul/hardware-logging. Runs locally from the hardware-logging Python package.
fastled
Add your description here. Runs locally from the mcp_server.py Python package. Needs 1 environment variable to run.
agentic-hil
Hardware-in-the-loop MCP server for AI coding agents: develop firmware on the real board behind your debug probe, flashing, resetting and driving UART and CAN against it. The run on the hardware is the gate that decides the work is done, and a pytest plugin runs the same gate in CI. Runs locally from the agentic-hil…
hwcontract
Temporal assertions for real hardware traces: judge pulse timing, serial logs and decoded events against YAML contracts (MCP server, pytest plugin, GitHub Action). Runs locally from the hwcontract Python package.
byteask-embedded-docs
MCP server "byteask-embedded-docs" as configured in ByteAsk/ByteAsk-Embedded-MCP. Runs locally from the byteask-embedded-mcp Python package.
embedded-docs
Page-cited retrieval for embedded docs, datasheets, MISRA, CMSIS, and RTOS references. Remote server at mcp.byteask.ai.