MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

Publisher portfolio

turbyho

Explore the MCP servers published by turbyho, with independent connection checks, performance measurements, and setup instructions for each project.

Listed servers
4

Active projects in this portfolio. Deleted and deprecated registry rows are excluded.

Sampled servers
0

Active servers with a recorded connection probe

Latest probe connected
0

Latest stored probe connected. This is not a live guarantee.

Repositories
4

Distinct source repositories linked by the active listings

Portfolio overview

MCP servers

Compare connection status and measurements. Open a server for its tools, check results, and client configuration.

Dated server measurements. The status describes the last probe or a listed authentication requirement. Checks that have not been measured are not failures. Open a server to inspect the evidence.
Server / capabilityLast probeMedian latencyChecks passedLast checked
io.github.turbyho/fw-context-mcp

Build-aware code intelligence for embedded C/C++ firmware — libclang, FTS5, call graphs, 37 tools

Developer ToolsCode & DevOps

Not measuredNot measured4 / 6Not checked yet
io.github.turbyho/datasheet-lens

Component datasheets (PDF) for LLM agents: index, search, original pages; BOM and CAD checks

Developer ToolsCode & DevOps

Not measuredNot measured4 / 6Not checked yet
io.github.turbyho/mem-context

Temporal memory MCP server with LanceDB vector search, weight-decay scoring, and LLM consolidation

Developer ToolsAI / LLM tooling

Not measuredNot measured4 / 6Not checked yet
KiCad Workbench

Gives KiCad 8, 9 and 10 projects to LLM agents: schematics, boards, ERC, DRC, BOM, edits

Developer ToolsCode & DevOps

Not measuredNot measured4 / 6Not checked yet

Company & identity

About turbyho

turbyho publishes MCP servers under the io.github.turbyho namespace. This namespace is associated with a GitHub login in the MCP Registry.

Namespace verification connects the publisher to its registry identity. It does not certify the security of individual servers.

Source repositories