Flash and run real firmware on physical embedded dev boards from an AI agent, over MCP.
MCPpedia last refreshed this data
io.github.oxyvore-cyber/firmware-test-farm-mcp is an MCP server that flash and run real firmware on physical embedded dev boards from an AI agent, over MCP. Its tool list has not been published yet over http, requires no API key, and scores 67/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
https://test-farm-17d99.web.app/mcpRemote servers are added as connectors, not in claude_desktop_config.json, which is for local servers.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Flash and run real firmware on physical embedded dev boards from an AI agent, over MCP.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in ai-ml / security
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
An open-source AI agent that brings the power of Gemini directly into your terminal.
🛡️ BLA (Blind LLM Agents) — Adversarial defense shield that protects binaries, Electron apps, JS bundles, Python, and WebAssembly against AI reverse-engineering agents like REA. Poison -> Exhaust -> Hallucinate.
Open source device layer for AI agents: control mobile, web, TV, and desktop apps over MCP
MCP Security Weekly
Get CVE alerts and security updates for io.github.oxyvore-cyber/firmware-test-farm-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP server that lets an AI agent flash a compiled firmware binary onto a real, physical embedded dev board, run it, and get back structured pass/fail results — serial output, crash info, reset reason, timing — instead of a simulator or a description of what should happen.
This repo hosts the server.json manifest for the MCP Registry. The
server itself runs as a hosted, always-on remote endpoint — there's no package to install.
Sign up and create an API key from the dashboard, then point any MCP client that supports Streamable HTTP + a bearer token at:
https://test-farm-17d99.web.app/mcp Authorization: Bearer
run_firmware_test — flashes the given firmware artifact onto a real board of the requested board_type
and waits for a structured result (pass/fail, serial log excerpt, crash/reset info, timing). Every response
includes live queue info (position, boards available, estimated wait) so an agent can decide whether to wait
or come back later.get_upload_url — returns a short-lived signed URL to upload a firmware binary to before calling
run_firmware_test.search_firmware_examples — searches a curated knowledge base of reference examples, known issues, and
pinout/datasheet links for a given board type.heltec_wireless_tracker, arduino_giga_r1, xiao_nrf52840_plus, arduino_nicla_voice,
arduino_nano_33_ble, adafruit_feather_esp32_v2, seeed_grove_vision_ai_v2, raspberrypi_pico
More board types are defined in the schema for future hardware; a submission for a board_type with no
physical board currently registered is rejected up front rather than left queued forever.
Every account starts on a free tier (50 firmware runs/month). Paid and Enterprise tiers are unlimited — Enterprise additionally covers custom board types and custom motors/controllers/sensors outside the standard fleet. See the dashboard for current usage and to request a tier change.